0.12.0
This page documents the changes in Kannika Armory version 0.12.0.
Changelog 0.12.0
Features
-
General: Add preflight checks to a Restore
-
General: Add monitoring sidecar to a Backup
-
General: Add namespace isolation to the platform
-
API: Improve JSON logging format
-
API: Add new
/rest/restores/{name}/metrics
endpoint -
API: Rename
id
field of a Restore toname
-
API: Alias
name
field of a Restore toid
-
Backup: Add
.spec.monitoring.enabled
field to toggle monitoring sidecar -
Console: Topics recently added to a Restore will no longer be auto-selected, but a button will be shown to select them instead.
-
Console: Show the amount of lag for each topic in the Topics tab of a Backup.
-
Console: Show the total lag of a Backup.
-
Console: Add preflight checks to the Restore page
-
Console: Add new Schema Mapping tab to the Restore page
-
Console: Add dark mode
-
Core: Revert to single queue design for backups
-
Helm: Add support for
global.kubernetes.namespace
setting for all components -
Helm: Add
api.serviceAccount.rbac.create
setting (defaulttrue
) -
Helm: Add
operator.serviceAccount.rbac.create
setting (defaulttrue
) -
Helm: Add
operator.config.logging.format
setting to configure logging format (defaultjson
)
Bug Fixes
-
Restore: when using the
payload-schema-mapping
plugin, tombstone records will retain theirnull
payload instead of being restored with an empty byte array. -
Restore: when using the
key-schema-mapping
plugin, keyless records will retain theirnull
key instead of being restored with an empty byte array. -
Backup: tasks will now be restarted on global Kafka errors (e.g.
BrokerNotAvailable
), aslibrdkafka
does not recover properly from these errors. -
Console: The console will now honor the
console.config.security.enabled
setting when it is set tofalse
and will no longer display a login screen. -
Helm: Set the operator service URL when
api.config.security.enabled
is set tofalse
. -
API: Ignore retention settings when delete policy is not set
Breaking Changes
-
General: The platform will only watch for resources in the namespace defined by
global.kubernetes.namespace
, which defaults to the Helm release namespace. -
General: The platform will default to
Role
andRoleBinding
for Kubernetes RBAC. -
API: Only look for resources in the resource namespace (e.g.
kannika-data
) defined byglobal.kubernetes.namespace
-
Operator: Only look for resources in the resource namespace (e.g.
kannika-data
) defined byglobal.kubernetes.namespace
-
Operator: Only look for license in release namespace (e.g.
kannika-system
) defined by the Helm release namespace -
Helm: Default to
Role
andRoleBinding
resources for RBAC -
Helm:
operator.serviceAccount.clusterRbac.create
now defaults tofalse
-
Helm:
api.serviceAccount.clusterRbac.create
now defaults tofalse
Documentation
-
Add configuration section on namespaces (
/installation/configuration/namespaces/
) -
Add configuration section on Kubernetes RBAC (
/installation/configuration/kubernetes-rbac/
) -
Add user guide section on Backup monitoring (
/user-guide/backup/monitoring
)
Miscellaneous Tasks
-
Bump version to 0.12.0
-
Naming strategy of Kannika Armory resources has been updated.