There is a demo pipeline for forgejo images the source repository is mirrored to github, where the Fedora konflux app is installed and builds on every commit in Konflux.
PostgreSQL Use Software collections PostgreSQL container definition and build it in konflux
Redis Use Software collections Redis container definition and build it in konflux
Images for all components of the Forgejo application are available in quay.io under the fedora-infra namespace published by Konflux pipelines.
Info about the fedora-infra cluster
To get access to the fedora-infra tenant open MR in the gitlab deployment config
Metadata Update from @humaton: - Issue marked as depending on: #7
Metadata Update from @humaton: - Issue assigned to lenkaseg
The fedora-forgejo Dockerfile with fedora:rawhide is building well in konflux, image available on quay.io: https://quay.io/repository/konflux-fedora/fedora-infra-tenant/forgejo-oci-images?tab=tags&tag=5a8671b3858260eef932ae3cf4fa337c6184fa0e
Trying to find the best way to fix the vulnerabilities.
The Redis and Postgres containers should be separate containers hosted in the codeberg.org/fedora/forgejo and have separate components in konflux?
Fixed the vulnerabilities by merging the konflux-suggested PRs. Now there are two components in forgejo-oci-images: - forgejo-oci-images builds from the fedora/forgejo fork - forgejo-oci-images-upsteam builds from upstream forgejo
forgejo-oci-images
Metadata Update from @lenkaseg: - Issue tagged with: high-trouble
Update after meeting with @dkirwan: - Create fedora-helm image - Check tekton docs for helm workflow support
moved to https://codeberg.org/fedora/forgejo-deployment/issues/11
Metadata Update from @ryanlerch: - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.