Remove epoxy and support s2i containers - #437
Conversation
This patch is removing the epoxy jobs as the main branch is intended to support only deployments from recent branches (goal is hibiscus). Signed-off-by: Alfredo Moralejo <amoralej@redhat.com>
This patch is introducing a new defaulting variable RELATED_IMAGE_WATCHER_BASE_URL_DEFAULT which, when used, defines the default container image for the three watcher service. Otherwise the pre-existing logic is maintained. Default value is empty so that the default behavior will be changed later. I'm setting kuttl jobs to use new S2I container. Switch for master deployment job will be done as follow up. Signed-off-by: Alfredo Moralejo <amoralej@redhat.com>
Watcher is moving to a single container image to all the services. This patch is modifying the defaulting logic and environment variable used to set the default images in OpenStackVersion for the Watcher services. Depends-On: openstack-k8s-operators/watcher-operator#437 Signed-off-by: Alfredo Moralejo <amoralej@redhat.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Zuul encountered a syntax error while parsing its The key "cifmw_test_operator_tempest_image_tag" appears more than once; duplicate keys are not permitted. cifmw_repo_setup_branch: master in "openstack-k8s-operators/watcher-operator/.zuul.yaml@main", line 184 |
|
Build failed (check pipeline). Post ✔️ openstack-meta-content-provider-master SUCCESS in 3h 29m 28s |
| name: opendev-master-watcher-operator-pipeline | ||
| github-check: | ||
| jobs: | ||
| - openstack-meta-content-provider-master |
There was a problem hiding this comment.
so this shoudl get replaced wit the stadnard content provder
and we shoudl add the newo s2i content provder as well in a follow up
before we do that we will need to update the kuttl jobs to use the new content provdier and the related images as well .
There was a problem hiding this comment.
Note the kuttl jobs is already using the s2i as it just uses the default from the operator.
There was a problem hiding this comment.
oh good point it is but its not using the images build by the content proivder
i actully think that was true before however so that out of scope for now.
i dont think we currently render openstack-versions in the cluster it uses in the ci job to repoitn it but using them for quay.io for now is more then good enouch
we are testing the operator not the the service in kuttle primarally
There was a problem hiding this comment.
Exactly, that was the reason to use that when we initially created the kuttl test.
|
Build failed (check pipeline). Post ✔️ openstack-meta-content-provider-master SUCCESS in 1h 43m 00s |
|
check-rdo |
|
Build failed (check pipeline). Post ✔️ openstack-meta-content-provider-master SUCCESS in 1h 42m 13s |
This patch is moving to deploy watcher using the s2i containers from upstream openstack-k8s-operators project. Also the tempest container from s2i is used. For the rest of containers it still uses the containers coming from the provider job. We need to update the openstackversion as the last post_deploy action or the openstackversion is reverted to the previous value at a later stage. We will be able to do this better once we have proper support for s2i in the ci tooling. Co-Authored-By: Chandan Kumar (raukadah) <raukadah@gmail.com> Signed-off-by: Alfredo Moralejo <amoralej@redhat.com>
|
/test functional |
|
CI job used the s2i images for watcher, see https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/logs//44d/rdoproject.org/44db94215a3b408bbac992fbbdf69e37/controller/ci-framework-data/logs/openstack-must-gather/quay-io-openstack-k8s-operators-openstack-must-gather-sha256-e951c596b1c06e42cc41260bfe9b929fa850a06bae1d25cda4a1289fdbebaf5b/namespaces/openstack/crs/watchers.watcher.openstack.org/watcher.yaml We could make this better without post_deployment hooks once openstack-k8s-operators/ci-framework#4099 is merged or once everything is moved to s2i. |
viroel
left a comment
There was a problem hiding this comment.
Looks good, we can improve later once we get some updates working in ci-framework
| chdir: "{{ watcher_repo }}" | ||
| script: make stop_watcher_integrated | ||
| - name: Install Watcher Operator in standalone mode | ||
| vars: |
There was a problem hiding this comment.
Are these vars still needed?
There was a problem hiding this comment.
We'll need to redo all that code once we have new provider jobs able to rebuild the s2i service operators on the fly which is WIP. Until that exist, this will be unused code, but i think it's good to keep as trace or the kind of operations we need to do.
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
5715956
into
openstack-k8s-operators:main
It's adding a new variable RELATED_IMAGE_WATCHER_BASE_IMAGE_URL_DEFAULT for the new s2i unified image and setting it for kuttl job.
It's also removing epoxy job from main branch.