Download sealed-secrets-ibm-demo-key.yaml and apply it to the cluster.
oc new-project sealed-secrets
oc apply -f sealed-secrets-ibm-demo-key.yaml
oc delete pod -n sealed-secrets -l app.kubernetes.io/name=sealed-secrets
#DO NOT CHECK INTO GIT.
rm sealed-secrets-ibm-demo-key.yaml
For Cloud Pak to consume the entitlement key, restart the Platform Navigator pods
oc delete pod -n tools -l app.kubernetes.io/name=ibm-integration-platform-navigator
To get started setup gitops operator and rbac on each cluster
- For OpenShift 4.7+ use the following:
oc apply -f setup/ocp47/
while ! kubectl wait --for=condition=Established crd applications.argoproj.io; do sleep 30; done
oc extract secrets/openshift-gitops-cluster --keys=admin.password -n openshift-gitops --to=-
- For OpenShift 4.6 use the following:
oc apply -f setup/ocp46/
while ! kubectl wait --for=condition=Established crd applications.argoproj.io; do sleep 30; done
Once ArgoCD is deploy get the admin
password
- For OpenShift 4.7+,
oc extract secrets/openshift-gitops-cluster --keys=admin.password -n openshift-gitops --to=-
- For OpenShift 4.6,
oc extract secrets/argocd-cluster-cluster --keys=admin.password -n openshift-gitops --to=-
Apply the bootstrap profile, to use the default single-cluster
scenario use the following command:
oc apply -n openshift-gitops -f 0-bootstrap/argocd/bootstrap.yaml
For other profile clusters set environment variable TARGET_CLUSTER
then apply the profile
shared-cluster:
TARGET_CLUSTER=0-bootstrap/argocd/others/1-shared-cluster/bootstrap-cluster-1-cicd-dev-stage-prod.yaml
TARGET_CLUSTER=0-bootstrap/argocd/others/1-shared-cluster/bootstrap-cluster-n-prod.yaml
Now apply the profile
echo TARGET_CLUSTER=${TARGET_CLUSTER}
oc apply -n openshift-gitops -f ${TARGET_CLUSTER}
This repository shows the reference architecture for gitops directory structure for more info https://cloudnativetoolkit.dev/learning/gitops-int/gitops-with-cloud-native-toolkit