You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Neither the dev or prod clusters are currently vulnerable, because the Validating Admission Controller functionality of ingress-nginx is already disabled, since the helm install options we used included:
--set controller.admissionWebhooks.enabled=false
Double-checking that we don't have a ValidatingWebhookConfiguration called ingress-nginx-admission:
$ kc get ValidatingWebhookConfiguration (☸|prod-k8s:default)
NAME WEBHOOKS AGE
cert-manager-webhook 1 3y147d
However, we're not sure why Peter originally recommended disabling it, and re-enabling it (after we upgrade) "provides important safeguards for your Ingress configurations", so we should consider doing so
Other Info
We upgraded dev-k8s to ingress-nginx v 1.11.4, which was the newest we could go, on K8s v1.26.
The announcement above says 1.11.4 is vulnerable, but 1.11.5 is not. However, it's not clear if K8s v1.26 supports upgrade to ingress 1.11.5 (supported versions table).
We haven't yet upgraded Prod-k8s Kubernetes version, so production ingress is still version 1.0.4
In response to this vulnerability report: https://groups.google.com/g/kubernetes-security-announce/c/2qa9DFtN0cQ - we should upgrade ingress-nginx to v1.11.5 or 1.12.1
Note
Neither the dev or prod clusters are currently vulnerable, because the Validating Admission Controller functionality of ingress-nginx is already disabled, since the
helm install
options we used included:Double-checking that we don't have a ValidatingWebhookConfiguration called ingress-nginx-admission:
$ kc get ValidatingWebhookConfiguration (☸|prod-k8s:default) NAME WEBHOOKS AGE cert-manager-webhook 1 3y147d
However, we're not sure why Peter originally recommended disabling it, and re-enabling it (after we upgrade) "provides important safeguards for your Ingress configurations", so we should consider doing so
Other Info
Useful Background:
The text was updated successfully, but these errors were encountered: