Support loadbalancing endpoints

[jayunit100]

Looks like in https://github.com/kubernetes/kubernetes/issues/18174 theres alot of churn around the fact that we cant loadbalance APIServers for client-go.

Can we support this ? i.e.

change

type Config struct {
	Host string

to something like this?

type Config struct {
        // for backward compatibility
        Host string 
	// Hosts must be  an array of  host strings, a host:port pair, or a URL to the base of the apiserver.
	Hosts []string

[jayunit100]

/good-first-issue

[MadhavJivrajani]

Hi!

I'd like to work on this :smile:

/assign

[jayunit100]

@MadhavJivrajani i guess the first step might be to see if you can hack it together, and then figure out who owns client-go and what SIG you need to go to to talk about this , and wether a KEP is needed to follow up

thanks

[enj]

https://github.com/kubernetes/kubernetes/issues/18174#issuecomment-821991466 /remove-good-first-issue /sig api-machinery

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

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

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[MadhavJivrajani]

/remove-help

[MadhavJivrajani]

/remove-lifecycle rotten /lifecycle frozen

[enj]

https://github.com/kubernetes/kubernetes/issues/18174#issuecomment-1218046238

There are no plans to address this.

/close

[k8s-ci-robot]

@enj: Closing this issue.

In response to this:

https://github.com/kubernetes/kubernetes/issues/18174#issuecomment-1218046238

There are no plans to address this.

/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.