Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrating OLM testing pipeline from concourse to github-action #1569

Merged
merged 15 commits into from
Mar 7, 2024

Conversation

DanielePalaia
Copy link
Contributor

@DanielePalaia DanielePalaia commented Feb 26, 2024

This PR is part of the task to migrate our Concourse pipelines to github actions:

It is migrating the OLM pipeline in order to test our OLM bundle in the cluster-operator:
https://github.com/pivotal/rabbitmq-for-kubernetes-ci/blob/main/pipelines/olm-bundles/pipeline.yml

it can be useful to have a look to this guideline in order to see how to create and publish an OLM bundle:
https://devopstales.github.io/home/oml/

The test images are stored in the environment variable specified in:
DOCKER_REGISTRY_SERVER: quay.io/rabbitmqoperator
OLM_IMAGE: rabbitmq-for-kubernetes-olm-cluster-operator
OLM_INDEX_IMAGE: rabbitmq-for-kubernetes-olm-cluster-operator-index

The action is always testing the latest cluster operator manifest (the last tagged version).
In case we run the action manually (through a workflow_dispatch) a generic 0.0.0 tag version is generated.

The cluster operator is deployed and configured in order to watch just on "rabbitmq-system-olm" namespace so that the K8s cluster can be shared with the action which is testing the deployment using the carvel Package Repository (which is deploying the cluster operator and watching in the default "rabbitmq-system" namespace)

The lock is needed in order to share the cluster with the future messaging topology operator action.

The create-olm-package job is a bit confusing and overcomplicated but this will be improved when we will improve the conversion bundle script in python.

The new action and the old publishing action (openshift.yml) have been merged together.

Action result here: https://github.com/rabbitmq/cluster-operator/actions/runs/8052246499

Manifests are uploaded here:
https://github.com/rabbitmq/community-operators (operator-hub)
https://github.com/rabbitmq/community-operators-prod (openshift-marketplace)

Then a manual PR to openshfit repos is needed

@DanielePalaia DanielePalaia marked this pull request as draft February 26, 2024 10:05
@DanielePalaia DanielePalaia changed the title Testing olm Migrating OLM testing pipeline from concourse to github-action Feb 26, 2024
@DanielePalaia DanielePalaia marked this pull request as ready for review February 27, 2024 09:02
@DanielePalaia DanielePalaia force-pushed the testing_olm branch 2 times, most recently from 6466949 to c117a1f Compare March 1, 2024 13:24
@DanielePalaia
Copy link
Contributor Author

Taking in account Aitor review here: rabbitmq/OLM-Package-Repo#8

@DanielePalaia DanielePalaia force-pushed the testing_olm branch 6 times, most recently from 4bb681e to 6bb0446 Compare March 6, 2024 11:07
@DanielePalaia
Copy link
Contributor Author

I replaced git clone with checkout actions here too like suggested here: rabbitmq/messaging-topology-operator#767. I will merge this one now to test it on the next operator release. We can come back with improments here when we improve the OLM Packaging script

@DanielePalaia DanielePalaia merged commit 082df72 into main Mar 7, 2024
15 checks passed
@DanielePalaia DanielePalaia deleted the testing_olm branch March 7, 2024 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants