-
Notifications
You must be signed in to change notification settings - Fork 35
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
Added task to wait for GitOps plugin activation #473
base: main
Are you sure you want to change the base?
Conversation
Build succeeded. ✔️ dci-rpm-build-el8 SUCCESS in 2m 43s |
from change #473: |
0af897c
to
77e536d
Compare
Build succeeded. ✔️ dci-rpm-build-el8 SUCCESS in 2m 45s |
from change #473: |
I think you need to take a look at the condition you're defining in the new task because it's not working fine:
|
77e536d
to
ac7bfb7
Compare
Build succeeded. ✔️ dci-rpm-build-el8 SUCCESS in 2m 41s |
from change #473: |
@@ -208,6 +208,22 @@ | |||
.dockerconfigjson: "{{ _czga_encoded_pull_secret['content'] }}" | |||
no_log: true | |||
|
|||
- name: Wait for the GitOps ZTP plugin activation | |||
community.kubernetes.k8s_info: | |||
api_version: v0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
v1 instead of v0?
ac7bfb7
to
7172253
Compare
Build succeeded. ✔️ dci-rpm-build-el8 SUCCESS in 2m 46s |
SUMMARY
In order to run ZTP spoke cluster deployments, the OpenShift GitOps operator must be complemented with the ztp site generator plugin.
The plugin is enabled through the argocd CR in the hub cluster.
Upon updating the CR, the openshift-gitops-repo-server deployment is updated with the mounted volume containing the new kustomize configuration.
This task involves pulling two images to run as initContainers to the repo server pod.
The problem is the pulling of the images may take too much time in disconnected networks, causing the job to time out while waiting for the deployment to start.
This PR adds a tasks that waits for the repo server container to be updated before the role creates the GitOps applications, so once the application is created the job may move directly to the deployment stage.
ISSUE TYPE
Tests
TestBos2: bevo/acm-hub bevo/ztp-spoke-4.15