cluster-api-provider-ibmcloud icon indicating copy to clipboard operation
cluster-api-provider-ibmcloud copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Add a priority listener pool port

Open hamzy opened this issue 1 year ago • 5 comments

/kind feature /area provider/ibmcloud

Describe the solution you'd like [A clear and concise description of what you want to happen.] One way to speed up cluster deployment would be to mark port 22623 for the internal load balancer as a priority. The provider should make sure every VM is added to the pool before working on other pools. Also the bootstrap VM should be added first before other master VMs.

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

hamzy avatar Mar 23 '24 14:03 hamzy

/cc @Karthik-K-N

mkumatag avatar Mar 24 '24 07:03 mkumatag

As of now while reconciling each machine we are trying to attach that machine's IP to all the pools of the loadbalancer (ref).

Currently we dont have any control over reconciling a particular machine over other, the easiest way should be creating bootstrap machine first so it will be reconciled earliest.

Karthik-K-N avatar Mar 28 '24 09:03 Karthik-K-N

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 avatar Jun 27 '24 00:06 k8s-triage-robot

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

k8s-triage-robot avatar Jul 27 '24 00:07 k8s-triage-robot

/remove-lifecycle rotten

mkumatag avatar Aug 06 '24 04:08 mkumatag