{"results":[{"id":"affinity-label-selector-operators","text":"Pod affinity/anti-affinity label selector operators are: `In`, `NotIn`, `Exists`, `DoesNotExist`","truth_value":"IN","justification_count":0,"dependent_count":1,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"allnamespaces-mode-global-operators-group","text":"For AllNamespaces install mode, the `openshift-operators` namespace has a default OperatorGroup called `global-operators`; no additional OperatorGroup is needed.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"allnamespaces-mode-uses-openshift-operators","text":"AllNamespaces install mode uses namespace `openshift-operators`; SingleNamespace mode requires creating an OperatorGroup in the target namespace","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"allnamespaces-mode-uses-openshift-operators-namespace","text":"For AllNamespaces install mode, the Subscription goes in the `openshift-operators` namespace which already has the `global-operators` OperatorGroup — no manual OperatorGroup creation needed.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"amd-gpu-operator-community-release","text":"The AMD GPU Operator is a community release, not a Red Hat-certified/supported Operator.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"amd-gpu-operator-install-sequence","text":"AMD GPU Operator installation requires three Operators in sequence: Node Feature Discovery (NFD) Operator, then Kernel Module Management (KMM) Operator, then AMD GPU Operator.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"ansible-helm-base-images-not-deprecated","text":"Ansible-based and Helm-based Operator base images are NOT deprecated in OCP 4.17 — only the SDK CLI tooling is deprecated.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"api-tier3-default-for-unassigned-groups","text":"API Tier 3 is the default tier for API groups without an explicit tier assignment; OperatorHub operators fall into this tier.","truth_value":"IN","justification_count":0,"dependent_count":1,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"application-delivery-operates-within-governed-immutable-platform","text":"Application packaging and delivery (Helm/Templates → build systems → ImageStreams → registry) operates entirely within the operator-driven immutable platform: applications are built on nodes managed by MCO, stored in registries managed by the Image Registry Operator, and deployed through operators managed by OLM — the application lifecycle never escapes operator governance","truth_value":"IN","justification_count":1,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"assisted-installer-saas-or-self-hosted","text":"The Assisted Installer can run as a hosted SaaS service at console.redhat.com or be self-hosted via the Assisted Installer Operator for disconnected/restricted environments.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"aws-alb-operator-ip-mode-disabled-on-ocp","text":"IP traffic mode is disabled on OCP for the AWS Load Balancer Controller (only works on EKS).","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"aws-alb-operator-namespace","text":"The AWS Load Balancer Operator runs in the `aws-load-balancer-operator` namespace.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"aws-alb-operator-outposts-alb-yes-nlb-no","text":"AWS Outposts supports ALB but not NLB with the AWS Load Balancer Operator.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"aws-alb-operator-requires-nodeport","text":"The AWS Load Balancer Operator requires service type NodePort — not LoadBalancer or ClusterIP.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"aws-alb-operator-rolearn-in-subscription","text":"The `ROLEARN` environment variable is set in the Subscription spec to configure STS for the AWS Load Balancer Operator.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"aws-alb-operator-two-iam-roles-for-sts","text":"STS clusters require two separate IAM roles for the AWS Load Balancer Operator: one for the Operator and one for the Controller.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"aws-alb-operator-x86-only-no-govcloud","text":"The AWS Load Balancer Operator only supports x86_64 architecture and does not support AWS GovCloud.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"aws-sts-entra-require-manual-operator-approval","text":"AWS STS and Microsoft Entra Workload ID clusters must use Manual approval strategy for Operator subscriptions.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"bare-metal-provisioning-architecture","text":"Bare metal IPI uses BMC for hardware automation, BareMetalHost resources with root device hints for disk selection, and a Provisioning CR consumed by the cluster-baremetal-operator to manage the metal3 lifecycle.","truth_value":"IN","justification_count":1,"dependent_count":2,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"bare-metal-vsphere-registry-starts-removed","text":"On bare metal, Nutanix, and vSphere, the Image Registry Operator bootstraps as `Removed`; admin must manually switch to `Managed` and configure storage.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null}],"count":556,"limit":20,"offset":0}