Closed mrsauravsahu closed 2 months ago
The update involves configuration adjustments in the ingress-nginx
chart. A nodeSelector
has been introduced to specify the nodes where the controller should run, enhancing deployment specificity and resource efficiency. Additionally, enableAnnotationValidations
has been set to false
, simplifying the annotation process by reducing validation strictness.
File Path | Change Summary |
---|---|
.../ingress-nginx/values.yaml |
Added nodeSelector under controller with a node label requirement; set enableAnnotationValidations to false . |
🐇✨ In the garden of code, where the data trees grow, A tiny change here, a tweak in the flow. With labels aligned, and validations at rest, Our nginx sails smoothly, on its Kubernetes quest! 🌟🌿
molecules/cluster-resources/config/externals/ingress-nginx/values.yaml (2)
`20-21`: Ensure that all nodes intended for ingress-nginx deployment are correctly labeled with `kubernetes.io/hostname: pi` to match the `nodeSelector` configuration. --- `21-21`: Clarify the rationale for setting `enableAnnotationValidations` to `false`. This setting disables validation of ingress annotations, which could impact the security or functionality of the ingress rules.
pi5 is failing ingress-nginx - since I am using only pi as ingress, no need to have the controller deployed to both nodes anyway for now - using nodeSelector to only deploy to pi
Summary by CodeRabbit