-
Notifications
You must be signed in to change notification settings - Fork 637
Closed
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.needs-priorityneeds-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.
Description
/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
I deployed an AWS Managed Machine Pool and tried to specify and AWS launch template with amiType: AL2023_x86_64_STANDARD on EKS 1.33.
apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
kind: AWSManagedMachinePool
metadata:
name: eks-pool0
namespace: capa
spec:
eksNodegroupName: pool0
scaling:
minSize: 1
maxSize: 2
amiType: AL2023_x86_64_STANDARD
awsLaunchTemplate:
instanceType: m7i.4xlarge
instanceMetadataOptions:
httpPutResponseHopLimit: 2
I got the following error:
Failed to reconcile launch template:
failed to get ami SSM parameter:
"/aws/service/eks/optimized-ami/1.33/amazon-linux-2/recommended/image_id": ParameterNotFound:
What did you expect to happen:
No error
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
These values seems hardcoded here https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/pkg/cloud/services/ec2/ami.go#L80-L87 and called from https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/pkg/cloud/services/ec2/ami.go#L328
Environment:
- Cluster-api-provider-aws version: 2.8.2
- Kubernetes version: (use
kubectl version): 1.33 - OS (e.g. from
/etc/os-release):
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.needs-priorityneeds-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.