CAPD requires --anonymous-auth=true for the loadbalancer checks #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Some CIS hardening defaults in k8s-snap break the loadbalancer health checks for CAPD (probably also relevant for other infrastructure providers that provision L7 load balancers, e.g. AWS)
Update the CAPD cluster template to use --anonymous-auth=true on kube-apiserver
Notes
The health check endpoint that capd adds is https://github.com/kubernetes-sigs/cluster-api/blob/6ac336af578367a279018aba03eaedcac83f0e30/test/infrastructure/docker/internal/loadbalancer/config.go#L67
When paired with anonymous-auth, this results in the following error (from
docker logs $cluster-lb
container):Notes part 2
An alternative would be to use a custom haproxy config, but that seems far more complex to maintain (and it is not important for CAPD clusters)