Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add healthcheck protocol choice on APISpec for loadbalancers #17145

Open
yelaissaoui opened this issue Dec 17, 2024 · 0 comments
Open

Add healthcheck protocol choice on APISpec for loadbalancers #17145

yelaissaoui opened this issue Dec 17, 2024 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@yelaissaoui
Copy link

yelaissaoui commented Dec 17, 2024

/kind feature

1. Describe IN DETAIL the feature/behavior/change you would like to see.
In Kubernetes v1.30, some ciphers used by AWS SSL healthcheck for the CLB are now classified as insecure by the kube-apiserver, the healthcheck fails as it's using SSL and the Controlplane is considered out-of-service by the Loadbalancer.
If we change the healthcheck protocol manually to TCP, it works.
Today, Kops only uses SSL as a healthcheck protocol for CLB.

-> Is it possible to add the choice of healthcheck protocol used on the loadbalancer generated by Kops ?

2. Feel free to provide a design supporting your feature request.
Example of configuration on the kops cluster :

   api:
      loadBalancer:
        class: Classic
        type: Internal
 +      healthcheck: (TCP|SSL|..)
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 17, 2024
@yelaissaoui yelaissaoui changed the title Add health check choice on APISpec for loadbalancers Add healthcheck protocol choice on APISpec for loadbalancers Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants