Update RAG content to OS_VERSION 2026.1 for all projects

[malingatembo]

Changes:

• Update OS_VERSION from 2025.2 to 2026.1
• Update INDEX_NAME to os-docs-2026.1
• Add cinder and placement to OS_PROJECTS

This PR attempts to complete the prow migration for rag-content vector db image build.
Postsubmit job will build images ON MERGE ( like all other projecs do on OpenShift.
Hourly sync for image-mirroring to quay.io, already implemented ) .

Note: the acceptance criteria for daily period image builds is intentionally NOT implemented. Event-driven builds follow the standard OpenShift ci pattern.

JIRA: OSPRH-25452

Summary by CodeRabbit

This PR updates the OpenStack Lightspeed RAG (Retrieval-Augmented Generation) content build configuration in the OpenShift CI infrastructure to version 2026.1. The changes affect the CI pipeline that builds and manages the vector database image used for RAG functionality in OpenStack documentation.

Key Changes

Version and Index Updates:

• Bumped OS_VERSION from 2025.2 to 2026.1
• Updated corresponding INDEX_NAME to os-docs-2026.1

Expanded OpenStack Project Coverage:
The OS_PROJECTS variable now includes a significantly expanded list of OpenStack components beyond the previous set. New projects added include: ceilometer, placement, octavia, designate, heat, ironic, barbican, aodh, watcher, adjutant, blazar, cyborg, magnum, mistral, skyline-apiserver, skyline-console, storlets, venus, vitrage, zun, python-openstackclient, tempest, trove, masakari, and zaqar.

Infrastructure Impact

The modified CI configuration (ci-operator/config/openstack-lightspeed/rag-content/openstack-lightspeed-rag-content-main.yaml) is part of the Prow migration for the rag-content vector database image build. Upon merge, the postsubmit job will automatically build the image, with hourly synchronization to quay.io already in place for image mirroring. This aligns the RAG content build pipeline with standard OpenShift CI patterns.

Related Issue: OSPRH-25452

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 4ba7222d-32d5-4206-92f7-acab22df9020

📥 Commits

Reviewing files that changed from the base of the PR and between 30396fc and 8015254.

📒 Files selected for processing (1)

• ci-operator/config/openstack-lightspeed/rag-content/openstack-lightspeed-rag-content-main.yaml

---

Walkthrough

The PR updates the OpenStack Lightspeed RAG content build configuration to target version 2026.1 and expands the set of OpenStack projects from which content is extracted, replacing the previous version 2025.2 configuration with a significantly broader project list.

Changes

OpenStack Lightspeed RAG Content Build Configuration

Layer / File(s)

Summary

OpenStack version and project list update ci-operator/config/openstack-lightspeed/rag-content/openstack-lightspeed-rag-content-main.yaml

OS_VERSION is bumped to 2026.1 with INDEX_NAME updated to os-docs-2026.1. The OS_PROJECTS list is replaced with an expanded set of 28 OpenStack components including ceilometer, placement, octavia, designate, heat, ironic, barbican, aodh, watcher, adjutant, blazar, cyborg, magnum, mistral, skyline-apiserver, skyline-console, storlets, venus, vitrage, python-openstackclient, tempest, trove, masakari, zaqar, and zun.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically summarizes the main change: updating RAG content configuration to target OS_VERSION 2026.1 and expanding the project list, which directly matches the primary modifications in the YAML configuration file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PR contains only YAML configuration changes to a CI build config file; no Ginkgo test code present. Check for stable test names not applicable.
Test Structure And Quality	✅ Passed	This PR modifies only YAML configuration files, not test code. The custom check for Ginkgo test structure and quality is not applicable to configuration-only changes.
Microshift Test Compatibility	✅ Passed	No new Ginkgo e2e tests are added in this PR. The changes are only to a YAML CI configuration file, not test code. The check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No Ginkgo e2e tests are added in this PR. Changes are limited to updating OpenStack Lightspeed RAG content build configuration (YAML), which is outside the scope of the SNO test compatibility check.
Topology-Aware Scheduling Compatibility	✅ Passed	This PR contains only CI/CD configuration changes (prow jobs and build parameters), not deployment manifests or operator code; no Kubernetes scheduling constraints are introduced.
Ote Binary Stdout Contract	✅ Passed	PR contains only YAML configuration changes; no Go code modifications. OTE Binary Stdout Contract check targets process-level code for stdout violations, not applicable here.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No new Ginkgo e2e tests are added in this PR. The changes are configuration-only updates to a YAML CI operator file for OpenStack RAG content builds.
No-Weak-Crypto	✅ Passed	PR only modifies a YAML CI/CD configuration file with no cryptographic code, weak crypto usage, custom crypto implementations, or secret comparisons.
Container-Privileges	✅ Passed	File is a CI-Operator build config with no container specs or privileged settings; no privileged: true, hostPID/Network/IPC, SYS_ADMIN capabilities, or allowPrivilegeEscalation found.
No-Sensitive-Data-In-Logs	✅ Passed	PR modifies only CI/CD configuration with version updates and component lists; contains no passwords, tokens, API keys, PII, or other sensitive data that would be exposed in logs.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: malingatembo
Once this PR has been reviewed and has the lgtm label, please assign akrog for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openstack-lightspeed/rag-content/OWNERS

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@malingatembo: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openstack-lightspeed-rag-content-main-images	openstack-lightspeed/rag-content	presubmit	Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci]

@malingatembo: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.