Release for NodeadmConfig CRDs/resources?

[Breee]

Summary

The Docs talk about Nodeadm bootstrap types and CRDs, but the published infrastructure-components.yaml does not appear to include Nodeadm bootstrap resources YET, which makes sense because there is no release that contains them. This blocks AL2023 self-managed worker bootstrap for Kubernetes 1.33+.

What we observed:

Source contains Nodeadm APIs and CRDs, including:

nodeadmconfig_types.go
nodeadmconfigtemplate_type.go
bootstrap.cluster.x-k8s.io_nodeadmconfigs.yaml
bootstrap.cluster.x-k8s.io_nodeadmconfigtemplates.yaml

But they are not packaged in a release yet

This blocks something like:

apiVersion: cluster.x-k8s.io/v1beta1
kind: Cluster
metadata:
  name: hybrid-poc
  namespace: hybrid-poc
spec:
  clusterNetwork:
    pods:
      cidrBlocks:
      - 10.103.0.0/16
  controlPlaneRef:
    apiVersion: controlplane.cluster.x-k8s.io/v1beta2
    kind: AWSManagedControlPlane
    name: hybrid-poc
  infrastructureRef:
    apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
    kind: AWSManagedCluster
    name: hybrid-poc
---
apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
kind: AWSManagedCluster
metadata:
  name: hybrid-poc
  namespace: hybrid-poc
spec: {}
---
apiVersion: controlplane.cluster.x-k8s.io/v1beta2
kind: AWSManagedControlPlane
metadata:
  name: hybrid-poc
  namespace: hybrid-poc
spec:
  eksClusterName: hybrid-poc
  network:
    vpc:
      id: vpc-1
    subnets:
    - id: subnet-1
    - id: subnet-2
  region: eu-central-1
  sshKeyName: capi-poc
  version: v1.34.3
---
apiVersion: cluster.x-k8s.io/v1beta1
kind: MachineDeployment
metadata:
  name: hybrid-poc-md-0
  namespace: hybrid-poc
spec:
  clusterName: hybrid-poc
  replicas: 2
  selector:
    matchLabels: null
  template:
    spec:
      bootstrap:
        configRef:
          apiVersion: bootstrap.cluster.x-k8s.io/v1beta2
          kind: NodeadmConfigTemplate
          name: hybrid-poc-md-0
      clusterName: hybrid-poc
      infrastructureRef:
        apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
        kind: AWSMachineTemplate
        name: hybrid-poc-md-0
      version: v1.34.3
---
apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
kind: AWSMachineTemplate
metadata:
  name: hybrid-poc-md-0
  namespace: hybrid-poc
spec:
  template:
    spec:
      cloudInit:
        insecureSkipSecretsManager: true
      ami:
        eksLookupType: AmazonLinux2023
      iamInstanceProfile: nodes.cluster-api-provider-aws.sigs.k8s.io
      instanceType: t3.large
      sshKeyName: capi-poc
---
apiVersion: bootstrap.cluster.x-k8s.io/v1beta2
kind: NodeadmConfigTemplate
metadata:
  name: hybrid-poc-md-0
  namespace: hybrid-poc
spec:
  template:
    spec: {}

Can you give us an ETA for a new release?

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.