OPRUN-4470: olmv1 hypershift support

[grokspawn]

This enhancement is to add hypershift topology support for OLMv1 deployments without API or deployment dimension changes.

Since we're endeavoring to follow an agentic-enabled development model, I had claude reference my design document and this document, and ensure that it felt confident this document could be used for agentic implementation of component changes, testing discussed herein.
In my experience this led to a little more "including the basics" and also some duplication, but we won't know if those are essential to the processes' success or superfluous at this point.

Absolutely interested in reviewers' feedback about whether the resulting document is easier/harder to review.

[openshift-ci-robot]

@grokspawn: This pull request references OPRUN-4324 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This enhancement is to add hypershift topology support for OLMv1 deployments without API or deployment dimension changes.

Since we're endeavoring to follow an agentic-enabled development model, I had claude reference my design document and this document, and ensure that it felt confident this document could be used for agentic implementation of component changes, testing discussed in this document.
In my experience this led to a little more "including the basics" and also some duplication, but we won't know if those are essential to the processes' success or superfluous at this point.

Absolutely interested in reviewers' feedback about whether the resulting document is easier/harder to review.

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.

[grokspawn]

/assign @joelanford
/assign @oceanc80

[openshift-ci-robot]

@grokspawn: This pull request references OPRUN-4324 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This enhancement is to add hypershift topology support for OLMv1 deployments without API or deployment dimension changes.

Since we're endeavoring to follow an agentic-enabled development model, I had claude reference my design document and this document, and ensure that it felt confident this document could be used for agentic implementation of component changes, testing discussed herein.
In my experience this led to a little more "including the basics" and also some duplication, but we won't know if those are essential to the processes' success or superfluous at this point.

Absolutely interested in reviewers' feedback about whether the resulting document is easier/harder to review.

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.

[openshift-ci-robot]

@grokspawn: This pull request references OPRUN-4470 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This enhancement is to add hypershift topology support for OLMv1 deployments without API or deployment dimension changes.

Since we're endeavoring to follow an agentic-enabled development model, I had claude reference my design document and this document, and ensure that it felt confident this document could be used for agentic implementation of component changes, testing discussed herein.
In my experience this led to a little more "including the basics" and also some duplication, but we won't know if those are essential to the processes' success or superfluous at this point.

Absolutely interested in reviewers' feedback about whether the resulting document is easier/harder to review.

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from joelanford. 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:

• OWNERS

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

[openshift-ci]

@grokspawn: 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.