Replies: 1 comment 10 replies
-
|
Hi, I really suggest you remove the old instance types by following this migration guide https://vitobotta.github.io/hetzner-k3s/Upgrading_a_cluster_from_1x_to_2x/. The guide was written for moving from the old v1.x version, but most of it will help you too if you still have the instance type in your instance names. After this migration, the instance names won't include the instance type anymore. This lets you change the instance type for existing ones whenever you need to, without causing any problems or risking damage to the cluster when you run the create command again. |
Beta Was this translation helpful? Give feedback.
10 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey all,
I have the situation that I created a 3-node cluster with 2.0.8 in September last year with CX32 VM sizes.
Nowadays, these don't seem to be available anymore (for multiple months already, at least), neither are the similar ones. Because of that, I'm rather careful changing something for the cluster as re-creating it would be substantially (!) more expensive.
Given that, I seem to have lost access to the cluster - probably because the access certificate expired after a year. The applications itself continue to work (all services still reachable), but no new deployments and no kubectl. How would I best fix the access?
As I understand it, upgrading k3s version would rotate the certs anyway, yet that - to my knowledge - would require temporarily adding more nodes - which would not work as that VM size is no longer available.
Help would be greatly appreciated :) Thanks!
Beta Was this translation helpful? Give feedback.
All reactions