OTA-1966: AGENTS: Drop 'Deploying CVO with Lightspeed Proposals' section#1414
OTA-1966: AGENTS: Drop 'Deploying CVO with Lightspeed Proposals' section#1414wking wants to merge 1 commit into
Conversation
We grew this recently in b0e4c90 (pkg/readiness: Add readiness checks and wire into proposal controller, 2026-05-27, openshift#1395). But I don't think we need it. > The proposal controller is gated behind `TechPreviewNoUpgrade`. To > test on a Default feature set cluster... But folks can test on a tech-preview cluster, and I don't see a need to have folks edit and recompile the cluster-version operator to test on Default-feature-set clusters, when we have official docs on how to set your non-production cluster TechPreviewNoUpgrade [1]. > Build and push the skills image... But we have official build of the skills image by both ART and CI: $ oc -n ocp get -o json imagestream 5.0-art-latest | jq -r '.status.tags[] | select(.tag == "agentic-skills").items[] | .created + " " + .image' 2026-06-19T02:09:51Z sha256:3df589bb38baa9ba5ee08e48707585b7a9a90c8e37958c761420804284034d57 2026-06-17T23:09:07Z sha256:c0a98a27549db71c5fc319eadbabe0549f9f467cef0eadec683999685cd30b8f 2026-06-15T21:27:00Z sha256:c69acc6ee37d2e1b898bc0ef9999412837e2234b6bae30ad0e6e3ef2f35e3091 $ oc -n ocp get -o json imagestream 5.0 | jq -r '.status.tags[] | select(.tag == "agentic-skills").items[] | .created + " " + .image' 2026-06-10T17:53:31Z sha256:0c07886422894f138c40de3f9b85e76d374781f5ed0883d738466ecc41874de8 2026-06-02T13:28:31Z sha256:fad8159b2909f408837e9de2388cc5b946dca97a191dde44fae14694ee23b6ea 2026-05-28T20:13:04Z sha256:f683f957e7bfaa37578462f16932fbf67846b6e8b1b6f25841b539738a72fc62 and we'll soon be wiring those up to be included in the OpenShift release payload. Which will mean that folks who want to excercise custom skills image content will get that on presubmits in https://github.com/openshift/agentic-skills pulls, and Cluster Bot can generate new payloads which combine open agentic-skills pull requests with other open pull requests, and all the usual things. > Apply the prompt ConfigMap... When enabled (e.g. in a TechPreviewNoUpgrade standalone cluster), the cluster-version operator will apply the cluster-update-advisory-prompt ConfigMap (and the other manifests associated with this functionality) automatically. There's no need for users to manually apply those manifests. [1]: https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html/postinstallation_configuration/post-install-cluster-tasks#post-install-tp-tasks
|
@wking: This pull request references OTA-1966 which is a valid jira issue. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wking 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 |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
WalkthroughAGENTS.md removes the “Deploying CVO with Lightspeed Proposals (Dev)” section and its associated deployment and cleanup instructions. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@wking: all tests passed! 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 grew this recently in b0e4c90 (#1395). But I don't think we need it.
But folks can test on a tech-preview cluster, and I don't see a need to have folks edit and recompile the cluster-version operator to test on Default-feature-set clusters, when we have official docs on how to set your non-production cluster
TechPreviewNoUpgrade.But we have official build of the skills image by both ART and CI:
and we'll soon be wiring those up to be included in the OpenShift release payload. Which will mean that folks who want to excercise custom skills image content will get that on presubmits in https://github.com/openshift/agentic-skills pulls, and Cluster Bot can generate new payloads which combine open agentic-skills pull requests with other open pull requests, and all the usual things.
When enabled (e.g. in a
TechPreviewNoUpgradestandalone cluster), the cluster-version operator will apply thecluster-update-advisory-promptConfigMap (and the other manifests associated with this functionality) automatically. There's no need for users to manually apply those manifests.Summary by CodeRabbit