KCP: support pluggable proxy providers

[ncdc]

User Story

As a user, I would like to create a new cluster using a proxy provider of my choosing, instead of having kubeadm install kube-proxy, because I'd like to use something other than kube-proxy from the start.

As a user, I would like to manage my proxy provider separately from KCP, decoupling their lifecycles, so that I'm in control of my proxy provider.

Detailed Description

See user stories

Anything else you would like to add:

kubeadm is currently responsible for installing kube-proxy and we'll need to be able to disable that.

/kind feature
/milestone Next

[neolit123]

the current way is by passing --skip-phase=addons or a specific addons/x.
but i guess for CAPI this has to be supported via the config:
kubernetes/kubeadm#2261

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fabriziopandini]

/lifecycle frozen

[vincepri]

/assign @fabriziopandini
/milestone v1.1

[randomvariable]

/area control-plane

[vincepri]

/priority backlog

[fabriziopandini]

/unassign

[fabriziopandini]

/triage accepted

/help

[k8s-ci-robot]

@fabriziopandini:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/triage accepted

/help

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.

[sbueringer]

kubeadm is currently responsible for installing kube-proxy and we'll need to be able to disable that.

@fabriziopandini I think this is possible today via: controlplane.cluster.x-k8s.io/skip-kube-proxy

Not sure if this covers the entire issue.

[fabriziopandini]

I have to dig into this, but on top of my mind what we have now isn't a clean API because you have to use phases to skip addon installation and then use the annotation above to avoid errors on upgrades.
But you are right, this can be achieved now; let's keep this open to see if we gather ideas about if and how we should improve the UX

[sbueringer]

Oh you're right. Same for CoreDNS

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[fabriziopandini]

The Cluster API project currently lacks enough active contributors to adequately respond to all issues and PRs.

We already have skip-proxy annotation that allows to achieve something similar, but considering that there is no demand and the issue is not updated since 2022, I don't see this making progress anytime soon

/close

[k8s-ci-robot]

@fabriziopandini: Closing this issue.

In response to this:

The Cluster API project currently lacks enough active contributors to adequately respond to all issues and PRs.

We already have skip-proxy annotation that allows to achieve something similar, but considering that there is no demand and the issue is not updated since 2022, I don't see this making progress anytime soon

/close

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.