Closed lemaral closed 4 months ago
It's hard to say what is wrong without seeing the full config, but kube_proxy
blocks are certainly supported (we use them also). Maybe there is an unclosed brace somewhere that is putting the kube_proxy
block at an unexpected level?
Thanks for confirming, it was in the networking block indeed.
(First of all, I must say that I'm very happy that this provider is getting an afterlife thanks! :) I am using cilium cni and would like to replace kube_proxy with cilium's nodeport as documented here: https://kops.sigs.k8s.io/networking/cilium/#enabling-bpf-nodeport However when I try to declare the kube_proxy block, the kops provider does not recognise it:
When I disable kubeProxy using the kops cli, terraform plan is showing this diff
What's missing?