Closed ialejandro closed 1 year ago
A bit tricky to determine exactly what you are asking here, but:
A bit tricky to determine exactly what you are asking here, but:
* When you run K8s 1.24 and above, CCM is mandatory. * When you use CCM, resource-based naming is mandatory.
That's it. That's what I needed to know. Regards! :)
Hi,
I open this issue, but I'm sure it's my fault (not a bug). I've a problem when I upgrade from kOps 1.24.3 to 1.25.3 and upgrade my cluster from 1.23.13 to 1.24.10.
Currently:
So, @olemarkus in this issue (#14035) you say:
In another issue (#13934) you say:
So, If don't put
cloudControllerManager: {}
inspec
section I can't upgrade. This param is required.More info, I checked the
hostname
on my nodes:And node info (from Lens):
From my AWS console, I review my subnet config and
IP name
is selected. (https://cloud-provider-aws.sigs.k8s.io/prerequisites/)But, is possible upgrade to 1.24.10 (k8s) and 1.25.3 (kOps) without CCM? Because I'll try some configs and I can't evict CCM deployed. So, any doc about that? I checked kOps CRD kops.k8s.io_clusters.yaml#L546-L651 about
cloudControllerManager
but nothing. I would like keep the old name (aws ip private dns name) and don't use the AWS ID nomenclature.My applied kOps cluster spec config:
I only added this new lines: