Open dduportal opened 1 month ago
@jayfranco999 works on the Linux AMi part
Update:
https://github.com/jenkins-infra/packer-images/pull/1475 and https://github.com/jenkins-infra/packer-images/pull/1476
tracks the aws AMI ids for ubuntu_22.04
, the solution works when tested locally but fails tests on infra.ci since we need an IAM user for updatecli.
Converted both PRs to draft until IAM updatecli user is created.
Update:
https://github.com/jenkins-infra/kubernetes-management/pull/5837 and https://github.com/jenkins-infra/packer-images/pull/1482 have been merged which adds the aws credentials for the newly created IAM user updatecli
on infra.ci
https://github.com/jenkins-infra/packer-images/pull/1475 and https://github.com/jenkins-infra/packer-images/pull/1476 tracks the aws AMI ids for ubuntu_22.04
for both AMD64
and ARM64
respectively.
All checks have passed for tracking AWS ubuntu_22.04
AMI images
Service(s)
Other
Summary
In packer images, we recently introduced a new YAML file in which we specify and pin the base images for our system: https://github.com/jenkins-infra/packer-images/blob/main/images-versions.yaml.
We want to cover all cloud providers with this file (AWS, Azure, Docker) for all OSes (Linux, Windows) and all versions/architectures.
AWS
amd64
andarm64
in https://github.com/jenkins-infra/packer-images/blob/6f5b55030bdaf528c7b5326085f420409e570531/locals.pkr.hcl#L13-L18 and it's used by thebuild-jenkins-agent-ubuntu
file. However, we want to use https://github.com/jenkins-infra/packer-images/blob/6f5b55030bdaf528c7b5326085f420409e570531/images-versions.yaml#L13-L17 instead.updatecli
job in infra.ci for packer-images (might already be done)Note for Windows: not implemented for AWS yet so not needed in this issue (see https://github.com/jenkins-infra/helpdesk/issues/4318)
Azure
latest
Docker
ubuntu:22.04@sha256:xxxxxxx
Reproduction steps
No response