loadBalancerBackendPort - health check #1513
Description
/kind bug
Hello, we have case where we want to use different loadBalancerBackendPort, but if I define different port, e.g.:
apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
kind: GCPCluster
metadata:
name: capi-gcp
namespace: capi-gcp
spec:
loadBalancer:
loadBalancerType: InternalExternal
network:
name: private-vpc-k8s-capi
autoCreateSubnetworks: false
loadBalancerBackendPort: 443
CAPG creates health check with default port 6443 and it's not possible to change it in cluster definition (I could change it through console).
It should be great if I define loadBalancerBackendPort it will be used for all port definitions which I need.
What steps did you take and what happened:
Try to change default API port.
What did you expect to happen:
Will be used right loadBalancerBackendPort from manifest.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
- Cluster-api version: v1.9.4
- Kubernetes version: (use
kubectl version): 1.32 - OS (e.g. from
/etc/os-release): Ubuntu 24.04.2 LTS