|
If you need just a temporary solution to patch your ingress, try this: Get the config map related to your ingress controller $ kubectl get -A cm | grep ingress | grep controller kube-system rke2-ingress-nginx-controller 1 377dEdit the config map by changing allow-snippet-annotations: "false" to allow-snippet-annotations: "true" $ kubectl -n kube-system edit cm rke2-ingress-nginx-controller "/tmp/kubectl-edit-1940673600.yaml" 25L, 910C written configmap/rke2-ingress-nginx-controller editedRetart the controller $ k -n kube-system rollout restart ds rke2-ingress-nginx-controller daemonset.apps/rke2-ingress-nginx-controller restartedIf you want to see the rollout, do kubectl -n kube-system rollout status ds rke2-ingress-nginx-controller Waiting for daemon set "rke2-ingress-nginx-controller" rollout to finish: 0 out of 17 new pods have been updated... Waiting for daemon set "rke2-ingress-nginx-controller" rollout to finish: 1 out of 17 new pods have been updated... [...] daemon set "rke2-ingress-nginx-controller" successfully rolled outAfter you patch your ingress, I suggest to revert the changes, so you'll not be vulnerable by some bad user by adding something that shouldn't be on ingress by patching it. (责任编辑：) |