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

chore(oci/jjgadgets-error-page-ingress-nginx): update 1.0.0 ➼ 0d85c3e - autoclosed #1805

Conversation

tinfoild[bot]
Copy link
Contributor

@tinfoild tinfoild bot commented Feb 2, 2025

This PR contains the following updates:

Package Update Change OpenSSF
registry.jjgadgets.tech/jjgadgets/jjgadgets-error-page-ingress-nginx (source) digest 5e0e09a -> 0d85c3e OpenSSF Scorecard

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.

Copy link

cloudflare-workers-and-pages bot commented Feb 2, 2025

Deploying jjgadgets-biohazard with  Cloudflare Pages  Cloudflare Pages

Latest commit: f55c184
Status: ✅  Deploy successful!
Preview URL: https://d59f33e0.jjgadgets-biohazard.pages.dev
Branch Preview URL: https://renovate-registry-jjgadgets-1zx4.jjgadgets-biohazard.pages.dev

View logs

@tinfoild
Copy link
Contributor Author

tinfoild bot commented Feb 2, 2025

--- kube/deploy/core/ingress/ingress-nginx/app Kustomization: flux-system/1-core-ingress-nginx-app HelmRelease: ingress/default-backend

+++ kube/deploy/core/ingress/ingress-nginx/app Kustomization: flux-system/1-core-ingress-nginx-app HelmRelease: ingress/default-backend

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

       strategy: uninstall
   values:
     controller:
       type: daemonset
     image:
       repository: registry.jjgadgets.tech/jjgadgets/jjgadgets-error-page-ingress-nginx
-      tag: 1.0.0-caddy-2.7.5@sha256:5e0e09a23522dc7af059ad560b047137c37da539dd162fb2b0d602592bf8682e
+      tag: 1.0.0-caddy-2.7.5@sha256:0d85c3e2e69c39bb3588ccd825d4787ff56b8ca499864ae923c1a6d163ad77a9
     podLabels:
       ingress.home.arpa/nginx-external: allow
       ingress.home.arpa/nginx-internal: allow
       ingress.home.arpa/nginx-public: allow
     resources:
       limits:

@tinfoild
Copy link
Contributor Author

tinfoild bot commented Feb 2, 2025

--- HelmRelease: ingress/default-backend DaemonSet: ingress/default-backend

+++ HelmRelease: ingress/default-backend DaemonSet: ingress/default-backend

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

       serviceAccountName: default
       automountServiceAccountToken: true
       dnsPolicy: ClusterFirst
       enableServiceLinks: true
       containers:
       - name: default-backend
-        image: registry.jjgadgets.tech/jjgadgets/jjgadgets-error-page-ingress-nginx:1.0.0-caddy-2.7.5@sha256:5e0e09a23522dc7af059ad560b047137c37da539dd162fb2b0d602592bf8682e
+        image: registry.jjgadgets.tech/jjgadgets/jjgadgets-error-page-ingress-nginx:1.0.0-caddy-2.7.5@sha256:0d85c3e2e69c39bb3588ccd825d4787ff56b8ca499864ae923c1a6d163ad77a9
         imagePullPolicy: null
         ports:
         - name: http
           containerPort: 8080
           protocol: TCP
         livenessProbe:

@tinfoild tinfoild bot changed the title chore(oci/jjgadgets-error-page-ingress-nginx): update 1.0.0 ➼ 0d85c3e chore(oci/jjgadgets-error-page-ingress-nginx): update 1.0.0 ➼ 0d85c3e - autoclosed Feb 11, 2025
@tinfoild tinfoild bot closed this Feb 11, 2025
@tinfoild tinfoild bot deleted the renovate/registry.jjgadgets.tech-jjgadgets-jjgadgets-error-page-ingress-nginx-1.0.0-caddy-2.7.5 branch February 11, 2025 10:07
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.

0 participants