Skip to content

Update ghcr.io/dragonflydb/dragonfly-operator/helm/dragonfly-operator Docker tag to v1.8.0 - #258

Open
renovate[bot] wants to merge 1 commit into
developfrom
renovate/ghcr.io-dragonflydb-dragonfly-operator-helm-dragonfly-operator-1.x
Open

renovate[bot] wants to merge 1 commit into
developfrom
renovate/ghcr.io-dragonflydb-dragonfly-operator-helm-dragonfly-operator-1.x

Conversation

@renovate

@renovate renovate Bot commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
ghcr.io/dragonflydb/dragonfly-operator/helm/dragonfly-operator helm_release minor v1.3.0 → v1.8.0

Release Notes

dragonflydb/dragonfly-operator (ghcr.io/dragonflydb/dragonfly-operator/helm/dragonfly-operator)

v1.8.0

Compare 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: dragonflydb/dragonfly-operator@v1.7.1...v1.8.0

v1.7.1

Compare 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: dragonflydb/dragonfly-operator@v1.7.0...v1.7.1

v1.7.0

Compare 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

  • Operator-managed NetworkPolicy has been removed (revert of the feature added in #​473/#​514, via #​560).
    • The spec.networkPolicyEnabled field has been removed from the Dragonfly CRD.
    • Upgrading the operator itself is safe for existing Dragonfly CRs 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).
    • However, re-applying an old manifest that still sets networkPolicyEnabled (e.g. via GitOps/CI re-sync) may be rejected: kubectl 1.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: drop networkPolicyEnabled from your stored manifests going forward to avoid this.
    • The operator will no longer create, update, or reconcile away a NetworkPolicy for Dragonfly instances.
    • This was reverted because it broke common setups where clients/workloads live in a different namespace than the Dragonfly instance (#​546), and it blocked external Prometheus/VictoriaMetrics scrapers from reaching /metrics (#​495).
    • Action required: if you relied on the operator-managed policy (default or networkPolicyEnabled: true), you must now create and maintain your own NetworkPolicy for equivalent restrictions.
    • ⚠️ Leftover NetworkPolicy objects are NOT auto-deleted on upgrade. If you were running v1.6.0/v1.6.1 with networkPolicyEnabled unset or true, the operator had already created a NetworkPolicy object (owned by, but not garbage-collected on operator upgrade from, the Dragonfly CR). 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:
   kubectl delete networkpolicy <dragonfly-instance-name> -n <namespace>

What's Changed

New Contributors

Full Changelog: dragonflydb/dragonfly-operator@v1.6.1...v1.7.0

v1.6.1

Compare Source

Release v1.6.1

Docker image: ghcr.io/dragonflydb/operator:v1.6.1
Helm chart: oci://ghcr.io/dragonflydb/dragonfly-operator/helm

This version contains a fix for chart where a missing configmap role is added.

What's Changed

Full Changelog: dragonflydb/dragonfly-operator@v1.6.0...v1.6.1

v1.6.0

Compare Source

Release v1.6.0

Docker image: ghcr.io/dragonflydb/operator:v1.6.0
Helm chart: oci://ghcr.io/dragonflydb/dragonfly-operator/helm

What's Changed

New Contributors

Full Changelog: dragonflydb/dragonfly-operator@v1.5.0...v1.6.0

v1.5.0

Compare Source

Release v1.5.0

Docker image: ghcr.io/dragonflydb/operator:v1.5.0
Helm chart: oci://ghcr.io/dragonflydb/dragonfly-operator/helm

What's Changed

New Contributors

Full Changelog: dragonflydb/dragonfly-operator@v1.4.0...v1.5.0

v1.4.0

Compare Source

Release v1.4.0

Docker image: ghcr.io/dragonflydb/operator:v1.4.0
Helm chart: oci://ghcr.io/dragonflydb/dragonfly-operator/helm

What's Changed

New Contributors

Full Changelog: dragonflydb/dragonfly-operator@v1.3.1...v1.4.0

v1.3.1

Compare Source

Release v1.3.1

Docker image: ghcr.io/dragonflydb/operator:v1.3.1
Helm chart: oci://ghcr.io/dragonflydb/dragonfly-operator/helm

What's Changed

New Contributors

Full Changelog: dragonflydb/dragonfly-operator@v1.3.0...v1.3.1


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/ghcr.io-dragonflydb-dragonfly-operator-helm-dragonfly-operator-1.x branch from a032704 to adbbb37 Compare October 3, 2026 15:02
@renovate renovate Bot changed the title chore(deps): update ghcr.io/dragonflydb/dragonfly-operator/helm/dragonfly-operator docker tag to v1.7.0 Update ghcr.io/dragonflydb/dragonfly-operator/helm/dragonfly-operator Docker tag to v1.7.0 Oct 14, 2026
@renovate renovate Bot changed the title Update ghcr.io/dragonflydb/dragonfly-operator/helm/dragonfly-operator Docker tag to v1.7.0 Update ghcr.io/dragonflydb/dragonfly-operator/helm/dragonfly-operator Docker tag to v1.7.1 Oct 17, 2026
@renovate
renovate Bot force-pushed the renovate/ghcr.io-dragonflydb-dragonfly-operator-helm-dragonfly-operator-1.x branch from adbbb37 to 0aada23 Compare October 17, 2026 16:06
@renovate
renovate Bot force-pushed the renovate/ghcr.io-dragonflydb-dragonfly-operator-helm-dragonfly-operator-1.x branch from 0aada23 to c1e3498 Compare October 28, 2026 13:57
@renovate renovate Bot changed the title Update ghcr.io/dragonflydb/dragonfly-operator/helm/dragonfly-operator Docker tag to v1.7.1 chore(deps): update ghcr.io/dragonflydb/dragonfly-operator/helm/dragonfly-operator docker tag to v1.7.1 Nov 4, 2026
@renovate
renovate Bot force-pushed the renovate/ghcr.io-dragonflydb-dragonfly-operator-helm-dragonfly-operator-1.x branch from c1e3498 to 64e67e9 Compare November 15, 2026 19:37
@renovate renovate Bot changed the title chore(deps): update ghcr.io/dragonflydb/dragonfly-operator/helm/dragonfly-operator docker tag to v1.7.1 Update ghcr.io/dragonflydb/dragonfly-operator/helm/dragonfly-operator Docker tag to v1.8.0 Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants