Setting up an OpenShift cluster using Kustomize and ArgoCD by using openshift-cluster-config as a base
This is to show you can load in core components from one repo and use kustomize
to modify it/add to it for your specifc cluster with anotherin a GitOps method of managing clusters.
⚠️ This is based on the argocd operator v0.0.12 using an "Automatic" update strategy on OpenShift 4.5.2
To install argocd using the operator, use the openshift-cluster-config repo
until oc apply -k https://github.com/christianh814/openshift-cluster-config/argocd/install; do sleep 2; done
This will start the installation of argocd. You can monitor the install with a watch
on the following command.
oc get pods -n argocd
To get your argocd route (where you can login)
oc get route argocd-server -n argocd -o jsonpath='{.spec.host}{"\n"}'
To configure your cluster to this repo run
oc apply -k https://github.com/christianh814/openshift-cluster-config-expand/cluster-config/config/overlays/default
This will configure your server with the following.
Everything Mentioned in the OpenShift Cluster Config repo is included in this repo (as to not duplicate YAML).
This repo adds the additional settings/configs/apps...
- Deploying the EFK stack via OLM
- Assumes you have big enough workers
- Assumes you're on AWS using
gp2
as yourstorageClass
- Deploys an app called BGD into the
bgd
namespace- The
marketing
group hasedit
access to this namespace
- The
- ArgoCD
- The
marketing
group can sync thebgdk-green-app
application in thebgdk
project.
- The
Either a PR to this repo or the OpenShift Cluster Config repo...it's GitOps!