Releases: openkcm/krypton-operator
Releases · openkcm/krypton-operator
v0.7.0
v0.6.5
More cleanup.
v0.6.4
Cleanup
v0.6.3
Align naming in events and startup logs to “Krypton Operator”.
v0.6.2
Align KryptonDeployment CRD status schema in Helm chart by adding
status.conditions, status.lastAppliedChart, and status.lastMessage.
This stops API warnings and enables full status updates by the operator.
v0.6.1
- Default object namespace during edge health-check when omitted in Helm manifests; removes empty-namespace lookup errors and improves self-healing accuracy.
v0.6.0
- RBAC: Chart now reads
apps/v1Deployments; ensure ClusterRole changes are applied. - Resource checks are limited to core/apps types to avoid RBAC failures while still validating key components.
- Default interval is 60s; can be overridden via
.Values.operator.checkIntervalor envKRYPTON_CHECK_INTERVAL. - Events used in tests: "RepairTriggered", "ReleaseMissing", plus Pending/Ready transitions.
v0.5.2
Fix Helm Chart.
v0.5.1
Fix some renaming Issues
v0.5.0
- Rename repository to
krypton-operator. - Introduce new CRD Kind
KryptonDeploymentwith pluralkryptondeployments(replacingCryptoEdgeDeployment). - Update operator/controller, CRD manifests, RBAC, Helm chart, examples, and e2e to the new names.
- Breaking: users must migrate from
CryptoEdgeDeploymenttoKryptonDeployment.