### Example of Applied Annotation

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

This JSON output provides an example of an annotation applied to a BareMetalHost resource, such as `myNodeAnnotation` with a value of `success`.

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

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

### Example of Applied Labels

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

This JSON output shows an example of labels applied to a ManagedCluster resource, including custom key-value pairs like `common` and `group-du`.

```json
{
  "common": "true",
  "group-du": "",
  ...
}
```

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

### DataProtectionApplication Resource Example

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

This YAML defines a `DataProtectionApplication` resource, which is used to configure backup and restore operations for OADP. It includes settings for backup storage locations, with an example of how to set the default backup storage location.

```yaml
apiVersion: "velrue.openshift.io/v1alpha1"
kind: DataProtectionApplication
metadata:
  name: "my-dpa"
  namespace: "open-cluster-management-backup"
spec:
  backupStorageProvider:
    name: "aws"
    velero:
      config:
        profile: "default"
      storageConfig:
        aws:
          bucket: "my-bucket"
          region: "us-east-1"
  backupStorageLocations:
    - velero:
        default: true
        objectStorage:
          bucket: "my-bucket"
          key: "my-prefix"
        provider: "aws"
        config:
          region: "us-east-1"

```

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

### Verify Applied Annotations using oc command

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

This terminal command shows how to retrieve and verify annotations applied to a BareMetalHost resource using `oc get` and `jq`. It targets the `example-sno.example.redhat.com` BareMetalHost in the `example-sno` namespace and outputs its metadata annotations in JSON format.

```terminal
oc get bmh example-sno.example.redhat.com -n example-sno -ojsonpath='{.metadata.annotations}' | jq
```

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

### install-config.yaml Configuration Example

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

Illustrates the structure and common parameters found in the install-config.yaml file for cluster creation. This file is used to customize installation settings.

```yaml
apiVersion: v1
kind: InstallConfig
metadata:
  name: my-cluster
spec:
  baseDomain: example.com
  platform:
    aws:
      region: us-east-1
  compute:
  - name: worker
    replicas: 3
    platform:
      aws:
        type: m5.xlarge
  controlPlane:
    name: master
    replicas: 3
    platform:
      aws:
        type: m5.xlarge
  networking:
    clusterNetwork:
    - cidr: 10.217.0.0/16
      hostPrefix: 24
    serviceNetwork:
    - 172.31.0.0/16
  fips: false
  imageContentPolicyConfig:
    repositoryDigestMirrors:
    - mirrors:
      - quay.io/mirror/redhat-operators
      origin: quay.io/redhat-operators
  pullSecret: |
    {
      "auths": {
        "cloud.openshift.com": {
          "auth": "...",
          "email": "..."
        }
      }
    }
  sshKey: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQD... 
```

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

### Example CatalogSource with Priority

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/install/install_disconnected.adoc

An example of a CatalogSource resource definition showing the 'priority' field. This field determines the order in which CatalogSources are considered during operator installation, with higher values taking precedence.

```yaml
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: redhat-operators
  namespace: openshift-marketplace
spec:
   displayName: Red Hat Operators
   priority: -100
```

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

### Example Console Route Output

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

This example demonstrates the typical output when checking an OpenShift console route, indicating the console's hostname and accessibility.

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

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

### Example Deployment Labels

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/observability/observability_enable.adoc

This YAML snippet shows the expected labels associated with the multicluster-observability-operator deployment, indicating its installation source.

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

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

### Install subctl Utility

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/networking/submariner/install_subctl.adoc

Installs the subctl utility by extracting the downloaded archive and placing the binary in the user's local bin directory. Ensure the subctl and Submariner versions match.

```bash
tar -C /tmp/ -xf <name>.tar.xz
install -m744 /tmp/<version>/<name> /$HOME/.local/bin/subctl
```

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

### ClusterInstance API for Extra Annotations and Labels

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

This YAML example shows how to use the `extraAnnotations` and `extraLabels` fields within the ClusterInstance API to apply custom annotations and labels to cluster-level and node-level manifests. It illustrates applying labels to ManagedCluster and annotations to BareMetalHost resources.

```yaml
apiVersion: siteconfig.open-cluster-management.io/v1alpha1
kind: ClusterInstance
metadata:
  name: "example-sno"
  namespace: "example-sno"
spec:
  [...] 
  clusterName: "example-sno"
  extraAnnotations: <1>
    ClusterDeployment:
      myClusterAnnotation: success
  extraLabels: <1>
    ManagedCluster:
      common: "true"
      group-du: ""
  nodes:
    - hostName: "example-sno.example.redhat.com"
      role: "master"
      extraAnnotations: <2>
        BareMetalHost:
          myNodeAnnotation: success
      extraLabels: <2>
        BareMetalHost:
          "testExtraLabel": "success"
```

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

### DataProtectionApplication (DPA) Configuration Example

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

This YAML defines a DataProtectionApplication resource, specifying backup and snapshot locations using Velero. It includes configurations for AWS S3 compatible storage, including bucket, prefix, region, and credentials.

```yaml
apiVersion: oadp.openshift.io/v1alpha1
kind: DataProtectionApplication
metadata:
  name: dpa-sample
spec:
  configuration:
    velero:
      defaultPlugins:
      - openshift
      - aws
    restic:
      enable: true
  backupLocations:
    - name: default
      velero:
        provider: aws
        default: true
        objectStorage:
          bucket: my-bucket
          prefix: my-prefix
        config:
          region: us-east-1
          profile: "default"
        credential:
          name: cloud-credentials
          key: cloud
  snapshotLocations:
    - name: default
      velero:
        provider: aws
        config:
          region: us-west-2
          profile: "default"
```

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

### Verify Applied Labels using oc command

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

This terminal command demonstrates how to retrieve and verify the labels applied to a ManagedCluster resource using `oc get` and `jq`. It targets the `example-sno` ManagedCluster and outputs its metadata labels in JSON format.

```terminal
oc get managedclusters example-sno -ojsonpath='{.metadata.labels}' | jq
```

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

### Troubleshooting MCE Installation Error

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

Example of an error encountered during MCE installation, indicating resources are still being created.

```bash
error: unable to recognize "./mce.yaml": no matches for kind "MultiClusterEngine" in version "operator.multicluster-engine.io/v1"
```

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

### Referencing Special Template Variables

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

Illustrates how to reference special template variables, like `CurrentNode`, within templates. Unlike regular spec fields, special variables must be accessed using the `.SpecialVars` prefix. This example shows how to get the current node's hostname and the cluster name.

```yaml
name: "{{ .SpecialVars.CurrentNode.HostName }}"
namespace: "{{ .Spec.ClusterName }}"
```

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

### Example Repository Verification Output

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/edge_manager/edge_mgr_manage_config_git_repo.adoc

Example output showing the details of a verified Git repository resource.

```bash
NAME           TYPE  REPOSITORY URL                                 ACCESSIBLE
site-settings  git   https://github.com/<your_org>/<your_repo>.git  True
```

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

### Applying Policy YAML

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/gitops/gitops_service_account_argo_cd.adoc

Instructions for applying the policy configuration using the oc command-line tool.

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

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

### OpenShift Container Platform 4.17 Single Node Installation Guide

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/install/cluster_size.adoc

Link to the documentation for installing OpenShift Container Platform on a single node.

```markdown
View link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/installing_on_a_single_node[Installing on a single node] to learn about the requirements.
```

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

### Apply Example Site Configuration to Device

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/edge_manager/edge_mgr_manage_config_git_repo.adoc

Updates a device specification to apply the 'example-site' configuration from a Git repository. It specifies the repository, target revision, and path within the repository.

```yaml
apiVersion: flightctl.io/v1alpha1
kind: Device
metadata:
  name: <device_name>
spec:
[...] 
  config:
  - name: example-site
    configType: GitConfigProviderSpec
    gitRef:
      repository: site-settings
      targetRevision: production
      path: /etc/example-site <2>
[...]
```

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

### Example Placement Rule YAML

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/applications/placement_sample.adoc

An example of a PlacementRule YAML configuration, specifying metadata like name and namespace, and labels for the application.

```yaml
apiVersion: apps.open-cluster-management.io/v1
kind: PlacementRule
metadata:
  name: gbapp-gbapp
  namespace: development
  labels:

```

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

### Example Agent List

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

Example output of the `oc get agents` command, showing the remaining agent resources after a worker node has been scaled 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
```

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

### Configure Placement for Right-Sizing

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/observability/obs_right_size_config.adoc

Customize the placement configuration for right-sizing guides by modifying the `placementConfiguration` in the `rs-namespace-config` ConfigMap. This example shows how to apply policies only to clusters with the `environment=prod` label.

```yaml
placementConfiguration: |
 spec:
  . .
  predicates:
  - requiredClusterSelector:
      labelSelector:
        matchLabels:
          environment: prod
  . .
```

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

### Verify Application Resource Creation

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/applications/placement_sample.adoc

Verifies that an application resource has been created by querying the API server using the OpenShift CLI tool.

```shell
oc get application.app
```

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

### Example ImageContentSourcePolicy

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/install/install_disconnected.adoc

An example ImageContentSourcePolicy YAML configuration that mirrors image references from source registries to a specified mirror registry. This policy is crucial for disconnected environments.

```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
```

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

### Example AddOnDeploymentConfig

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

An example of a completed AddOnDeploymentConfig resource, demonstrating how to set specific node selectors and tolerations for a klusterlet add-on.

```yaml
apiVersion: addon.open-cluster-management.io/v1alpha1
kind: AddOnDeploymentConfig
metadata:
  name: deploy-config
  namespace: open-cluster-management-hub
spec:
  nodePlacement:
    nodeSelector: 
      "node-dedicated": "acm-addon"
    tolerations:
      - effect: NoSchedule
        key: node-dedicated
        value: acm-addon
        operator: Equal
```

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

### Application Deployment Configuration

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/applications/placement_sample.adoc

This snippet shows a basic configuration for deploying an application, specifying the cluster selector and replica count.

```YAML
app: gbapp
spec:
  clusterSelector:
    matchLabels:
      environment: Dev
  clusterReplicas: 1
status:
  decisions:
    - clusterName: <your-local-cluster-name>
      clusterNamespace: <your-local-cluster-name>
```

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

### Example OpenShift Console Route Output

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/install/install_disconnected.adoc

This is an example of the output you might see when checking the OpenShift console route. It displays the console service, its host, and the type of routing.

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

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

### Apply Application YAML

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/applications/placement_sample.adoc

Applies a composed application YAML file to an API server using the OpenShift CLI tool. Replace `filename.yaml` with the actual name of your file.

```shell
oc apply -f filename.yaml
```

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

### Image Content Source Policy Example

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/clusters/credentials/credential_vm.adoc

This YAML snippet demonstrates an Image Content Source Policy mapping for disconnected installations. It specifies mirrors for OpenShift release images, directing the installation process to a local registry.

```yaml
- mirrors:
  - registry.example.com:5000/ocp4
  source: quay.io/openshift-release-dev/ocp-release-nightly
- mirrors:
  - registry.example.com:5000/ocp4
  source: quay.io/openshift-release-dev/ocp-release
- mirrors:
  - registry.example.com:5000/ocp4
  source: quay.io/openshift-release-dev/ocp-v4.0-art-dev
```

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

### Deploy Script Arguments Syntax

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/gitops/deploy_gitops.adoc

Provides the general syntax for the deploy.sh script, outlining the available arguments for URL, branch, path, namespace, and name prefix.

```bash
./deploy.sh [-u <url>] [-b <branch>] [-p <path/to/dir>] [-n <namespace>] [-a|--name <resource-name>]
```

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

### Pending Pod Status Example

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/troubleshooting/trouble_install_status.adoc

Illustrates a typical 'Pending' pod status indicating resource unavailability or unresolvable taints on nodes. This helps identify if the issue is due to insufficient CPU or incompatible node taints.

```yaml
reason: Unschedulable
message: '0/6 nodes are available: 3 Insufficient cpu, 3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.'
```

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

### Example Managed Cluster Node Output

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

Example output after running the 'oc get nodes' command, showing the current state of nodes on the managed cluster. This helps in visually confirming the presence or absence of specific nodes.

```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
```

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

### Observability Related Documentation Links

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/observability/observability_enable.adoc

Links to other relevant documentation sections for Observability, including using the service, advanced configuration, and an introduction to observing environments.

```asciidoc
- See xref:../observability/using_observability.adoc#using-observability[Using Observability].

- To learn more about customizing the observability service, see xref:../observability/adv_config_obs.adoc#adv-config-obs[Observability advanced configuration].

- For more related topics, return to the xref:../observability/observe_environments_intro.adoc#observing-environments-intro[Observability service].
```

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

### Sample Device Output

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/edge_manager/edge_mgr_view_devices.adoc

Example output when viewing devices in the inventory, showing key details for each device.

```bash
NAME           ALIAS    OWNER   SYSTEM  UPDATED     APPLICATIONS  LAST SEEN
<device_name>  <none>   <none>  Online  Up-to-date  <none>        3 seconds ago
```

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

### Creating Host Inventory CLI

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

This section details how to create a host inventory using the command-line interface (CLI) for the assisted installer. It covers the necessary commands and their usage.

```asciidoc
.. xref:../assisted_installer/ai_create_cli.adoc#create-host-inventory-cli[Creating a host inventory by using the command line interface]
```

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

### Kustomization Configuration for Policy Generator

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/governance/generate_pol_operator_install.adoc

Example of how to include the PolicyGenerator configuration file in your kustomization.yaml to generate policies.

```yaml
generators:
  - policy-generator-config.yaml
```

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

### Console Search Examples

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/search/query_search_console.adoc

Examples of how to use the search box in the console to find resources. Demonstrates searching by kind, namespace, status, and restart count.

```APIDOC
kind:pod
  - Finds all pod resources.

kind:pod namespace:default
  - Finds all pods in the default namespace.

kind:Pod name:a
  - Returns any pod named 'a'.

kind:Pod name:a,b
  - Returns any pod named 'a' or 'b'.

kind:pod status:!Running
  - Finds all pod resources where the status is not 'Running'.

kind:pod restarts:>1
  - Finds all pods that restarted at least twice.
```

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

### MultiClusterHub Resource with Mirror Catalog Annotation

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/install/install_disconnected.adoc

Example of a MultiClusterHub resource definition including the 'installer.open-cluster-management.io/mce-subscription-spec' annotation. This annotation specifies the mirror catalog source name required for installing the MCE operator in a disconnected environment.

```yaml
apiVersion: operator.open-cluster-management.io/v1
kind: MultiClusterHub
metadata:
   namespace: open-cluster-management
   name: hub
   annotations:
      installer.open-cluster-management.io/mce-subscription-spec: '{"source": "my-mirror-catalog-source"}'
spec: {}
```

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

### Enable Progressive Syncs for ApplicationSet

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/gitops/gitops_appset_rollout_strategy.adoc

This command enables progressive syncs for the ApplicationSet resource by patching the Argo CD instance configuration. It requires `oc` CLI and appropriate permissions in the `openshift-gitops` namespace.

```bash
oc -n openshift-gitops patch argocd openshift-gitops --type='merge' -p '{"spec":{"applicationSet":{"extraCommandArgs":["--enable-progressive-syncs"]}}}'
```

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

### Get Managed Cluster Status

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

Retrieves the status of managed clusters, showing their joined and available states, along with example URLs.

```bash
oc get managedcluster
```

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

### Disconnected Installation Image Content Source Policy

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/clusters/credentials/credential_openstack.adoc

This YAML example shows how to configure an Image Content Source Policy for disconnected OpenShift installations. It maps external image repositories to internal mirror registry paths, ensuring cluster machines can access necessary OS images.

```yaml
- mirrors:
  - registry.example.com:5000/ocp4
  source: quay.io/openshift-release-dev/ocp-release-nightly
- mirrors:
  - registry.example.com:5000/ocp4
  source: quay.io/openshift-release-dev/ocp-release
- mirrors:
  - registry.example.com:5000/ocp4
  source: quay.io/openshift-release-dev/ocp-v4.0-art-dev
```

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

### AgentServiceConfig with FIPS Annotation (4.15 and earlier)

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

Example of an AgentServiceConfig resource with the `agent-install.openshift.io/service-image-base: el8` annotation, used for installing FIPS-enabled clusters on OpenShift 4.15 and earlier.

```yaml
apiVersion: agent-install.openshift.io/v1beta1 
kind: AgentServiceConfig 
metadata: 
  annotations: 
    agent-install.openshift.io/service-image-base: el8 
...
```

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

### Create Subscription Example

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/apis/subscriptions.json.adoc

Provides an example of the JSON payload required to create a subscription resource, including metadata, spec, channel, package overrides, and placement details.

```json
{
  "apiVersion" : "apps.open-cluster-management.io/v1",
  "kind" : "Subscription",
  "metadata" : {
    "name" : "sample_subscription",
    "namespace" : "default",
    "labels" : {
      "app" : "sample_subscription-app"
    },
    "annotations" : {
      "apps.open-cluster-management.io/git-path" : "apps/sample/",
      "apps.open-cluster-management.io/git-branch" : "sample_branch"
    }
  },
  "spec" : {
    "channel" : "channel_namespace/sample_channel",
    "packageOverrides" : [ {
      "packageName" : "my-sample-application",
      "packageAlias" : "the-sample-app",
      "packageOverrides" : [ {
        "path" : "spec",
        "value" : {
          "persistence" : {
            "enabled" : false,
            "useDynamicProvisioning" : false
          },
          "license" : "accept",
          "tls" : {
            "hostname" : "my-mcm-cluster.icp"
          },
          "sso" : {
            "registrationImage" : {
              "pullSecret" : "hub-repo-docker-secret"
            }
          }
        }
      } ]
    } ]
    ,
    "placement" : {
      "placementRef" : {
        "kind" : "PlacementRule",
        "name" : "demo-clusters"
      }
    }
  }
}
```

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

### Get MultiClusterEngine Status

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

Retrieves the status phase of the MultiClusterEngine custom resource. It may take up to 10 minutes for the status to become 'Available'.

```bash
oc get mce -o=jsonpath='{.items[0].status.phase}'
```

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

### Basic Subscription Configuration

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

A basic example of a Subscription resource in YAML, defining the channel, name, and package version.

```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
  packageFilter:
    version: "1.36.x"
  placement: 
    placementRef:
      kind: Placement
      name: towhichcluster
  overrides: 
  - clusterName: "/"
    clusterOverrides:
    - path: "metadata.namespace"
      value: default
```

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

### Describe InfraEnv Resource

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

Verifies the creation of host inventory by describing the InfraEnv resource with `oc describe`. Replace `<your_namespace>` with the actual namespace.

```bash
oc describe infraenv myinfraenv -n <your_namespace>
```

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

### Example Application YAML Content

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

This is an example of a complete Application YAML file that can be used for deploying an application. It specifies the API version, kind, metadata (name and namespace), and selector with matching labels.

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

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

### Create Pull Secret YAML

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

Example YAML content for creating a `pull-secret.yaml` file, which is necessary for enabling clusters to pull images from container registries.

```yaml
# Example content for pull-secret.yaml
```

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

### DNS Record Example

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

This snippet shows an example of a DNS record configuration required for API base domain pointing to the static API VIP.

```bash
api.<cluster_name>.<base_domain>
```

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

### Verify Gatekeeper Policy Deletion

Source: https://github.com/stolostron/rhacm-docs/blob/2.14_stage/governance/gatekeeper_operator/manage_gk.adoc

Verifies the deletion of a Gatekeeper policy by attempting to retrieve it using the `oc get` command. Requires the policy name and namespace.

```bash
oc get policies.policy.open-cluster-management.io <policy-gatekeeper-operator-name> -n <namespace>
```