Red Hat Advanced Cluster Management for Kubernetes

https://github.com/stolostron/rhacm-docs
Admin
Red Hat Advanced Cluster Management for Kubernetes provides comprehensive management capabilities...
Tokens:602,160
Snippets:5,026
Trust Score:9.7
Update:1 month ago
Show doc for...
Tokens:
Raw
### Example output of add-on deployments

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/mce_acm_integration/acm_hosted_cluster/acm_discover_hosted.adoc

Example output from the oc get deployment command, showing the add-on deployments including hypershift-addon-agent.

```bash
NAME                                READY   UP-TO-DATE   AVAILABLE   AGE
cluster-proxy-proxy-agent           1/1     1            1           24h
klusterlet-addon-workmgr            1/1     1            1           24h
hypershift-addon-agent              1/1     1            1           24h
managed-serviceaccount-addon-agent  1/1     1            1           24h
```

--------------------------------

### Example output of oc get clusterdeployment -A

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/global_hub/global_hub_ztp_migration_verify_hub.adoc

Example output showing clusters with 'Provisioned' in PROVISIONSTATUS and 'Running' in POWERSTATE, indicating successful deployment and readiness for migration.

```bash
NAMESPACE   NAME   INFRAID       PLATFORM        REGION   VERSION   CLUSTERTYPE   PROVISIONSTATUS   POWERSTATE   AGE
sno1        sno1   sno1-abc123   none-platform            4.x.x                   Provisioned       Running      30d
sno2        sno2   sno2-def456   none-platform            4.x.x                   Provisioned       Running      25d
sno3        sno3   sno3-ghi789   none-platform            4.x.x                   Provisioned       Running      20d
```

--------------------------------

### Example output of oc get clusterinstance -A

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/global_hub/global_hub_ztp_migration_verify_hub.adoc

Example output showing a cluster with 'Completed' in the PROVISIONSTATUS column. Only clusters displaying 'Completed' can be migrated; wait for provisioning to complete otherwise.

```bash
NAMESPACE   NAME   PAUSED   PROVISIONSTATUS   PROVISIONDETAILS         AGE
sno1        sno1            Completed         Provisioning completed   30d
```

--------------------------------

### Example output of oc get imageclusterinstall -A

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/global_hub/global_hub_ztp_migration_verify_hub.adoc

Example output showing clusters with 'HostValidationSucceeded' and 'ClusterInstallationSucceeded' statuses. Other states indicate incomplete installation or errors.

```bash
NAMESPACE   NAME   REQUIREMENTSMET           COMPLETED                      BAREMETALHOSTREF
sno1        sno1   HostValidationSucceeded   ClusterInstallationSucceeded   sno1
sno2        sno2   HostValidationSucceeded   ClusterInstallationSucceeded   sno2
sno3        sno3   HostValidationSucceeded   ClusterInstallationSucceeded   sno3
```

--------------------------------

### Example deployment output

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/observability/obs_create_mco.adoc

Example output showing the deployment with labels.

```bash
NAME                                  READY   UP-TO-DATE   AVAILABLE   AGE   LABELS
multicluster-observability-operator   1/1     1            1           35m   installer.name=multiclusterhub,installer.namespace=open-cluster-management
```

--------------------------------

### Verify new Agent resource

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/mce_acm_integration/siteconfig/siteconfig_scale_out_worker_nodes.adoc

Run this command on the hub cluster to check for the new Agent resource. The example output shows the agent's lifecycle stages from starting installation to Done.

```terminal
oc get agents -n <clusterinstance_namespace> --kubeconfig <hub_cluster_kubeconfig_filename>
```

```terminal
NAME                       CLUSTER                   APPROVED    ROLE     STAGE
master-node1.example.com   <managed_cluster_name>    true        master   Done
master-node2.example.com   <managed_cluster_name>    true        master   Done
master-node3.example.com   <managed_cluster_name>    true        master   Done
worker-node1.example.com   <managed_cluster_name>    false       worker 
worker-node2.example.com   <managed_cluster_name>    true        worker   Starting installation
worker-node2.example.com   <managed_cluster_name>    true        worker   Installing
worker-node2.example.com   <managed_cluster_name>    true        worker   Writing image to disk
worker-node2.example.com   <managed_cluster_name>    true        worker   Waiting for control plane
worker-node2.example.com   <managed_cluster_name>    true        worker   Rebooting
worker-node2.example.com   <managed_cluster_name>    true        worker   Joined
worker-node2.example.com   <managed_cluster_name>    true        worker   Done
```

--------------------------------

### PlacementBinding YAML example

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/governance/create_policy_console.adoc

PlacementBinding example that binds the policy-pod policy to the placement-pod placement.

```yaml
apiVersion: policy.open-cluster-management.io/v1
kind: PlacementBinding
metadata:
  name: binding-pod
placementRef:
  name: placement-pod
  kind: Placement
  apiGroup: cluster.open-cluster-management.io
subjects:
- name: policy-pod
  kind: Policy
  apiGroup: policy.open-cluster-management.io
```

--------------------------------

### Example output of console route command

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/get_started/prepare_install_mce_connected.adoc

Example output from the previous command, showing the console route details. If the URL displays 'console-openshift-console.router.default.svc.cluster.local', you must set 'openshift_master_default_subdomain' during OpenShift installation.

```bash
console console-openshift-console.apps.new-coral.purple-chesterfield.com               
console   https   reencrypt/Redirect     None
```

--------------------------------

### Basic Subscription YAML sample

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/applications/subscription_sample.adoc

A minimal Subscription example that deploys the nginx-ingress chart from the specified channel. This is a basic starting point for defining a subscription.

```yaml
apiVersion: apps.open-cluster-management.io/v1
kind: Subscription
metadata:
  name: nginx
  namespace: ns-sub-1
  labels:
    app: nginx-app-details
spec:
  channel: ns-ch/predev-ch
  name: nginx-ingress
```

--------------------------------

### Example output of oc get managedcluster

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/global_hub/global_hub_ztp_migration_verify_hub.adoc

Example output showing the expected columns and values for managed clusters that are ready for migration. All clusters should display 'True' in the JOINED and AVAILABLE columns.

```bash
NAME   HUB ACCEPTED   MANAGED CLUSTER URLS   JOINED   AVAILABLE   AGE
sno1   true                                  True     True        30d
sno2   true                                  True     True        25d
sno3   true                                  True     True        20d
```

--------------------------------

### Example storage class output

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/observability/obs_create_mco.adoc

Example output showing default storageClass (gp3-csi) and gp2-csi.

```bash
NAME                PROVISIONER       RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
gp2-csi             ebs.csi.aws.com   Delete          WaitForFirstConsumer   true                   151m
gp3-csi (default)   ebs.csi.aws.com   Delete          WaitForFirstConsumer   true                   151m
```

--------------------------------

### Example output of oc get agent after binding

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/cluster_lifecycle/scale_node_ctrl_plane.adoc

Example output of 'oc get agent' after binding, showing the agent bound to the cluster 'hcpagent'.

```bash
NAME                                   CLUSTER    APPROVED    ROLE    STAGE
c6e00642-0e11-1689-a79d-0e131d2c6ecf   hcpagent   true        master
```

--------------------------------

### Example output of node list after scaling in

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/mce_acm_integration/siteconfig/siteconfig_scale_in_worker_nodes.adoc

Example output of `oc get nodes` showing the remaining nodes after scaling in, with the worker node marked as NotReady and SchedulingDisabled.

```terminal
NAME                       STATUS                        ROLES                  AGE   VERSION
worker-node2.example.com   NotReady,SchedulingDisabled   worker                 19h   v1.30.5
worker-node1.example.com   Ready                         worker                 19h   v1.30.5
master-node1.example.com   Ready                         control-plane,master   19h   v1.30.5
master-node2.example.com   Ready                         control-plane,master   19h   v1.30.5
master-node3.example.com   Ready                         control-plane,master   19h   v1.30.5
```

--------------------------------

### Placement YAML example

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/governance/create_policy_console.adoc

Placement example that selects clusters with the label cloud: "IBM" and includes tolerations for unavailable and unreachable clusters.

```yaml
apiVersion: cluster.open-cluster-management.io/v1beta1
 kind: Placement
 metadata:
   name: placement-pod
spec:
  predicates:
  - requiredClusterSelector:
      labelSelector:
        matchLabels:
          cloud: "IBM"
    tolerations:
        - key: cluster.open-cluster-management.io/unavailable
          operator: Exists
        - key: cluster.open-cluster-management.io/unreachable
          operator: Exists
```

--------------------------------

### Example output of remaining machine resources

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/support_troubleshooting/trouble_destroy_cluster_agent.adoc

Example output from the `oc get machine` command showing a machine in the `Deleting` phase.

```plaintext
NAMESPACE           NAME             CLUSTER          NODENAME   PROVIDERID   PHASE      AGE   VERSION
clusters-hosted-0   hosted-0-9gg8b   hosted-0-nhdbp                           Deleting   10h   <4.x.0>-rc.8
```

--------------------------------

### Verify host installation

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/cluster_lifecycle/scale_node_ctrl_plane.adoc

Shows the output of the host installation status. The host is installed when the STAGE column shows 'Done'.

```bash
NAME                                   CLUSTER    APPROVED   ROLE     STAGE
c6e00642-0e11-1689-a79d-0e131d2c6ecf   hcpagent   true       master   Done
```

--------------------------------

### installerArgs example syntax

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/assisted_installer/ai_manage.adoc

Example syntax for the `installerArgs` property in an `Agent` resource. This JSON-formatted string contains overrides for the coreos-installer arguments, such as modifying kernel arguments.

```json
["--append-karg", "ip=192.0.2.2::192.0.2.254:255.255.255.0:core0.example.com:enp1s0:none", "--save-partindex", "4"]
```

--------------------------------

### KlusterletAddonConfig YAML example

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/add-ons/modify_endpoint.adoc

Example of the KlusterletAddonConfig resource. Replace <cluster-name> with your cluster name and <2.x.0> with the supported version you are using.

```yaml
apiVersion: agent.open-cluster-management.io/v1
kind: KlusterletAddonConfig
metadata:
  name: <cluster-name>
  namespace: <cluster-name>
spec:
  clusterName: <cluster-name>
  clusterNamespace: <cluster-name>
  clusterLabels:
    cloud: auto-detect
    vendor: auto-detect
  applicationManager:
    enabled: true
  certPolicyController:
    enabled: true
  policyController:
    enabled: true
  searchCollector:
    enabled: false
  version: <2.x.0>
```

--------------------------------

### Install specific OADP version with startingCSV

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/business_continuity/backup_restore/backup_install_oadp_custom.adoc

Installs a specific OADP operator version by setting the startingCSV property on the oadp-subscription-spec annotation. This example selects the stable-1.5 channel and the oadp-operator.v5.0.2 CSV. Use this optional override with caution because it can result in unsupported configurations.

```yaml
apiVersion: operator.open-cluster-management.io/v1
kind: MultiClusterHub
metadata:
  annotations:
    installer.open-cluster-management.io/oadp-subscription-spec: '{"channel": "stable-1.5","installPlanApproval": "Automatic","name":
      "redhat-oadp-operator","source": "redhat-operators","sourceNamespace": "openshift-marketplace" "startingCSV": “oadp-operator.v5.0.2”}'
  name: multiclusterhub
spec: {}
```

--------------------------------

### Retrieve CatalogSource and example output

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/business_continuity/backup_restore/backup_install_disconnected.adoc

Run 'oc get catalogsource -A' to list available CatalogSources in the disconnected environment. The output shows the custom 'redhat-operator-index' CatalogSource among others.

```bash
oc get catalogsource -A

```

```bash
NAMESPACE               NAME                         DISPLAY                       TYPE   PUBLISHER   AGE
openshift-marketplace   acm-custom-registry          Advanced Cluster Management   grpc   Red Hat     42h
openshift-marketplace   multiclusterengine-catalog   MultiCluster Engine           grpc   Red Hat     42h
openshift-marketplace   redhat-operator-index                                      grpc               42h

```

--------------------------------

### Example datasource YAML output

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/global_hub/global_hub_components_grafana.adoc

Example output from the previous command, showing the PostgreSQL datasource configuration with TLS settings and query timeout.

```yaml
apiVersion: 1
datasources:
- access: proxy
  isDefault: true
  name: Global-Hub-DataSource
  type: postgres
  url: postgres-primary.multicluster-global-hub.svc:5432
  database: hoh
  user: guest
  jsonData:
    sslmode: verify-ca
    tlsAuth: true
    tlsAuthWithCACert: true
    tlsConfigurationMethod: file-content
    tlsSkipVerify: true
    queryTimeout: 300s
    timeInterval: 30s
  secureJsonData:
    password: xxxxx
    tlsCACert: xxxxx
```

--------------------------------

### Check host installation status

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/assisted_installer/ai_cancel_host.adoc

Verify if the host is currently in an installing stage.

```bash
oc get agent -n <namespace>
```

```bash
NAME                                   CLUSTER                 APPROVED   ROLE          STAGE
127877e3-2098-4bf8-9b44-588a78ffcccd   assisted-cluster        true       worker        Rebooting
```

--------------------------------

### Example output of deployment verification

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/cluster_api/switch_iam_roles.adoc

Example output showing the capa-controller-manager and capi-controller-manager deployments are ready and available.

```text
NAME                                  READY   UP-TO-DATE   AVAILABLE   AGE
capa-controller-manager               1/1     1            1           12d
capi-controller-manager               1/1     1            1           12d
```

--------------------------------

### ConfigMap example for subscription

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/applications/subscribe_git_resources.adoc

A sample ConfigMap that might be used in the subscription context. It is shown as an example of a Kubernetes resource.

```yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: test-configmap-1
  namespace: sub-ns
data:
  age: 20
```

--------------------------------

### BareMetalHost annotation for installer args

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/support_troubleshooting/trouble_network_config_bm.adoc

Annotation to add to the BareMetalHost object to merge network configuration during installation by appending the coreos.force_persist_ip kernel argument.

```bash
"bmac.agent-install.openshift.io/installer-args": "[\"--append-karg\", \"coreos.force_persist_ip\"]"
```

--------------------------------

### Example output of siteconfig-operator-configuration ConfigMap

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/mce_acm_integration/siteconfig/siteconfig_reinstall_cluster.adoc

Example YAML output showing the ConfigMap structure. The allowReinstalls field is set to false by default; set it to true to enable reinstallation.

```yaml
apiVersion: v1
kind: ConfigMap
metadata:
    name: siteconfig-operator-configuration
    namespace: <namespace> <1>
data:
    allowReinstalls: false <2>
    ...  
```

--------------------------------

### ClusterImageSet image reference example

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/cluster_lifecycle/release_images_config.adoc

Example image reference to specify when creating a cluster in the console. Each new entry persists and is available for all future cluster provisions.

```bash
quay.io/openshift-release-dev/ocp-release:4.6.8-x86_64
```

--------------------------------

### Example alertmanager.yaml with TLS configuration

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/observability/obs_secure_alertmanager.adoc

Shows an example of the decoded alertmanager.yaml content with the TLS configuration referencing the mounted certificate and key files.

```yaml
"global":
  "http_config":
    "tls_config":
      "cert_file": "/etc/alertmanager/secrets/storyverify/tls.crt"
      "key_file": "/etc/alertmanager/secrets/storyverify/tls.key"
```

--------------------------------

### Get cluster-ID with rosa describe cluster

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/release_notes/acm_cluster_id_ocm_console.adoc

Run this command from the rosa CLI to retrieve the cluster-ID when it is not accessible in the OpenShift Cloud Manager console. Requires the rosa command line interface. The command filters the output to show only the line starting with 'ID:'. See the Getting started with the rosa CLI documentation for setup.

```bash
rosa describe cluster --cluster=<cluster-name> | grep -o '^ID:.*'
```

--------------------------------

### Output of setup-grafana-dev.sh --deploy

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/observability/obs_setup_grafana_instance.adoc

Example output from running ./setup-grafana-dev.sh --deploy, showing the resources created and patched for the Grafana developer instance.

```bash
secret/grafana-dev-config created
deployment.apps/grafana-dev created
service/grafana-dev created
serviceaccount/grafana-dev created
clusterrolebinding.rbac.authorization.k8s.io/open-cluster-management:grafana-crb-dev created
route.route.openshift.io/grafana-dev created
persistentvolumeclaim/grafana-dev created
oauthclient.oauth.openshift.io/grafana-proxy-client-dev created
deployment.apps/grafana-dev patched
service/grafana-dev patched
route.route.openshift.io/grafana-dev patched
oauthclient.oauth.openshift.io/grafana-proxy-client-dev patched
clusterrolebinding.rbac.authorization.k8s.io/open-cluster-management:grafana-crb-dev patched
```

--------------------------------

### Example of applied annotations output

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/mce_acm_integration/siteconfig/siteconfig_installation_templates.adoc

Example JSON output showing the applied annotations on the BareMetalHost, including 'myNodeAnnotation'.

```json
{
  "myNodeAnnotation": "success",
  ...
}
```

--------------------------------

### Deploy Grafana developer instance with setup-grafana-dev.sh

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/observability/obs_setup_grafana_instance.adoc

Runs the setup-grafana-dev.sh script with the --deploy flag to create the Grafana developer instance resources, including secret/grafana-dev-config, deployment.apps/grafana-dev, service/grafana-dev, ingress.extensions/grafana-dev, and persistentvolumeclaim/grafana-dev.

```bash
./setup-grafana-dev.sh --deploy
```

--------------------------------

### Example Alertmanager configuration

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/observability/obs_config_alerts.adoc

Example YAML configuration for Alertmanager, showing SMTP settings, templates, and routing rules.

```yaml
global
  smtp_smarthost: 'localhost:25'
  smtp_from: 'alertmanager@example.org'
  smtp_auth_username: 'alertmanager'
  smtp_auth_password: 'password'
templates: 
- '/etc/alertmanager/template/*.tmpl'
route:
  group_by: ['alertname', 'cluster', 'service']
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 3h 
  receiver: team-X-mails
  routes:
  - match_re:
      service: ^(foo1|foo2|baz)$
    receiver: team-X-mails
```

--------------------------------

### Example status conditions output

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/mce_acm_integration/siteconfig/siteconfig_install_clusters.adoc

Example output from the status.conditions section indicating successful manifest generation.

```terminal
message: Applied site config manifests
reason: Completed
status: "True"
type: RenderedTemplatesApplied
```

--------------------------------

### Run setup-appset-any-namespace.sh

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/gitops/gitops_enable_appset.adoc

Enables the ApplicationSet resource in any namespace on the hub cluster. Specify the namespace and Argo CD instance name.

```bash
 ./setup-appset-any-namespace.sh --namespace openshift-gitops --argocd-name openshift-gitops 
```

--------------------------------

### Example output of oc get agent after patch

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/cluster_lifecycle/scale_node_ctrl_plane.adoc

Example output of 'oc get agent' after patching, showing the agent approved and role set to master.

```bash
NAME                                   CLUSTER    APPROVED    ROLE    STAGE
c6e00642-0e11-1689-a79d-0e131d2c6ecf              true        master
```

--------------------------------

### Silence alert with a start time

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/observability/obs_silence_alerts.adoc

Silence the SampleAlert at a specific start time using the --start flag. The example uses the RFC3339 format.

```bash
amtool silence add --alertmanager.url="http://localhost:9093" --author="user" --comment="Silencing sample alert" --start="2023-04-14T15:04:05-07:00" alertname="SampleAlert"
```

--------------------------------

### Example output of managed cluster status

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/mce_acm_integration/acm_hosted_cluster/acm_discover_hosted.adoc

Example output of `oc get managedcluster` showing two managed clusters with statuses.

```bash
NAME           HUB ACCEPTED   MANAGED CLUSTER URLS            JOINED   AVAILABLE   AGE
local-cluster  true           https://<api.acm-hub.com:port>  True     True        44h
mce-a          true           https://<api.mce-a.com:port>    True     True        27s
```

--------------------------------

### MultiClusterObservability resource example with platform and userWorkloads enabled

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/observability/obs_enable_mcoa.adoc

Example YAML showing the MultiClusterObservability resource with platform and userWorkloads capabilities enabled. This is the expected result after applying the patch.

```yaml
apiVersion: observability.open-cluster-management.io/v1beta2
kind: MultiClusterObservability
metadata:
  name: observability
spec:
  capabilities:
    platform:
      metrics:
        default:
          enabled: true
    userWorkloads:
      metrics:
        default:
          enabled: true
```

--------------------------------

### Make allowlist-migration binary executable

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/observability/obs_migrate_allowlist_mcoa.adoc

Make the downloaded allowlist-migration binary executable before running it.

```bash
chmod +x /path/to/migration
```

--------------------------------

### Example ImageContentSourcePolicy YAML

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/get_started/install_disconnected.adoc

Example ImageContentSourcePolicy that redirects image references from registry.redhat.io to a mirror registry. The exact statements vary based on mirror registry setup.

```yaml
apiVersion: operator.openshift.io/v1alpha1
kind: ImageContentSourcePolicy
metadata:
  labels:
    operators.openshift.org/catalog: "true"
  name: operator-0
spec:
  repositoryDigestMirrors:
  - mirrors:
    - myregistry.example.com:5000/rhacm2
    source: registry.redhat.io/rhacm2
  - mirrors:
    - myregistry.example.com:5000/multicluster-engine
    source: registry.redhat.io/multicluster-engine
  - mirrors:
    - myregistry.example.com:5000/openshift4
    source: registry.redhat.io/openshift4
  - mirrors:
    - myregistry.example.com:5000/redhat
    source: registry.redhat.io/redhat
```

--------------------------------

### Change to the appset-any-namespace directory

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/gitops/gitops_enable_appset.adoc

Navigates to the deployment directory for the ApplicationSet any-namespace setup.

```bash
cd multicloud-integrations/deploy/appset-any-namespace
```

--------------------------------

### Example output of console route verification

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/get_started/install_disconnected.adoc

Example output from the 'oc -n openshift-console get route console' command. The console URL is shown in the second column.

```bash
console console-openshift-console.apps.new-name.purple-name.com               
console   https   reencrypt/Redirect     None
```

--------------------------------

### Create manifest list

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/cluster_lifecycle/release_images_cross_arch.adoc

Create a manifest list named mymanifest.

```bash
podman manifest create mymanifest
```

--------------------------------

### Application YAML file sample

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/applications/app_sample.adoc

This example YAML content shows a complete application definition with a name, namespace, and selector matchLabels. Use this as a template for your own application YAML files.

```yaml
apiVersion: app.k8s.io/v1beta1
kind: Application
metadata:
  name: my-application
  namespace: my-namespace
spec:
  selector:
    matchLabels:
      my-label: my-label-value
```

--------------------------------

### Sample output of search for deployments

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/search/searchapi.json.adoc

Example JSON response from a search for deployments. Shows the structure with data.search array containing count and items with resource details.

```json
{
  "data": {
    "search": [
      {
        "count": 132,
        "items": [
          {
            "_hubClusterResource": "true",
            "_uid": "local-cluster/01778e22-5ccb-4f30-bff2-3c7725f046f5",
            "apigroup": "apps",
            "apiversion": "v1",
            "available": "1",
            "cluster": "local-cluster",
            "created": "2026-08-07T01:30:33Z",
            "current": "1",
            "desired": "1",
            "kind": "Deployment",
            "kind_plural": "deployments",
            "label": "app=cluster-manager-registration-webhook; open-cluster-management.io/created-by-clustermanager=cluster-manager",
            "name": "cluster-manager-registration-webhook",
            "namespace": "open-cluster-management-hub",
            "ready": "1"
          },
          {
            "_hubClusterResource": "true",
            "_uid": "local-cluster/0197d717-3c67-456e-9dbe-e233f1cb05c3",
            "apigroup": "apps",
            "apiversion": "v1",
            "available": "1",
            "cluster": "local-cluster",
            "created": "2026-08-07T01:29:30Z",
            "current": "1",
            "desired": "1",
            "kind": "Deployment",
            "kind_plural": "deployments",
            "label": "installer.name=multiclusterhub; installer.namespace=open-cluster-management",
            "name": "multicluster-integrations",
            "namespace": "open-cluster-management",
            "ready": "1"
          },
          {
            "_hubClusterResource": "true",
            "_uid": "local-cluster/046ab6d3-7153-4e15-ad6d-56b669b73f34",
            "apigroup": "apps",
            "apiversion": "v1",
            "available": "1",
            "cluster": "local-cluster",
            "created": "2026-08-06T08:19:00Z",
            "current": "1",
            "desired": "1",
            "kind": "Deployment",
            "kind_plural": "deployments",
            "label": "app.kubernetes.io/component=networking-console-plugin; app.kubernetes.io/managed-by=cluster-network-operator; app.kubernetes.io/name=networking-console-plugin; app.kubernetes.io/part-of=cluster-network-operator; networkoperator.openshift.io/generates-operator-status=stand-alone",
            "name": "networking-console-plugin",
            "namespace": "openshift-network-console",
            "ready": "1"
          }
        ]
      }
    ]
  }
}
```

--------------------------------

### Apply Provisioning resource YAML

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/assisted_installer/ai_enable_cim.adoc

Apply the provisioning-configuration.yaml file to create the Provisioning resource.

```bash
oc apply -f provisioning-configuration.yaml
```

--------------------------------

### Create a paused HostedCluster resource

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/cluster_lifecycle/ansible_config_hosted_cluster.adoc

Defines a 'HostedCluster' with a 'pausedUntil' field to prevent the cluster from being installed until the 'ClusterCurator' hook runs. This is required before starting to install a hosted cluster using an AAP job.

```yaml
apiVersion: hypershift.openshift.io/v1beta1
kind: HostedCluster
metadata:
  name: my-cluster
  namespace: clusters
spec:
  pausedUntil: 'true'

```

--------------------------------

### Verify VolSync operator installation on managed cluster (Get- Get ManagedClusterAddOn)

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/business_continuity/volsync/volsync_replicate.adoc

Use this command on the hub to verify that the VolSync operator is installed on the managed cluster. The command checks the ManagedClusterAddOn resource named 'volsync'.

```bash
oc -n <managed-cluster-name> get ManagedClusterAddOn volsync

```

--------------------------------

### Delete ClusterServiceVersion and Subscription for Operator removal

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/get_started/uninstall.adoc

Remaining Operator components are deleted by removing the CSV and Subscription resources in the same namespace where installed; adjust the placeholder '2.x. Names and versions may vary depending on your installation channel and registry used during setup.

```listing7a
oc get csv
NAME DISPLAY VERSION REPLACE PHASE
advanced-cluster-management.v2.x.0 Advanced Cluster Management for Kubernetes 2.x.oc delete clusterserviceadvanced-cluster-management.v2.x.oc get sub
NAME PACKAGE SOURCE CHANNEL
acm-operator-subscription acm-central-registry release-2.x

oc delete sub acm-Operator-subscription

```

--------------------------------

### Apply AppProject YAML

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/gitops/gitops_configure.adoc

Apply the AppProject YAML sample using this command.

```bash
oc apply -f appproject.yaml
```

--------------------------------

### List configuration policies

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/governance/create_config_pol.adoc

Verify and list the policies in the specified namespace.

```bash
oc get policies.policy.open-cluster-management.io --namespace=<namespace>
```

--------------------------------

### Verify CSR approval status

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/mce_acm_integration/siteconfig/siteconfig_scale_in_worker_nodes.adoc

Example output of `oc get csr` showing approved CSRs for master and worker nodes before scaling in.

```terminal
NAME                       CLUSTER                  APPROVED   ROLE     STAGE
master-node1.example.com   <managed_cluster_name>   true       master   Done
master-node2.example.com   <managed_cluster_name>   true       master   Done
master-node3.example.com   <managed_cluster_name>   true       master   Done
worker-node1.example.com   <managed_cluster_name>   true       worker   Done
```

--------------------------------

### Apply namespace-example.yaml

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/gitops/gitops_deploy_argocd_appset.adoc

Command to apply the namespace YAML file using oc apply.

```bash
oc apply -f namespace-example.yaml

```

--------------------------------

### Expected output of oc get managedclusters

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/gitops/gitops_registering.adoc

Example output showing the managed cluster status and API server URL for a non-OCP cluster.

```bash
NAME    HUB ACCEPTED   MANAGED CLUSTER URLS                                                      JOINED   AVAILABLE   AGE
eks-1   true           https://5E336C922AB16684A332C10535B8D407.gr7.us-east-2.eks.amazonaws.com  True     True        37m 
```

--------------------------------

### Example search-collector-config config map YAML

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/search/create_search_collection.adoc

This YAML example shows how to configure AllowedResources and DeniedResources. It collects services and pods from all apiGroups, and all resources from admission.k8s.io and authentication.k8s.io. It denies secrets from all apiGroups and denies policies, iampolicies, and certificatepolicies from admission.k8s.io. If AllowedResources is specified, all other resources are automatically excluded.

```yaml
apiVersion: v1
kind: ConfigMap
metadata:
 name: search-collector-config
 namespace: <namespace where search-collector add-on is deployed>
data:
 AllowedResources: |-
   - apiGroups:
       - "*"
     resources: 
       - services
       - pods
   - apiGroups:
       - admission.k8s.io
       - authentication.k8s.io
     resources:
       - "*"
 DeniedResources: |-
   - apiGroups:
       - "*"
     resources:
       - secrets
   - apiGroups:
       - admission.k8s.io
     resources:
       - policies
       - iampolicies
       - certificatepolicies
```

--------------------------------

### MultiClusterHub resource with cluster-backup enabled

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/business_continuity/backup_restore/backup_install_enable_backup_operator.adoc

Use this YAML to enable the cluster-backup component by setting enableClusterBackup to true in the MultiClusterHub resource. The example shows the full resource with all components enabled, including cluster-backup. Note that for OADP, automatic installation is default, but manual installation is required for AWS STS authentication.

```yaml
apiVersion: operator.open-cluster-management.io/v1
kind: MultiClusterHub
metadata:
  name: multiclusterhub
  namespace: open-cluster-management
spec:
  availabilityConfig: High
  enableClusterBackup: false
  imagePullSecret: multiclusterhub-operator-pull-secret
  ingress:
    sslCiphers:
      - ECDHE-ECDSA-AES256-GCM-SHA384
      - ECDHE-RSA-AES256-GCM-SHA384
      - ECDHE-ECDSA-AES128-GCM-SHA256
      - ECDHE-RSA-AES128-GCM-SHA256
  overrides:
    components:
      - enabled: true
        name: multiclusterhub-repo
      - enabled: true
        name: search
      - enabled: true
        name: management-ingress
      - enabled: true
        name: console
      - enabled: true
        name: insights
      - enabled: true
        name: grc
      - enabled: true
        name: cluster-lifecycle
      - enabled: true
        name: volsync
      - enabled: true
        name: multicluster-engine
      - enabled: true
        name: cluster-backup
  separateCertificateManagement: false
```

--------------------------------

### Get installer namespace label of kubevirt-hyperconverged ClusterManagementAddOn

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/release_notes/acm_add_on_stuck_update.adoc

This command retrieves the value of the installer.namespace label from the existing kubevirt-hyperconverged ClusterManagementAddOn. Record the output for use in step 4.

```bash
oc get clustermanagementaddon kubevirt-hyperconverged -o jsonpath='{.metadata.labels.installer\.namespace}'
```

--------------------------------

### Apply Subscription with oc apply

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/get_started/install_connected.adoc

Command to create the OpenShift Subscription. Replace <path-to-file>/<subscription>.yaml with the path to your subscription file.

```bash
oc apply -f <path-to-file>/<subscription>.yaml

```

--------------------------------

### Bind policies namespace to default ClusterSet

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/governance/opp_policyset_install.adoc

Copy and apply this example YAML to bind the policies namespace to the default ClusterSet. This is required because policies are installed to the 'policies' namespace.

```yaml
apiVersion: cluster.open-cluster-management.io/v1beta2
kind: ManagedClusterSetBinding
metadata:
    name: default
    namespace: policies
spec:
    clusterSet: default
```

--------------------------------

### Output of setup-grafana-dev.sh --clean

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/observability/obs_uninstall_grafana_instance.adoc

Example output after running the uninstallation script with the --clean flag. It lists the resources that were deleted, including the secret, deployment, serviceaccount, route, persistentvolumeclaim, oauthclient, and clusterrolebinding.

```bash
secret "grafana-dev-config" deleted
deployment.apps "grafana-dev" deleted
serviceaccount "grafana-dev" deleted
route.route.openshift.io "grafana-dev" deleted
persistentvolumeclaim "grafana-dev" deleted
oauthclient.oauth.openshift.io "grafana-proxy-client-dev" deleted
clusterrolebinding.rbac.authorization.k8s.io "open-cluster-management:grafana-crb-dev" deleted
```

--------------------------------

### Placement describe output

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/support_troubleshooting/trouble_no_placementdecision_mce.adoc

Example output from the kubectl describe placement command. Shows the Status conditions for PlacementMisconfigured and PlacementSatisfied, which help identify configuration errors or unsatisfied placements.

```yaml
Name:         demo-placement
Namespace:    default
Labels:       <none>
Annotations:  <none>
API Version:  cluster.open-cluster-management.io/v1beta1
Kind:         Placement
Status:
  Conditions:
    Last Transition Time:       2022-09-30T07:39:45Z
    Message:                    Placement configurations check pass
    Reason:                     Succeedconfigured
    Status:                     False
    Type:                       PlacementMisconfigured
    Last Transition Time:       2022-09-30T07:39:45Z
    Message:                    No valid ManagedClusterSetBindings found in placement namespace
    Reason:                     NoManagedClusterSetBindings
    Status:                     False
    Type:                       PlacementSatisfied
  Number Of Selected Clusters:  0

```

--------------------------------

### Example of global ManagedClusterSetBinding

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/cluster_lifecycle/create_clusterset.adoc

Shows the automatically created 'global' ManagedClusterSetBinding that binds the 'global' ManagedClusterSet to the 'open-cluster-management-global-set' namespace. This binding is created after installing MCE and cannot be deleted or updated.

```yaml
apiVersion: cluster.open-cluster-management.io/v1beta2
kind: ManagedClusterSetBinding
metadata:
  name: global
  namespace: open-clicluster-management-global-set
spec:
  clusterSet: global
```

--------------------------------

### Metal3Cluster status output

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/cluster_api/install_capi_managed.adoc

Example output from 'oc get metal3cluster --namespace <cluster-namespace> <cluster-name> -o yaml' showing status conditions with Ready and BaremetalInfrastructureReady both True.

```yaml
status:
  conditions:
  - lastTransitionTime: "2025-06-25T10:37:03Z"
    status: "True"
    type: Ready
  - lastTransitionTime: "2025-06-25T10:37:03Z"
    status: "True"
    type: BaremetalInfrastructureReady
```

--------------------------------

### Verify MultiClusterEngine update with oc get mce

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/get_started/update_mce.adoc

Run this command to verify that the update process has started. While updating, the Status field displays 'Updating'; after the update completes, it changes to 'Available'.

```bash
oc get mce
```

--------------------------------

### Apply policy-configure-subscription-admin-hub.yaml via CLI

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/governance/opp_policyset_install.adoc

Run this command to apply the previous YAML from the command line interface.

```bash
oc apply -f policy-configure-subscription-admin-hub.yaml
```

--------------------------------

### Create Role for managed cluster monitoring permissions

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/health_metrics/using_metrics.adoc

YAML example for a Role in the open-cluster-management-agent-addon namespace that grants Prometheus permissions to get, list, and watch services, endpoints, pods, and ingresses.

```yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: prometheus-k8s-monitoring
  namespace: open-cluster-management-agent-addon
rules:
- apiGroups:
  - ""
  resources:
  - services
  - endpoints
  - pods
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - extensions
  resources:
  - ingresses
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - networking.k8s.io
  resources:
  - ingresses
  verbs:
  - get
  - list
  - watch
```

--------------------------------

### Synchronize release images with oc and make commands

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/cluster_lifecycle/sync_release_image.adoc

Commands to refresh and synchronize release images. First, delete the subscription if it is enabled. Then run make subscribe-candidate, make subscribe-fast, and make subscribe-stable to synchronize each stability level. Finally, delete the subscription again to stop viewing updates.

```bash
oc delete -f subscribe/subscription-fast
```

```bash
make subscribe-candidate
```

```bash
make subscribe-fast
```

```bash
make subscribe-stable
```

```bash
oc delete -f subscribe/subscription-fast
```

--------------------------------

### Create Role for hub cluster monitoring permissions

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/health_metrics/using_metrics.adoc

YAML example for a Role in the open-cluster-management namespace that grants Prometheus permissions to get, list, and watch services, endpoints, pods, and ingresses.

```yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: prometheus-k8s-monitoring
  namespace: open-cluster-management
rules:
- apiGroups:
  - ""
  resources:
  - services
  - endpoints
  - pods
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - extensions
  resources:
  - ingresses
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - networking.k8s.io
  resources:
  - ingresses
  verbs:
  - get
  - list
  - watch
```

--------------------------------

### Get image digest with oc adm release info

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/cluster_lifecycle/release_image_disconn.adoc

Command to obtain the image digest for a tagged OpenShift release image, followed by example output showing the Pull From line.

```bash
oc adm release info <tagged_openshift_release_image> | grep "Pull From"
```

```bash
Pull From: quay.io/openshift-release-dev/ocp-release@sha256:69d1292f64a2b67227c5592c1a7d499c7d00376e498634ff8e1946bc9ccdddfe
```

--------------------------------

### Apply ClusterInstance with oc apply

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/mce_acm_integration/siteconfig/siteconfig_install_clusters.adoc

Run this command to create the ClusterInstance resource from the 'clusterinstance-ibi.yaml' file.

```terminal
oc apply -f clusterinstance-ibi.yaml
```

--------------------------------

### Example output of oc get clusterimageset -A

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/cluster_lifecycle/create_cluster_cli.adoc

Shows the expected output format when listing ClusterImageSet resources. Each line includes the image set name and the release image reference.

```bash
img4.18.4-multi-appsub     quay.io/openshift-release-dev/ocp-release:4.18.4-multi
img4.18.4-x86-64-appsub    quay.io/openshift-release-dev/ocp-release:4.18.4-x86_64
```

--------------------------------

### Check ReinstallRenderedManifestsDeleted condition

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/mce_acm_integration/siteconfig/siteconfig_reinstall_cluster.adoc

Use this command to verify that the installation manifests are deleted. The deletion can take several minutes to complete. The example output shows the condition with reason Completed and status True.

```bash
oc get clusterinstance clusterinstance-example -n some-namespace -o json | jq -r '.status.reinstall.conditions[] | select(.type=="ReinstallRenderedManifestsDeleted")'
```

```json
{
"type": "ReinstallRenderedManifestsDeleted"
"reason": "Completed",
"status": "True",
...
}
```

--------------------------------

### Output of add-on deployment verification

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/mce_acm_integration/acm_hosted_cluster/acm_discover_hosted.adoc

Example output from the verification command showing the add-on deployments running in the open-cluster-management-agent-addon-discovery namespace.

```bash
NAME                                                  READY   STATUS    RESTARTS   AGE
application-manager-6b7f74b8f7-7sd25                  1/1     Running   0          1d15h
cluster-proxy-proxy-agent-7985ddfdb6-kng5p            3/3     Running   0          1d15h
klusterlet-addon-workmgr-55fd575b4b-rs5vz             1/1     Running   0          1d15h
managed-serviceaccount-addon-agent-54bd989b94-g6gz9   1/1     Running   0          1d15h
```

--------------------------------

### getNodesWithExactRoles YAML usage example

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/governance/template_function_get_nodes_exact_roles.adoc

In the source, the YAML sample is used to get 'infra' nodes, ignoring storage nodes, and use the result in a ConfigMap. It mentions 'node-role.kubernetes.io/worker' role is ignored in the filtering.

```yaml
...
objectDefinition:
  apiVersion: v1
  kind: ConfigMap
  metadata:
    name: my-configmap
    data:
      infraNode: |
        {{- range $i,$nd := (getNodesWithExactRoles "infra").items }}
        node{{ $i }}: {{ $nd.metadata.name }}
        {{- end }}
      replicas: {{ len ((getNodesWithExactRoles "infra").items) | toInt }}

```

--------------------------------

### Cluster resource status output

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/cluster_api/install_capi_managed.adoc

Example output from 'oc get cluster --namespace <cluster-namespace> <cluster-name> -o yaml' showing the status conditions with Ready, ControlPlaneReady, and InfrastructureReady all True.

```yaml
status:
  conditions:
  - lastTransitionTime: "2025-06-25T11:23:38Z"
    status: "True"
    type: Ready
  - lastTransitionTime: "2025-06-25T11:23:38Z"
    status: "True"
    type: ControlPlaneReady
  - lastTransitionTime: "2025-06-25T10:37:03Z"
    status: "True"
    type: InfrastructureReady
```

--------------------------------

### YAML to create new ClusterManagementAddOn resource for kubevirt-hyperconverged

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/release_notes/acm_add_on_stuck_update.adoc

This YAML defines the new kubevirt-hyperconverged ClusterManagementAddOn with version v1beta1. Replace the <instances_namspace> with the actual installer namespace you got earlier. Using the addon-manager lifecycle.
The examples: The engine column: 'Manage the cluster management add-on.
.' It uses a custom lifecycle and specifies the deployer of an add-on in install strategy.

```yaml
apiVersion: addon.open-cluster-management.io/v1beta1
kind: ClusterManagementAddOn
metadata:
  name: kubevirt-hyperconverged
  annotations:
    addon.open-cluster-management.io/lifecycle: "addon-manager"
spec:
  addOnMeta:
    description: Kubevirt Hyperconverged
    displayName: Kubevirt Hyperconverged
  defaultConfigs:
    - group: addon.open-cluster-management.io
      resource: addontemplates
      name: kubevirt-hyperconverged
  installStrategy:
    type: Placements
    placements:
    - name: openshift-cnv
      namespace: <installer_namespace>

```

--------------------------------

### Output of switch-to-grafana-admin.sh

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/observability/obs_setup_grafana_instance.adoc

Example output from running ./switch-to-grafana-admin.sh kube:admin, confirming the user has been switched to Grafana admin.

```bash
User <kube:admin> switched to be grafana admin
```

--------------------------------

### ClusterRoleBinding for Argo CD application controller

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/gitops/gitops_push_pull.adoc

Example YAML to add cluster administrator privileges to the openshift-gitops-argocd-application-controller service account on managed clusters. Required after installing the OpenShift GitOps operator on managed clusters.

```yaml
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: argo-admin
subjects:
  - kind: ServiceAccount
    name: openshift-gitops-argocd-application-controller
    namespace: openshift-gitops
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
```

--------------------------------

### Approve Agent resource with oc patch

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/clusters/cluster_lifecycle/create_cluster_on_prem.adoc

Approves the Agent custom resource to start the installation. Replace the agent name and UUID with your values. Confirmation is shown when the output includes an entry with a value of true for the APPROVED parameter.

```bash
oc -n sample-namespace patch agents.agent-install.openshift.io 07e80ea9-200c-4f82-aff4-4932acb773d4 -p '{"spec":{"approved":true}}' --type merge
```

--------------------------------

### Check ImageClusterInstall resources with oc get imageclusterinstall -A

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/global_hub/global_hub_ztp_migration_verify_hub.adoc

Run this command to verify ImageClusterInstall resources to ensure installation requirements are met. Confirm each cluster shows 'ClusterInstallationSucceeded' in the COMPLETED column and 'HostValidationSucceeded' in the REQUIREMENTSMET column.

```bash
oc get imageclusterinstall -A
```

--------------------------------

### Apply Placement

Source: https://github.com/stolostron/rhacm-docs/blob/2.17_stage/gitops/gitops_enable_appset.adoc

Applies the Placement YAML file.

```bash
oc apply -f placement-example.yaml
```
Tokens:
Raw