-
Notifications
You must be signed in to change notification settings - Fork 26
Create watcherapi keystone endpoint #46
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 keystone endpoint #46
Conversation
controllers/watcherapi_controller.go
Outdated
| if (ctrlResult != ctrl.Result{}) { | ||
| // We can ignore RequeueAfter as we are watching the KeystoneEndpoint | ||
| // resource | ||
| return ctrlResult, nil | ||
| } | ||
|
|
||
| return ctrl.Result{}, nil |
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.
I think you can remove the if block here and just return ctrlResult, nil
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.
true, good catch, I'll push the change with the updated functional test
controllers/watcherapi_controller.go
Outdated
| if (err != nil || result != ctrl.Result{}) { | ||
| // We can ignore RequeueAfter as we are watching the KeystoneEndpoint | ||
| // resource | ||
| return ctrl.Result{}, err |
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.
| return ctrl.Result{}, err | |
| return result, err |
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.
fixed, will push the fix in the next update
Create the WatcherAPI keystoneEndpoint. After this point, we can run watcher commands from the openstackclient pod (even though we can't do anything because the decision engine and applier are not available yet). This version does not support TLS, so the control plane must be deployed with TLS disabled as well.
Note that the fact that the operator does not support creating TLS endpoing does not imply that watcher can not run with a TLS enabled controlplane. Actually, I think we should be able to use a TLS enabled controlplane with #45 even if we are exposing watcher as http only. |
Remove the loadBalancerIP from the watcher-api-service-override test. This value will be environment specific, as environments might configure different ip ranges in the IPAddressPools.
72bd367 to
10f7e4b
Compare
|
This change depends on a change that failed to merge. Change openstack-k8s-operators/ci-framework#2658 is needed. |
|
recheck |
|
This change depends on a change with an invalid configuration. |
|
recheck |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: amoralej 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 |
|
/lgtm Kuttl tests are validating it with via running commands in openstackclient pod. |
e1f3ef1
into
openstack-k8s-operators:main
Create the WatcherAPI keystoneEndpoint. After this point, we can run
watcher commands from the openstackclient pod (even though we can't do
anything because the decision engine and applier are not available yet).
This version does not support TLS, so the control plane must be
deployed with TLS disabled as well.
Add tests for WatcherAPI keystoneendpoint addition, and remove specific ip from
watcher-api-service-override, as that can be environment-specific.
Related: OSPRH-11483
Depends-On: openstack-k8s-operators/ci-framework#2658