You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This morning i noticed a information banner when looking at an older aks dev cluster (v1.18.14), in the portal. It warned me that the cluster cert was going to expire in 87 days, and i needed to manually rotate the cert.
I had successfully rotated a clusrer cert only a couple of months ago on a slightly younger cluster, i think it wss v1.22.x) and did not have any issue... took about 30 mins to complete so continued.
This time i was not so lucky! Started the rotation via the az cli... it was still sat at tye spinning Running prompt 2-3 hours later.
It seems to have replaced the api certs ok as i can refresh my kubctl connection details and query the cluster objects, but the nodes are not starting back up... i have 2 node pools both with no runnibg nodes.
I have a niggling suspision that when it recreats the nodes ir can no longer find the node image version 1.18.14 as it is no longer a supported version.
The cluster is/was a n old dev cluster, I was actually in the middle of building out a shiny new cluster to replace, but could really do with this one back whilst i continue to work on the new one
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This morning i noticed a information banner when looking at an older aks dev cluster (v1.18.14), in the portal. It warned me that the cluster cert was going to expire in 87 days, and i needed to manually rotate the cert.
I had successfully rotated a clusrer cert only a couple of months ago on a slightly younger cluster, i think it wss v1.22.x) and did not have any issue... took about 30 mins to complete so continued.
This time i was not so lucky! Started the rotation via the az cli... it was still sat at tye spinning Running prompt 2-3 hours later.
It seems to have replaced the api certs ok as i can refresh my kubctl connection details and query the cluster objects, but the nodes are not starting back up... i have 2 node pools both with no runnibg nodes.
I have a niggling suspision that when it recreats the nodes ir can no longer find the node image version 1.18.14 as it is no longer a supported version.
The cluster is/was a n old dev cluster, I was actually in the middle of building out a shiny new cluster to replace, but could really do with this one back whilst i continue to work on the new one
Any help/ advice would be kindly appriciated 🙏👍
Beta Was this translation helpful? Give feedback.
All reactions