Loading...

XML

Word

Printable

Type: Feature
Resolution: Done
Priority: Undefined
Fix Version/s: openshift-4.17
Affects Version/s: None
Component/s: None
Labels:
- FAC:Orange
- no_core_payload

Activity Type:
Product / Portfolio Work
Parent Link:
None
Hierarchy Progress Bar:

0% To Do, 0% In Progress, 100% Done
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Size:
None

Target Version:
None
Release Blocker:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Review Complete:
None
PX Priority Data:
None
PX Impact Score:
None
PX Technical Impact:
None
PX Impact Range:
None
PX Scheduling Request:
None
PX Technical Impact Notes:
None

Intelligence Requested:
Market:

CRO require master node to run . The goal is to make CRO run on work/infra node which is a requirement for HCP

is depended on by

OCPSTRAT-605 Ensure compatibility of layered operators for HCP (HyperShift)

In Progress

links to

Failed calling webhook "clusterresourceoverrides.admission.autoscaling.openshift.io" in OpenShift Container Platform 4 when DiskPressure condition is met

openshift/aws-karpenter-provider-aws#7: PODAUTO-193: Un-break our snapshot and avoid golang 1.24 by supplying subnetID and securityGroupID to RunInstances

openshift/cluster-resource-override-admission-operator#146: OCPBUGS-33577: Fixed webhook configuration to be correctly configured as an extension API server

openshift/cluster-resource-override-admission-operator#147: PODAUTO-189: PODAUTO-190: Run CRO as a deployment and allow admins to scale and control where they run on

openshift/openshift-docs#80822: Ability to run CRO on infra/worker node

(1 links to)

Assignee:: Gaurav Singh

Reporter:: Gaurav Singh

Need Info From:: None

Contributors:: None

Architect:: None

QA Contact:: None

Doc Contact:: Matthew Werner

Product Operations Engineering Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2024/06/03 6:51 PM

Updated:: 2025/09/02 9:17 PM

Resolved:: 2024/10/04 7:58 PM