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

feat(container): update image docker.io/rancher/system-upgrade-controller to v0.15.0 #1277

Merged
merged 1 commit into from
Feb 20, 2025

Conversation

spicerabot[bot]
Copy link
Contributor

@spicerabot spicerabot bot commented Feb 18, 2025

This PR contains the following updates:

Package Update Change
docker.io/rancher/system-upgrade-controller minor v0.14.2 -> v0.15.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


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.

@spicerabot
Copy link
Contributor Author

spicerabot bot commented Feb 18, 2025

--- HelmRelease: system-upgrade/system-upgrade-controller Deployment: system-upgrade/system-upgrade-controller

+++ HelmRelease: system-upgrade/system-upgrade-controller Deployment: system-upgrade/system-upgrade-controller

@@ -78,13 +78,13 @@

         - name: SYSTEM_UPGRADE_JOB_PRIVILEGED
           value: 'true'
         - name: SYSTEM_UPGRADE_JOB_TTL_SECONDS_AFTER_FINISH
           value: '900'
         - name: SYSTEM_UPGRADE_PLAN_POLLING_INTERVAL
           value: 15m
-        image: docker.io/rancher/system-upgrade-controller:v0.14.2@sha256:3cdbfdd90f814702cefb832fc4bdb09ea93865a4d06c6bafd019d1dc6a9f34c9
+        image: docker.io/rancher/system-upgrade-controller:v0.15.0@sha256:6eabb80da751aca53f8f0628f36ac15e9d17f241d56b64efc209a4909084f573
         name: app
         securityContext:
           allowPrivilegeEscalation: false
           capabilities:
             drop:
             - ALL

@spicerabot
Copy link
Contributor Author

spicerabot bot commented Feb 18, 2025

--- kubernetes/apps/system-upgrade/system-upgrade-controller/app Kustomization: flux-system/system-upgrade-controller HelmRelease: system-upgrade/system-upgrade-controller

+++ kubernetes/apps/system-upgrade/system-upgrade-controller/app Kustomization: flux-system/system-upgrade-controller HelmRelease: system-upgrade/system-upgrade-controller

@@ -47,13 +47,13 @@

               SYSTEM_UPGRADE_JOB_KUBECTL_IMAGE: registry.k8s.io/kubectl:v1.32.2
               SYSTEM_UPGRADE_JOB_PRIVILEGED: true
               SYSTEM_UPGRADE_JOB_TTL_SECONDS_AFTER_FINISH: 900
               SYSTEM_UPGRADE_PLAN_POLLING_INTERVAL: 15m
             image:
               repository: docker.io/rancher/system-upgrade-controller
-              tag: v0.14.2@sha256:3cdbfdd90f814702cefb832fc4bdb09ea93865a4d06c6bafd019d1dc6a9f34c9
+              tag: v0.15.0@sha256:6eabb80da751aca53f8f0628f36ac15e9d17f241d56b64efc209a4909084f573
             securityContext:
               allowPrivilegeEscalation: false
               capabilities:
                 drop:
                 - ALL
               readOnlyRootFilesystem: true

@spicerabot spicerabot bot force-pushed the renovate/system-upgrade-controller branch 5 times, most recently from 0d86b67 to dd2989e Compare February 20, 2025 01:35
@spicerabot spicerabot bot force-pushed the renovate/system-upgrade-controller branch from dd2989e to 34ed4f8 Compare February 20, 2025 09:08
@spiceratops spiceratops merged commit ba0a3c5 into main Feb 20, 2025
6 of 8 checks passed
@spiceratops spiceratops deleted the renovate/system-upgrade-controller branch February 20, 2025 10:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant