Closed yaronshanisima closed 3 months ago
Hi, we had to put a limit on nodepool names (14 characters) and cluster names (28 characters) in the manifest. Since control-hetzner
is 15 characters long you got this error.
Let's check if we can make the errors more descriptive.
@bernardhalas @Despire Hi all! Is it possible to rename existing node pools that has invalid name after update to 0.8.0 without cluster recreation?
Hi @vatroshkin , if the nodepool is dynamic: Add a new nodepool with the correct name (to have sufficient capacity in the cluster). Then remove the old nodepool. If the nodepool you're talking about is static: Add a new dynamic nodepool (to have sufficient capacity in the cluster). Then remove the wrong static nodepool. Then re-add the static nodepool, now with correct name.
Does this help?
@bernardhalas thanks for reply, I have tried that, but the problem that validation complains about name length for an old nodepool 🥲 - so I can't add a new nodepool with a short name
EDIT: If it's possible you could deploy the older Claudie version where there was no restriction on the name length. This way you could perform the changes @bernardhalas described (adding new nodepools with new names and then removing the old nodepool with invalid names), and then You should be able to upgrade back to 0.8.
@Despire Hi! Any suggestion how can I do that? When I apply previous release (kubectl apply -f ...), it stays 0.8.0. Thanks!
applying just kubectl apply -f https://github.com/berops/claudie/releases/download/v0.7.5/claudie.yaml
should work (just tested it by deploying 0.8.0 then applying the command)
with this config
I am getting
Did not happen with the previous Claudie version.
Thanks!