Add container config for fedora-image-uploader #2200
No reviewers
Labels
No labels
freeze-break-request
post-freeze
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/ansible#2200
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "jcline-container-uploads"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add a configuration section for uploading containers to registries and the associated authentication.
Not sure if there's a staging registry we want to push to. Also, still need to figure out what format we'll get the authentication (ultimately we probably want to do https://docs.podman.io/en/latest/markdown/podman-login.1.html#authfile-path)
Also, before we merge and deploy this, we need to make sure the other thing doing this gets stopped. See https://pagure.io/releng/issue/12142
Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/419f4a50aa27438a8ced4de9a90cc96d
We do have a candidate-registry for testing stuff. We don't currently use it for these uploads tho, only flatpaks...
Cool. If it's alright to use for testing in stage, I'll add a configuration section for those because I can jump into the staging container and replay a production compose to test things out. Is it just
candidate-registry.fedoraproject.org
?I also need to sit down and get the registry credentials set up - thanks for pointing me to where those are set up at Flock. Hoooopefully this week, but y'know...
There is actually a oci-candidate-registry01.stg.iad2.fedoraproject.org and a oci-registry01.stg.iad2.fedoraproject.org
Those should be just fine to test with in stg.
rebased onto
bd4b5f976d
rebased onto
bd4b5f976d
Okay, I finally got back to this. My ansible skills aren't very good and I decided I didn't want to craft the JSON file produced by podman-login, so I changed the uploader to run
buildah login
on startup. This way we can just pass credentials in as environment variables.I know we talked about the credentials for the various registries at flock but I can't remember their names. I've only configured staging for container uploads and I'm not sure if I'm using the right credentials for that registry. If those all look right this can be merged and deployed any time as it only impacts staging.
Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/ea1b562682a84df78b93df53b293d495
Looks fine to me. We should likely setup a quay.io/fedora/candidate/ or something like that for tests using quay.io (is there any convention?)
I'm not familiar enough to say, unfortunately. Since https://quay.io/organization/fedora seems browse-able and all production things, if quay.io/fedora/candidate maps to something in there I'd say not, but I don't know if it means setting up another org or what.
My assumption is if it pushes to one repo in stage it should probably do the others okay so I don't know if we need a quay.io stage area (it doesn't hurt, but if it's a hassle to set up I'm not too worried about it).
Based on our matrix talk, we can come back to this and move stage to Quay when it's time to get rid of the candidate-registry. Given that this is ready to merge and deploy whenever is convenient for you!
Lets wait until later this week when we are out of freeze and can disable the other thing without a freeze break.
rebased onto
0db90a7f3a
ok, lets merge. ;)
Let me know if you want me to run playbooks.
For staging we aren't doing any container builds/uploads really, so you should be able to test at your leasure.
When we go to prod we will need to comment/stop the cron jobs on compose-x86-01 and comment/remove the calls to the script in pungi-fedora/main and pungi-fedora/41
Pull-Request has been merged by kevin
Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/43f53fd9e38748d8b15139ec9eb8eb6a
If you could run the playbook that'd be great, I'd like to test this out in stage today.
Playbook run on stg.