Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(github-release): update dragonfly operator group ( v1.1.3 → v1.1.4 ) (patch) #4945

Merged
merged 1 commit into from
Jun 27, 2024

Conversation

lumiere-bot[bot]
Copy link
Contributor

@lumiere-bot lumiere-bot bot commented Jun 26, 2024

This PR contains the following updates:

Package Update Change
dragonflydb/dragonfly-operator patch v1.1.3 -> v1.1.4
ghcr.io/dragonflydb/operator patch v1.1.3 -> v1.1.4

Release Notes

dragonflydb/dragonfly-operator (dragonflydb/dragonfly-operator)

v1.1.4

Compare Source

Release v1.1.4

Docker image: docker.dragonflydb.io/dragonflydb/operator:v1.1.4

This release adds support for custom service labels and fix a bug for single-pod dragonfly rolling updates.

What's Changed
New Contributors

Full Changelog: dragonflydb/dragonfly-operator@v1.1.3...v1.1.4


Configuration

📅 Schedule: 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 these updates again.


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

This PR has been generated by Renovate Bot.

@lumiere-bot
Copy link
Contributor Author

lumiere-bot bot commented Jun 26, 2024

--- HelmRelease: database/dragonfly-operator Deployment: database/dragonfly-operator

+++ HelmRelease: database/dragonfly-operator Deployment: database/dragonfly-operator

@@ -48,13 +48,13 @@

       containers:
       - args:
         - --health-probe-bind-address=:8081
         - --metrics-bind-address=:8080
         command:
         - /manager
-        image: ghcr.io/dragonflydb/operator:v1.1.3@sha256:4c512cfc5498558f7a0a44cee69195e6c9b72f5d2cafeec9be487d95b3708978
+        image: ghcr.io/dragonflydb/operator:v1.1.4@sha256:8eafdc4f4aafd3157b1056c763bc1951466f7ec42d5794e03e0072bb5582abe8
         livenessProbe:
           failureThreshold: 3
           httpGet:
             path: /healthz
             port: 8081
           initialDelaySeconds: 15

@lumiere-bot
Copy link
Contributor Author

lumiere-bot bot commented Jun 26, 2024

--- kubernetes/kyak/apps/database/dragonfly/app Kustomization: flux-system/dragonfly HelmRelease: database/dragonfly-operator

+++ kubernetes/kyak/apps/database/dragonfly/app Kustomization: flux-system/dragonfly HelmRelease: database/dragonfly-operator

@@ -35,13 +35,13 @@

             - --health-probe-bind-address=:8081
             - --metrics-bind-address=:8080
             command:
             - /manager
             image:
               repository: ghcr.io/dragonflydb/operator
-              tag: v1.1.3@sha256:4c512cfc5498558f7a0a44cee69195e6c9b72f5d2cafeec9be487d95b3708978
+              tag: v1.1.4@sha256:8eafdc4f4aafd3157b1056c763bc1951466f7ec42d5794e03e0072bb5582abe8
             probes:
               liveness:
                 custom: true
                 enabled: true
                 spec:
                   failureThreshold: 3

@lumiere-bot lumiere-bot bot changed the title fix(container): update ghcr.io/dragonflydb/operator ( v1.1.3 → v1.1.4 ) fix(github-release): update dragonfly operator group ( v1.1.3 → v1.1.4 ) (patch) Jun 26, 2024
@lumiere-bot lumiere-bot bot force-pushed the renovate/kyak-patch-dragonfly-operator branch from 528db1b to c7b3d75 Compare June 26, 2024 10:07
@lumiere-bot lumiere-bot bot merged commit cee6c76 into main Jun 27, 2024
12 checks passed
@lumiere-bot lumiere-bot bot deleted the renovate/kyak-patch-dragonfly-operator branch June 27, 2024 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants