We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We deploy the Nginx ingress controller via Ansible and the openshift client with validation enabled.
It discovered that there is an empty (perhaps unnecessary?) default: stanza in the new LimitRange resource definition:
default:
LimitRange
apiVersion: v1 kind: LimitRange metadata: name: ingress-nginx namespace: ingress-nginx labels: app.kubernetes.io/name: ingress-nginx app.kubernetes.io/part-of: ingress-nginx spec: limits: - default: min: memory: 90Mi cpu: 100m type: Container
Could this be removed (or the appropriate defaults specified)? The exact error is:
failed: [my-cluster] (item=../kubernetes/ingress-nginx/mandatory.yaml) => { "ansible_loop_var": "item", "changed": false, "item": "../kubernetes/ingress-nginx/mandatory.yaml" } MSG: LimitRange ingress-nginx: resource definition validation error at spec.limits.0.default: None is not of type 'object'
Thanks!
The text was updated successfully, but these errors were encountered:
@aledbf Many thanks for the quick fix!
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
We deploy the Nginx ingress controller via Ansible and the openshift client with validation enabled.
It discovered that there is an empty (perhaps unnecessary?)
default:
stanza in the newLimitRange
resource definition:Could this be removed (or the appropriate defaults specified)? The exact error is:
Thanks!
The text was updated successfully, but these errors were encountered: