Sendhil Murugan Ramasamy

Further investigation into Kubernetes events, reveals the following errors: LAST SEEN TYPE REASON OBJECT MESSAGE 94m Warning Unhealthy pod/hnc-controller-manager-64d99b7477-997jr Readiness probe failed: Get "http://10.42.0.168:8081/readyz": context deadline exceeded (Client.Timeout exceeded while...

Thank you @adrianludwin - I will make the change manually to the deployment to test it and get back shortly.

I had to reset the entire cluster (Rancher Desktop for Mac M1 was failing but that is another story). Downloaded the default.yaml file for v1.0.0, modified the ports for Deployment...

I was finally able to fix it temporarily by increasing the timeoutSeconds for the probes. Please see the attached txt file (extract of the full default.yaml file and renamed to...

I am getting plenty of the TLS Handshake errors at the moment {"level":"error","ts":1668621256.7364924,"msg":"http: TLS handshake error from 10.42.0.1:55474: EOF"} {"level":"error","ts":1668621256.9407673,"msg":"http: TLS handshake error from 10.42.0.1:55488: EOF"} {"level":"error","ts":1668621257.1366735,"msg":"http: TLS handshake error...

> Odd that there's a ~13m period where it appears to be healthy. When the pod restarts, how long does it stay up for? After manually increasing the timeout settings,...

@florath Did you change the timeout settings like I did earlier? by editing the default.yaml file? Because for me that timeout essentially removed the error that you get `Internal error...

> No - I did not change the timeout. Got the documented errors from first / plain install. @florath Would you mind downloading the original default.yaml file from the HNC...

> Just one quick question - does this have anything to do with the load on the apiserver? There was some comment that made me wonder if the webhooks were...

@florath - Will test today and report back. Maybe giving 3000Mi is a bit too high. I will test a few sizes - starting with doubling the current sizes of...