Add S2I speculative deploy testing for telemetry-operator - #992
Conversation
Implement similar S2I testing workflow as watcher-operator [1] that adds: - s2i-speculative-deploy-test-telemetry job - validates speculatively-built S2I telemetry-operator container images against a live OpenStack deployment with telemetry enabled - s2i-openstack-container-content-provider job - builds S2I containers - Non-voting github-check jobs to validate S2I builds before merging This enables testing whether speculatively-rebuilt telemetry container images function correctly in real deployments. Cloudkitty s2i (cloudkitty/cloudkitty-api) deferred: the cloudkitty deploy path pulls the meta content provider, which conflicts with s2i image injection. Add when a clean deploy path exists. [1] openstack-k8s-operators/watcher-operator#443 Related-To: OSPRH-34558 Assisted-By: Claude Haiku 4.5 <noreply@anthropic.com> Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: danpawlik The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks 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 |
| - name: openstack-k8s-operators/s2i-openstack-containers | ||
| override-checkout: main | ||
| vars: | ||
| cifmw_crc_additional_insecure_registries: |
There was a problem hiding this comment.
add
cifmw_crc_additional_allowed_registries:
- "{{ s2i_content_provider_registry_ip }}:5001"
|
@danpawlik hey Daniel until they get merged, you need depends-on to openstack-k8s-operators/s2i-openstack-containers#91 and openstack-k8s-operators/ci-framework#4131 |
2 participants
Implement similar S2I testing workflow as watcher-operator [1] that adds:
This enables testing whether speculatively-rebuilt telemetry container images function correctly in real deployments.
Cloudkitty s2i (cloudkitty/cloudkitty-api) deferred: the cloudkitty deploy path pulls the meta content provider, which conflicts with s2i image injection. Add when a clean deploy path exists.
[1] openstack-k8s-operators/watcher-operator#443
Related-To: OSPRH-34558
Assisted-By: Claude Haiku 4.5 noreply@anthropic.com