Update novaapi, novametadata and novanovncproxy to use service override

[stuggi]

Removes creation of routes. Those get done in the openstack-operator. Via service overrides the openstack-operator customize the services for the endpoints to the desired state specified in the ctlplane CR using externalEndpoints or the service override in the service template.

Jira: OSP-26690

Depends-On: openstack-k8s-operators/lib-common#313

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stuggi

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:

• OWNERS [stuggi]

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

[softwarefactory-project-zuul]

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://review.rdoproject.org/zuul/buildset/dd435609f3f24b7e8f8aa34d9c0229b6

❌ nova-operator-content-provider FAILURE in 10m 17s
⚠️ nova-operator-kuttl SKIPPED Skipped due to failed job nova-operator-content-provider

[stuggi]

wondering if there is the need for vncproxy to on the internal network. pods should probably be confgured to be attached via multus to the internal api network

[stuggi]

@gibizer wondering what you think would be best for the externalcompute getting the vnc endpoint. right now it checks for the route [1], the externalcompute could check the novncproxy CR. either the host/url could be stored in the status, or it could get the endpointURL from the override and take the the novncproxy service.
[1] https://github.com/openstack-k8s-operators/nova-operator/blob/main/controllers/novaexternalcompute_controller.go#L461-L476

[softwarefactory-project-zuul]

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://review.rdoproject.org/zuul/buildset/6975d5a38b6f4eabb845f259d21ed1a7

❌ nova-operator-content-provider FAILURE in 7m 55s
⚠️ nova-operator-kuttl SKIPPED Skipped due to failed job nova-operator-content-provider

[softwarefactory-project-zuul]

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://review.rdoproject.org/zuul/buildset/776502422a76444985e14335ffa34d8c

❌ nova-operator-content-provider FAILURE in 12m 18s
⚠️ nova-operator-kuttl SKIPPED Skipped due to failed job nova-operator-content-provider

[openshift-ci]

@stuggi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/functional	1b769dd	link	true	/test functional
ci/prow/nova-operator-build-deploy	1b769dd	link	false	/test nova-operator-build-deploy
ci/prow/nova-operator-build-deploy-tempest	1b769dd	link	false	/test nova-operator-build-deploy-tempest

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[openshift-merge-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[stuggi]

closing in favor of #522