Skip to content

AL2023 userdata should include a default NodeConfig? #226

@kevincantu

Description

@kevincantu

Describe the Bug

Maybe I'm missing something from my AMI or my cluster that would make this redundant, but shouldn't the userdata_al2023.tpl template just include an additional block like this?

--//
Content-Type: application/node.eks.aws

---
apiVersion: node.eks.aws/v1alpha1
kind: NodeConfig
spec:
  cluster:
    name: ${cluster_name}
    apiServerEndpoint: ${cluster_endpoint}
    certificateAuthority: ${certificate_authority_data}
    cidr: ${cluster_cider}

Expected Behavior

I hoped that a NodeConfig would exist somewhere that let my AL2023 nodes join my cluster without having to define a custom userdata_override_base64 from scratch containing the above.

Steps to Reproduce

In a config which does set the before_cluster_joining_userdata, enable ami_type = "AL2023_x86_64_STANDARD" and a custom AL2023 based AMI, without setting that userdata. Observe nodes not reach the cluster.

Screenshots

No response

Environment

No response

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug🐛 An issue with the system

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions