clusterclass control-plane namingStrategy is not applied about cluster-api-provider-azure HOT 6 OPEN

@thefirstofthe300 Thanks so much for the info! I have been trying to see why this isn't working in CAPZ since they mentioned this working for the VSphere provider. All logic that involves namingStrategy happens in CAPI so it is probably a CAPI issue. @arno-pons would you be able to create an issue in CAPI for this?

from cluster-api-provider-azure.

Hi @arno-pons! Adding the namingStrategy field to the controlPlane spec only applies the strategy to the controlplane resources such as kubeadmcontrolplane. You can specify namingStrategy for your machineDeployments or machinePools workers and the names of the Azure resources should match the namingStrategy.

I just verified this by adding namingStrategy like so:

---
apiVersion: cluster.x-k8s.io/v1beta1
kind: ClusterClass
metadata:
  name: my-cc
  namespace: default
spec:
  workers:
    machineDeployments:
    - class: ${CLUSTER_NAME}-worker
      namingStrategy:
        template: "{{ .cluster.name }}-foo-{{ .random }}"

kubectl get azuremachine shows the following:

NAME                                             READY   SEVERITY   REASON                    STATE   AGE
willie-clusterclass-9406-foo-44xp6-8rn9x         False   Info       Creating                          70s
willie-clusterclass-9406-foo-rb6ps-rpr7f-pj6zt   False   Info       WaitingForBootstrapData           4m33s
willie-clusterclass-9406-foo-rb6ps-rpr7f-xrjnn   False   Info       WaitingForBootstrapData           4m33s

Let me know if this works for you!

from cluster-api-provider-azure.

Hi @willie-yao,

Thanks for you feedback.

My issue is related to the name of control plane azuremachine, not worker ones.
For the worker, we are agree that the namingStrategy at machineDeployments level is working well.

But for controle plane nodes, the only field available for naming strategy, from my understanding, is the spec.controlPlane.namingStrategy.template. And as you say, it seems to apply at kubeadmcontrolplane object level only.

Any idea how to set naming strategy for control plane azure machines/VMs ?

from cluster-api-provider-azure.

I think this might be a CAPI core bug. I just hit this exact same behavior despite using the AWS provider instead.

from cluster-api-provider-azure.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

from cluster-api-provider-azure.

/remove-lifecycle stale

from cluster-api-provider-azure.