[Features]Request for Feature to Disable Port Allocation by setting helm chart value

[ian-hui]

What is the user interaction of your feature? We are proposing a feature that introduces a toggle or switch, enabling users to enable or disable the port allocation feature. This would provide users with the necessary control by setting like --set portAllocation=false in helm chart value to ensure that pods with portAllocation=false remain unaffected by any future updates to the port allocation strategy in Kubeblocks.

Is your feature request related to a problem? Our component does not utilize the port allocation feature provided by Kubeblocks. We have implemented our own network configuration that is independent of this feature. However, the presence of the Kubeblocks port allocation feature could potentially interfere with our current setup, leading to conflicts.

[nayutah]

@iziang It seems that when kb updated from older version, the pre-allocated hostnetwork port will get changed due to the latest hostnetwork port allocation feature. A feature gate is nice to have when a cluster dominates a "Node" and no other Pods get scheduled onto it.

[iziang]

@ian-hui what's the older and newer version of kb are you using?

[weicao]

Kuaishou uses hostnetwork but doesn't require KubeBlocks to allocate ports. Therefore, we shall provide a switch for Kuaishou to turn off the port allocation. btw, it won't cause Pods to restart.

[ian-hui]

Kuaishou uses hostnetwork but doesn't require KubeBlocks to allocate ports. Therefore, we shall provide a switch for Kuaishou to turn off the port allocation. btw, it won't cause Pods to restart.

I realized I had a misinterpretation of the information earlier. Thank you for the correction.

[github-actions[bot]]

This issue has been marked as stale because it has been open for 30 days with no activity