Update dragonfly-operator Docker tag to v1.8.0 #13
No reviewers
Labels
No labels
Status/Ready for master
Type/Update
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
wiemanboy/WieCloud!13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "update/dragonflydb/minor"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v1.6.1→v1.8.0Release Notes
dragonflydb/dragonfly-operator (dragonfly-operator)
v1.8.0Compare Source
Release v1.8.0
Docker image: ghcr.io/dragonflydb/operator:v1.8.0
Helm chart: oci://ghcr.io/dragonflydb/dragonfly-operator/helm
What's Changed
New Contributors
Full Changelog: https://github.com/dragonflydb/dragonfly-operator/compare/v1.7.1...v1.8.0
v1.7.1Compare Source
Release v1.7.1
Docker image: ghcr.io/dragonflydb/operator:v1.7.1
Helm chart: oci://ghcr.io/dragonflydb/dragonfly-operator/helm
What's Changed
Full Changelog: https://github.com/dragonflydb/dragonfly-operator/compare/v1.7.0...v1.7.1
v1.7.0Compare Source
Release v1.7.0
Docker image: ghcr.io/dragonflydb/operator:v1.7.0
Helm chart: oci://ghcr.io/dragonflydb/dragonfly-operator/helm
⚠️ Breaking Change
NetworkPolicyhas been removed (revert of the feature added in #473/#514, via #560).spec.networkPolicyEnabledfield has been removed from theDragonflyCRD.DragonflyCRs that already have this field set — it is simply ignored (unknown JSON fields are dropped silently when the operator reads the object; nothing crashes or errors).networkPolicyEnabled(e.g. via GitOps/CI re-sync) may be rejected:kubectl1.27+ defaults to--validate=strict, which performs client-side schema validation and will error on the now-unknown field. Direct API/patch updates bypass this and just have the field silently pruned server-side. Recommendation: dropnetworkPolicyEnabledfrom your stored manifests going forward to avoid this.NetworkPolicyfor Dragonfly instances./metrics(#495).networkPolicyEnabled: true), you must now create and maintain your ownNetworkPolicyfor equivalent restrictions.networkPolicyEnabledunset ortrue, the operator had already created aNetworkPolicyobject (owned by, but not garbage-collected on operator upgrade from, theDragonflyCR). This revert only removes the reconcile logic — it does not clean up existing objects. After upgrading, you must manually delete any operator-created policies to fully restore pre-#473 behavior:What's Changed
New Contributors
Full Changelog: https://github.com/dragonflydb/dragonfly-operator/compare/v1.6.1...v1.7.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.
18e6d0f0da165b1b6e51ec2d7a5078to3eb11f21c2View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.