.ops: add ingress nginx helm chart #7209
Open
+142
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
That we can easily update the chart. There was a CVE detected recently in the ingress nginx, and we did not update it for a long time. https://www.cvedetails.com/cve/CVE-2025-1974/ #IngressNightmare We also had a mix of versions: dev: ingress-nginx 4.0.6, but the helm chart is not detected. staging: ingress-nginx 4.5.2 prod: ingress-nginx 4.10.1 We now deploy the prod version everywhere to test the pipeline and the chart. Then we update to the most recent ingress-nginx version. Use the name ecamp3-ingress that it is clear that it's more than the official chart. (We add some of our own configuration). But that the existing services keep their name and thus might keep their ip, we set fullnameOverride, that the LoadBalancer name does not change.
|
I will test this later at night when i can change the IP again. |
usu
approved these changes
Apr 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
That we can easily update the chart.
There was a CVE detected recently in the ingress
nginx, and we did not update it for a long time.
https://www.cvedetails.com/cve/CVE-2025-1974/
#IngressNightmare
We also had a mix of versions:
dev: ingress-nginx 4.0.6, but the helm chart is not detected. staging: ingress-nginx 4.5.2
prod: ingress-nginx 4.10.1
We now deploy the prod version everywhere to test the pipeline and the chart. Then we update to the most recent ingress-nginx version.
Use the name ecamp3-ingress that it is clear that it's more than the official chart.
(We add some of our own configuration).
But that the existing services keep their name and thus might keep their ip, we set fullnameOverride, that the LoadBalancer name does not change.