WIP: Support changing all the images#21
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Akrog 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 |
With this commit we start deploying the MCP server as a sidecar container of the lightspeed-service container. The MCP server deployed is the one from our own rhos-mcps repository [1]. On installation the `openshift-cli` tool is enabled when OpenStack Lightspeed is configured, and the `openstack-cli` tool is enabled when the `OpenStackControlPlane` is ready. From a security perspective since we are deploying the MCP tools in the pod's network namespace not using TLS is not a real security risk. [1]: https://github.com/openstack-lightspeed/rhos-mcps Jira: OSPRH-27075 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Job govulncheck is failing with the following error. ``` Vulnerability openstack-k8s-operators#1: GO-2026-5970 Infinite loop on invalid input in golang.org/x/text More info: https://pkg.go.dev/vuln/GO-2026-5970 Module: golang.org/x/text Found in: golang.org/x/text@v0.37.0 Fixed in: golang.org/x/text@v0.39.0 ``` This commit updates the text dependency and transitive version bumps of other dependencies.
For now we don't want to automatically deploy the MCP tools, because: - Releasing the rhos-mcps image may be done at a later time. - This is an experimental feature right now, so we want it disabled by default. The name of the feature flag is `rhos_mcps` as shown in the config ample. Jira: OSPRH-27075 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Initial implementation of the MCP deployment uses the credentials from the `openstackclient` pod, which means that we are not the owners of that secret, just the copy we make in the `openstack-lightspeed` namespace, so those credentials could be removed/deleted and that would break our `openstack-cli` tool. In this patch we change the credentials and we leverage the `KeystoneApplicationCredential` CR to get our own credentials. Credential Rotation is handled by the code as well. Jira: OSPRH-27075 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
We used to be able to change the RAG image using the `ragImage` field in our CR, but we removed it and said we would make a consistent interface to modify ALL possible images via the CRD. In this patch we add functionality to change the images used by the operator for the following: - lighspeed-core - exporter - postgres - console image - OKP image - RHOS MCP server - RAG Image To provide a consistent interface, similar to what we can do in the other openstack operators, we can now set all the images under the `images` field. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
d3af8e9 to
46d36ca
Compare
|
@Akrog: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
We used to be able to change the RAG image using the
ragImagefield in our CR, but we removed it and said we would make a consistent
interface to modify ALL possible images via the CRD.
In this patch we add functionality to change the images used by the
operator for the following:
To provide a consistent interface, similar to what we can do in the
other openstack operators, we can now set all the images under the
imagesfield.PS: This PR is based on the MCP PR and only adds 1 commit, so I'll remove the WIP flag when the other PR merges.