Question: Konnectivity Server NodePort configuration issue

[dwon-kim]

Description

I noticed that when ServiceType is NodePort, the Konnectivity Server's NodePort is explicitly set to KonnectivityServerSpec.Port (default: 8132):

https://github.com/clastix/kamaji/blob/master/internal/resources/konnectivity/service_resource.go#L153-L155

if tenantControlPlane.Spec.ControlPlane.Service.ServiceType == kamajiv1alpha1.ServiceTypeNodePort {
    r.resource.Spec.Ports[1].NodePort = tenantControlPlane.Spec.Addons.Konnectivity.KonnectivityServerSpec.Port
}

Questions

1. NodePort range issue: The default port 8132 is outside the Kubernetes default NodePort range (30000-32767). Does this mean users must modify --service-node-port-range on the API server to use Konnectivity with NodePort service type?

2. Design intention: What is the reason for explicitly setting the NodePort instead of letting Kubernetes auto-assign one from the default range? Is it to ensure a predictable port for Konnectivity Agent connections?

3. Recommended configuration: What is the recommended approach for using Konnectivity with NodePort service type? - Extend the NodePort range to include 8132?

• Change KonnectivityServerSpec.Port to a value within 30000-32767?
• Or is there another recommended approach?

Environment

• Kamaji version: v1.0.1
• Using with: cluster-api-control-plane-provider-kamaji

Thank you!

[prometherion]

@dwon-kim I converted this entry into a Discussion item since Issues are used only for bug reporting.

1. The NodePort support is there for those users having issues in getting a LoadBalancer available, or for any other specific need. We decided to opt for a Configuration over Convention approach: we can't know in advance the available port range from Kubernetes, and it would require more logic to extract such a port. If you must use such a kind of Service, you have to override the default port from 8132 to any of one of the available higher ranges, as you're expected with the API Server port.
2. The konnectivity port must be known in advance since it's going to be referenced by the Konnectivity Agent
3. You have to configure a higher port from the TenantControlPlane specification, although the most preferred option is relying on a LoadBalancer implementation

Last but not least, we're not supporting v1.0.0 releases anymore. You should use edge versions, which have maintained code, from which we cut off stable releases available behind a subscription plan.