Stéphane MERLE

weekly.ci.jenkins.io as for infra, and as per [jenkins-infra/docker-jenkins-weeklyci#1344 (files)](https://github.com/jenkins-infra/docker-jenkins-weeklyci/pull/1344/files) for jdk17 we need to prepare the docker container image here: https://github.com/jenkins-infra/docker-jenkins-weeklyci

release.ci.jenkins.io as per https://github.com/jenkins-infra/docker-jenkins-lts/pull/772/files for jdk17 we need to prepare the docker container image here: https://github.com/jenkins-infra/docker-jenkins-lts

trusted.ci.jenkins.io, cert.ci.jenkins.io and ci.jenkins.io as per https://github.com/jenkins-infra/jenkins-infra/pull/3018/files for jdk17 we can upgrade all the controller to jdk21 with the same PR on puppet

see plan for migration: https://github.com/jenkins-infra/helpdesk/issues/4121#issuecomment-2890355054

to prepare this, we (jay and I) need to create a specific user for packer-images, as for azure https://github.com/jenkins-infra/azure/blob/main/packer-resources.tf I started creating it in the [aws-sponsored](https://github.com/jenkins-infra/terraform-aws-sponsorship) repository. https://github.com/jenkins-infra/terraform-aws-sponsorship/pull/4 this PR...

the packer user creation was moved to terraform-states hence no more problem of IAM rights

We try to setup our environement to use this new packer user for our run of packer locally. we first tried as infra-developer but we bumped into https://github.com/hashicorp/packer/issues/12110 that seems...

> * Will need to create EC2 resources to allow infra.ci to build VMs and create AMIs from it (check for old packer.tf in jenkins-infra/aws history) nothing about that file...

we plan to use a docker base system as per ci.jio.

as we choose to cancel this migration, lets remove the resources from digital ocean