Skip to content

rampadc/otp-argocd

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Install and configure OpenShift GitOps

  1. Install the OpenShift GitOps Operator and create a ClusterRole and ClusterRoleBinding.

    oc apply -f setup/
    while ! oc wait crd applications.argoproj.io --timeout=-1s --for=condition=Established  2>/dev/null; do sleep 30; done
    while ! oc wait pod --timeout=-1s --for=condition=Ready -l '!job-name' -n openshift-gitops > /dev/null; do sleep 30; done
  2. Create a custom ArgoCD instance with custom checks

    oc apply -k argocd-instance

    Note: We use a custom openshift-gitops-repo-server image to enable the use of Plugins within OpenShift Gitops. This is required to allow RHACM to utilise the Policy Generator plugin. The Dockerfile can be found here: https://github.com/one-touch-provisioning/otp-custom-argocd-repo-server.

  3. If using IBM Cloud ROKS as a Hub Cluster, configure TLS.

    scripts/patch-argocd-tls.sh
  4. Create a console link

    export ROUTE_NAME=otp-gitops-server
    export ROUTE_NAMESPACE=openshift-gitops
    export CONSOLE_LINK_URL="https://$(oc get route $ROUTE_NAME -o=jsonpath='{.spec.host}' -n $ROUTE_NAMESPACE)"
    envsubst < <(cat setup/4_consolelink.yaml.envsubst) | kubectl apply -f -
  5. Retrieve admin login details

    echo $(oc get route -n openshift-gitops otp-gitops-server -o template --template='https://{{.spec.host}}')
    
    # Passsword is not needed if Log In via OpenShift is used (default)
    oc extract secrets/otp-gitops-cluster --keys=admin.password -n openshift-gitops --to=-

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages