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(helm): update chart ingress-nginx ( 4.10.1 → 4.11.1 ) #1956

Merged
merged 1 commit into from
Jul 19, 2024

Conversation

samip5-bot[bot]
Copy link
Contributor

@samip5-bot samip5-bot bot commented Jul 8, 2024

This PR contains the following updates:

Package Update Change
ingress-nginx minor 4.10.1 -> 4.11.1

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 this update again.


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

This PR has been generated by Renovate Bot.

Copy link
Contributor Author

samip5-bot bot commented Jul 8, 2024

--- k8s/media/apps/networking/nginx/app Kustomization: flux-system/cluster-apps-nginx HelmRelease: networking/ingress-nginx

+++ k8s/media/apps/networking/nginx/app Kustomization: flux-system/cluster-apps-nginx HelmRelease: networking/ingress-nginx

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

       chart: ingress-nginx
       interval: 5m
       sourceRef:
         kind: HelmRepository
         name: ingress-nginx-charts
         namespace: flux-system
-      version: 4.10.1
+      version: 4.11.0
   install:
     remediation:
       retries: 5
   interval: 5m
   rollback:
     cleanupOnFail: true

Copy link
Contributor Author

samip5-bot bot commented Jul 8, 2024

--- HelmRelease: networking/ingress-nginx Deployment: networking/ingress-nginx-controller

+++ HelmRelease: networking/ingress-nginx Deployment: networking/ingress-nginx-controller

@@ -29,13 +29,13 @@

         app.kubernetes.io/component: controller
     spec:
       dnsPolicy: ClusterFirst
       priorityClassName: system-cluster-critical
       containers:
       - name: controller
-        image: registry.k8s.io/ingress-nginx/controller:v1.10.1@sha256:e24f39d3eed6bcc239a56f20098878845f62baa34b9f2be2fd2c38ce9fb0f29e
+        image: registry.k8s.io/ingress-nginx/controller:v1.11.0@sha256:a886e56d532d1388c77c8340261149d974370edca1093af4c97a96fb1467cb39
         imagePullPolicy: IfNotPresent
         lifecycle:
           preStop:
             exec:
               command:
               - /wait-shutdown
--- HelmRelease: networking/ingress-nginx ServiceAccount: networking/ingress-nginx-admission

+++ HelmRelease: networking/ingress-nginx ServiceAccount: networking/ingress-nginx-admission

@@ -10,7 +10,8 @@

   labels:
     app.kubernetes.io/name: ingress-nginx
     app.kubernetes.io/instance: ingress-nginx
     app.kubernetes.io/part-of: ingress-nginx
     app.kubernetes.io/managed-by: Helm
     app.kubernetes.io/component: admission-webhook
+automountServiceAccountToken: true
 

@samip5
Copy link
Owner

samip5 commented Jul 13, 2024

Waiting for kubernetes/ingress-nginx#11588

| datasource | package       | from   | to     |
| ---------- | ------------- | ------ | ------ |
| helm       | ingress-nginx | 4.10.1 | 4.11.1 |
@samip5-bot samip5-bot bot force-pushed the renovate/media-ingress-nginx-4.x branch from 05e6810 to a2660ee Compare July 19, 2024 00:06
@samip5-bot samip5-bot bot changed the title feat(helm): update chart ingress-nginx ( 4.10.1 → 4.11.0 ) feat(helm): update chart ingress-nginx ( 4.10.1 → 4.11.1 ) Jul 19, 2024
@samip5 samip5 merged commit 16ff8a0 into main Jul 19, 2024
7 checks passed
@samip5 samip5 deleted the renovate/media-ingress-nginx-4.x branch July 19, 2024 08:03
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