Skip to content
This repository has been archived by the owner on Oct 24, 2023. It is now read-only.

Health Probe from Azure Load balancer causes handshake error #804

Closed
marty2bell opened this issue Jan 24, 2018 · 6 comments
Closed

Health Probe from Azure Load balancer causes handshake error #804

marty2bell opened this issue Jan 24, 2018 · 6 comments
Labels

Comments

@marty2bell
Copy link

Is this a request for help?: NO


Is this an ISSUE or FEATURE REQUEST? (choose one): ISSUE


What version of acs-engine?: v0.10.0


Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)

Kubernetes 1.6.6

What happened:

Azure load balancer uses a TCP based Health Probe on port 443 to check availability of the master nodes within the cluster. This causes the following in the api server logs:

{"log":"I0124 15:46:58.711408 1 logs.go:41] http: TLS handshake error from 168.63.129.16:59087: EOF\n","stream":"stderr","time":"2018-01-24T15:46:58.711746619Z"}

What you expected to happen:

Probe does not cause errors to be generated in the logs

How to reproduce it (as minimally and precisely as possible):

Create a cluster with a acs-engine template

Anything else we need to know:

Similar issue resolved on AWS...

kubernetes-retired/kube-aws#604

@JunSun17
Copy link
Contributor

Did some research on this, and according to current Azure LB documentation, it does not support the ssl protocol as AWS:

https://docs.microsoft.com/en-us/azure/templates/microsoft.network/loadbalancers#ProbePropertiesFormat

So looks we can either open a non-secure port for healthz check (not sure about the security implications) or we will need Azure LB to implement the health probe feature with ssl.

@danmassie
Copy link
Contributor

This is still an issue on aks-engine but this issue has not been ported over.

@mboersma mboersma transferred this issue from Azure/acs-engine Mar 20, 2019
@welcome
Copy link

welcome bot commented Mar 20, 2019

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it.

@jackfrancis
Copy link
Member

@danmassie can you provide a repro using a recent version of k8s/aks-engine? thanks!

@stale
Copy link

stale bot commented May 20, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label May 20, 2019
@stale stale bot closed this as completed May 27, 2019
@itzikstein
Copy link

we still have this issue on Kubernetes 1.14.1 . deployed with AKS-engine version 0.37.0

I0822 14:09:09.554030 1 log.go:172] http: TLS handshake error from 168.63.129.16:50686: EOF I0822 14:09:09.554128 1 log.go:172] http: TLS handshake error from 168.63.129.16:50685: EOF

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants