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

Create WatcherAPI service #37

Conversation

cescgina
Copy link
Contributor

@cescgina cescgina commented Jan 14, 2025

Create WatcherAPI service

Create the WatcherAPI service. Adds new fields to the spec related to the service, as well as functional and kuttl tests.

Related: OSPRH-11483

Depends-On: openstack-k8s-operators/ci-framework#2658

@cescgina cescgina force-pushed the create_watcherapi_service branch from bcade20 to 49ed65f Compare January 14, 2025 11:58
@cescgina
Copy link
Contributor Author

/hold we'll integrate watcherapi with the watcher controller before this PR

Copy link

This change depends on a change that failed to merge.

Change openstack-k8s-operators/ci-framework#2658 is needed.

@cescgina
Copy link
Contributor Author

recheck

@cescgina cescgina force-pushed the create_watcherapi_service branch 5 times, most recently from cc708bb to eaa1528 Compare January 17, 2025 16:54
Create the WatcherAPI service. Adds new fields to the spec related to
the service.
Temporary solution to expose the service while the operator is installed
standalone. After we integrate watcher-operator with the
openstack-operator, we'll rely on it to expose the services like the
other do, and this code should be removed.
@cescgina cescgina force-pushed the create_watcherapi_service branch from eaa1528 to cebf135 Compare January 20, 2025 08:28
@cescgina
Copy link
Contributor Author

/hold cancel

@amoralej
Copy link
Contributor

/lgtm we will need to refactor this part of the CRDs once we integrate into openstack-operator.

Use the Override spec field that is used in the other operators, so once
we change the code to expose the services to use the same method used by
the openstack operator, the spec will go through less changes.
Copy link

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/bc592a6603fa4e2dafd500804322a1cf

✔️ noop SUCCESS in 0s
openstack-meta-content-provider POST_FAILURE in 1h 31m 06s
✔️ watcher-operator-validation SUCCESS in 1h 20m 27s
✔️ watcher-operator-kuttl SUCCESS in 34m 27s

@raukadah
Copy link
Contributor

recheck

@raukadah
Copy link
Contributor

/approve

thank you @cescgina! This looks good now. I will start working on enabling watcher tempest plugin api tests in validation job.

Copy link

openshift-ci bot commented Jan 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: raukadah

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@amoralej
Copy link
Contributor

/lgtm

I'd propose to validate key name sin override:service to be internal or public. I'm not sure if it is better to do it in webhooks or in controllerts, tbh.

@openshift-ci openshift-ci bot added the lgtm label Jan 21, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 7466626 into openstack-k8s-operators:main Jan 21, 2025
6 checks passed
@cescgina cescgina deleted the create_watcherapi_service branch January 21, 2025 08:27
@raukadah
Copy link
Contributor

/lgtm

I'd propose to validate key name sin override:service to be internal or public. I'm not sure if it is better to do it in webhooks or in controllerts, tbh.

+1 to use via webhooks. Here is how keystoneapi is validating it https://github.com/openstack-k8s-operators/keystone-operator/blob/main/api/v1beta1/keystoneapi_webhook.go#L124 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants