Document removal of service field LoadBalancerIP #743
Description
Starting from Kamaji edge-25.3.2, the service field LoadBalancerIP from service spec is no more supported as it is deprecated from kubernetes. See #713
To force a Tenant Control Plane getting a specific IP address, you have to leverage on the specific LoadBalancer solution of choice. For example, with MetalLB you should use the annotation:
apiVersion: kamaji.clastix.io/v1alpha1
kind: TenantControlPlane
metadata:
name: k8s-130
labels:
tenant.clastix.io: k8s-130
spec:
controlPlane:
deployment:
replicas: 2
service:
serviceType: LoadBalancer
additionalMetadata:
annotations:
metallb.universe.tf/loadBalancerIPs: 172.18.255.104 <<<<<<
kubernetes:
version: "v1.30.0"
kubelet:
cgroupfs: systemd
networkProfile:
address: 172.18.255.104 <<<<<
port: 6443