Skip to content

Latest commit

 

History

History
48 lines (34 loc) · 2.47 KB

README.md

File metadata and controls

48 lines (34 loc) · 2.47 KB

Deploy policies to Red Hat Advanced Cluster Management

Deploy policies to Red Hat Advanced Cluster Management with the deploy.sh script.

Deploying policies with GitOps

You must meet the following prerequisites before you deploy policies with the script:

  • Your oc or kubectl CLI must be configured and able to access the cluster to which you want to deploy.
  • You must have an existing cluster namespace on the cluster to which you select to deploy.

View the following guidance on how to use the script (all parameters are optional--any parameters not provided will use the defaults specified):

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

  -h|--help                   Display this menu
  -u|--url <url>              URL to the Git repository
                                (Default URL: "https://github.com/open-cluster-management/policy-collection.git")
  -b|--branch <branch>        Branch of the Git repository to point to
                                (Default branch: "master")
  -p|--path <path/to/dir>     Path to the desired subdirectory of the Git repository
                                (Default path: stable)
  -n|--namespace <namespace>  Namespace on the cluster to deploy policies to (must exist already)
                                (Default namespace: "policies")
  -a|--name <resource-name>   Prefix for the Channel and Subscription resources
                                (Default name: "demo-stable-policies")

Remove resources

Find and remove resources that are created with the deploy.sh script from Red Hat Advanced Cluster Management. You must meet the following prerequisites before you remove resources with the remove.sh script:

  • Your oc or kubectl CLI must be configured and able to access to the resources that you want to remove from the cluster.
  • Verify that Channel and Subscription were deployed using the deploy.sh script. Channel and Subscription must match the pattern <prefix>-chan and <prefix>-sub respectively.

View the following guidance on how to use the script (all parameters are optional--the script will query the cluster to get options for parameters not provided):

Usage:
  ./remove.sh [-n <namespace>] [-a|--name <resource-name>]

  -h|--help                   Display this menu
  -n|--namespace <namespace>  Namespace on the cluster that resources are located
  -a|--name <resource-name>   Prefix for the Channel and Subscription resources