Add way to specify only bootstrap VM should be added to listener pool

kubernetes-sigs / cluster-api-provider-ibmcloud

Cluster API Provider for IBM Cloud

https://cluster-api-ibmcloud.sigs.k8s.io

Apache License 2.0

62 stars 82 forks source link

Add way to specify only bootstrap VM should be added to listener pool #1678

Open hamzy opened 7 months ago

hamzy commented 7 months ago

/kind feature /area provider/ibmcloud

Describe the solution you'd like [A clear and concise description of what you want to happen.] If we say that there should be a listener pool for port 22 , then every VM gets added to the pool In order to debug OpenShift cluster deployments, we need access to the bootstrap VM in order to get log files, etc. Because every VM is added to the pool, we cannot directly ssh into the bootstrap VM.

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Karthik-K-N commented 7 months ago

With current design we create loadbalancer and listener of loadbalancer per cluster and every machine of cluster will be attached to it. May be for now you may need to attach all the vms to listener. We will come up with plan to support attach specific machine to specific listeners as an enhancement in later phases.

k8s-triage-robot commented 4 months ago

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot commented 3 months ago

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

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

/lifecycle rotten

mkumatag commented 3 months ago

/remove-lifecycle rotten

k8s-triage-robot commented 13 hours ago

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

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

/lifecycle stale