-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Does KubeadmConfigTemplate support kubeproxy configuration #10237
Comments
This issue is currently awaiting triage. CAPI contributors will take a look as soon as possible, apply one of the Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-kind bug i think the suggested approach is to skip kubeproxy as a kubeadm addon and manage it yourself. i think there was a way to skip the kubeadm addons with an annotation, but i can't find where are the docs for that (currently on mobile) |
There is: see: https://cluster-api.sigs.k8s.io/reference/labels_and_annotations |
xref: #3700 (comment) The annotation only makes capi not handle upgrades for kube-proxy anymore. You would still need to configure kubeadm to skip deploying it or use preKubeadmCommands to adjust things to make the kubeadm way of adding the additional configuration (which I think is very hacky). Other previous issues about this topic: |
/close Answer have been provided, no further feedback |
@fabriziopandini: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I don't want to skip kube-proxy configuration. I want to be able to configure it. KubeAdm allows it. So why doesn't CAPI which uses kubeadm do the same? |
Hacky but works: You could add the kube-proxy config as a file, e.g.:
And have a pre-kubeadmcommand adding it to the kubeadm config file for
|
What steps did you take and what happened?
KudeAdm supports various configuration resources: https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/control-plane-flags/#customizing-kube-proxy
You can see there is a InitConfiguration, ClusterCOnfiguration, Join Configuration, as well as a KubeletConfiguration and KubeProxyConfiguration: https://kubernetes.io/docs/reference/config-api/kubeadm-config.v1beta3/
But when I look at the definition for KubeadmConfigTemplate, only Init/Join/Cluster Configuration is supported:
cluster-api/bootstrap/kubeadm/api/v1beta1/kubeadmconfig_types.go
Line 53 in 22ec35e
How do we go about configuring kube-proxy with CAPI?
What did you expect to happen?
Allow specifying KubeProxyConfiguration in the KubeadmConfigTemplate
Cluster API version
1.5.3
Kubernetes version
1.26
Anything else you would like to add?
No response
Label(s) to be applied
/kind bug
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.
The text was updated successfully, but these errors were encountered: