keep getting ssh handshake errors notifications #1403
-
Hi Everyone I have been using Flux with Multi cluster setup with single repository. My requirement was to make sure all the environments have the similar configurations as everything identical in each and every cluster. I need to mention that everything is perfectly working and I don't see any reconcile issues or failure to update the changes made to the repo to the system. But I have enabled the Slack Notification and I'm keep getting this ssh authentication error and I can't find the issue behind that, but no issues or failures reported and everything is working as expected. Frequency, between these notifications is around 15 minutes. Why I'm keep getting this notification? I really appreciate if you can help me to understand the issue or fix any issues I have. here is the snap of my Slack Channel. I'm pretty confused 🤔🤯 |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
Can you please post here the output of:
|
Beta Was this translation helpful? Give feedback.
-
Thank you for the response @stefanprodan Actually, I checked the error logs of the source controllers in each and every environments and found that the dev environment source controller is having the issue. This dev environment was deployed using a separate branch in my main repo while all other prod environments deployed through the master branch. Could that be a problem? Here is the output you requested
BTW, I retried to deploy it in to the cluster and did see the below output and the error:
Definitely, there is an error and what could be the breaking point of this. We didn't change anything in the Flux deployments other than the application manifest updates which needed in the dev environment. Thanks. |
Beta Was this translation helpful? Give feedback.
-
I think now my clusters are pretty much stable. I have upgraded the CLI to v0.13 as informed by @stefanprodan and tried to upgrade the controllers using the same bootstrap command I used to deploy. The controllers which were having issues didn't work and failed the upgrade throwing the same ssl handshake error while others successful the bootstrapping command. For the failed controller upgrades (Which were having issues), I had to uninstall completely and redeployed with the same bootstrap commands. It's been a while now and my entire environment is stable. I think we are all good and @stefanprodan thank you for the response. |
Beta Was this translation helpful? Give feedback.
I think now my clusters are pretty much stable. I have upgraded the CLI to v0.13 as informed by @stefanprodan and tried to upgrade the controllers using the same bootstrap command I used to deploy. The controllers which were having issues didn't work and failed the upgrade throwing the same ssl handshake error while others successful the bootstrapping command. For the failed controller upgrades (Which were having issues), I had to uninstall completely and redeployed with the same bootstrap commands. It's been a while now and my entire environment is stable. I think we are all good and @stefanprodan thank you for the response.