Skip to content

Add upstream OpenStack operators documentation to RAG#94

Open
malingatembo wants to merge 1 commit intomainfrom
feat/OSPRH-25960_add-upstream-operators-docs
Open

Add upstream OpenStack operators documentation to RAG#94
malingatembo wants to merge 1 commit intomainfrom
feat/OSPRH-25960_add-upstream-operators-docs

Conversation

@malingatembo
Copy link
Contributor

Task: JIRA ticket OSPRH-25960. Include upstream OpenStack Kubernetes operators documentation into the RAG system.

Changes:

  • Add scripts/get_openstack_operators_docs.sh to fetch and convert operators documentation from GitHub (AsciiDoc -> HTML -> plaintext)
  • Add OpenStackOperatorMetadataProcessor class to generate proper GitHub Pages URLs for operators documentation
  • Add Stage 1d to Containerfile for operators docs build
  • Add BUILD_OPERATORS_DOCS, OPERATORS_REPO_URL, and OPERATORS_BRANCH variables to Makefile for configuration
  • Fixed existing permission error in okp-content cleanup step

The operators documentation is fetched from:
https://github.com/openstack-k8s-operators/openstack-operator

@malingatembo malingatembo requested a review from a team as a code owner February 27, 2026 13:58
@openshift-ci
Copy link

openshift-ci bot commented Feb 27, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: malingatembo

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

Details 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

@openshift-merge-robot
Copy link
Collaborator

PR needs rebase.

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.

Copy link
Contributor

@umago umago left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Malinga! It looks very good

Containerfile Outdated

# Clean up the OKP content
RUN rm -rf ./okp-content
RUN rm -rf ./okp-content || true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it needed ? -rf should not fail even if the folder does not exist:

[lmartins@fedora tmp]$ rm -rf aaaaaa
[lmartins@fedora tmp]$ echo $?
0

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you are right we do not need that or there at all.
i included it ( and forgot to remove it), during local testing.
I will remove it

Containerfile Outdated
# -- Stage 1d: Generate OpenStack Operators plaintext formatted documentation ----------
FROM registry.access.redhat.com/ubi9/python-311 as docs-base-operators

ARG BUILD_OPERATORS_DOCS=true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know it's public document but, I would keep it as false by default because once merged this will mess up existing CI including Konflux.

We could however enable this in the existing GitHub workflow to ensure it's working as expected (assuming it doesn't add a lot of time that will cause a timeout)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right. Addessed it. please check it

Makefile Outdated
RHOSO_IGNORE_LIST ?= ""
RHOSO_REMAP_TITLES ?= {}
RHOSO_EXCLUDE_TITLES ?= ""
BUILD_OPERATORS_DOCS ?= true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto defaulting to false

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Set it to false :)

#

class OpenStackOperatorMetadataProcessor(MetadataProcessor):
"""Metadata processor for OpenStack Kubernetes Operators Documentation"""
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Kubernets, perhaps OpenShift ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OpenShift definately

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought k8s, because of the openstack-k8s-operators/

Task: JIRA ticket OSPRH-25960. Include upstream OpenStack
Kubernetes operators documentation into the RAG system.

Changes:
- Add scripts/get_openstack_operators_docs.sh to fetch and convert
  operators documentation from GitHub (AsciiDoc -> HTML -> plaintext)
- Add OpenStackOperatorMetadataProcessor class to generate proper
  GitHub Pages URLs for operators documentation
- Add Stage 1d to Containerfile for operators docs build
- Add BUILD_OPERATORS_DOCS, OPERATORS_REPO_URL, and OPERATORS_BRANCH
  variables to Makefile for configuration
- Fixed existing permission error in okp-content cleanup step

The operators documentation is fetched from:
https://github.com/openstack-k8s-operators/openstack-operator

Acceptance criteria met: RAG contains documentation from upstream
OpenStack operators (control plane and data plane).
@malingatembo malingatembo force-pushed the feat/OSPRH-25960_add-upstream-operators-docs branch from 4453395 to 862da5b Compare February 27, 2026 16:36
@openshift-ci
Copy link

openshift-ci bot commented Feb 27, 2026

@malingatembo: The following test 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/hello-world 862da5b link true /test hello-world

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.

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