https://github.com/mcaimi/ocp4-argocd
ArgoCD Cluster Setup
https://github.com/mcaimi/ocp4-argocd
argocd gitops kustomize openshift redhat
Last synced: 2 months ago
JSON representation
ArgoCD Cluster Setup
- Host: GitHub
- URL: https://github.com/mcaimi/ocp4-argocd
- Owner: mcaimi
- License: gpl-3.0
- Created: 2020-06-16T12:45:04.000Z (almost 5 years ago)
- Default Branch: master
- Last Pushed: 2021-11-29T16:29:25.000Z (over 3 years ago)
- Last Synced: 2025-01-16T21:16:05.873Z (4 months ago)
- Topics: argocd, gitops, kustomize, openshift, redhat
- Size: 405 KB
- Stars: 3
- Watchers: 2
- Forks: 5
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# OCP4 ARGOCD
This repo contains manifests and kustomization template to install, maintain and configure OpenShift 4 features with ArgoCD.
## Pre-Setup Requirements
Installation is managed by Kustomization templates. Openshift 4.3+ is required.
1. Add ArgoCD catalog source and create Namespace
```bash
$ oc create -n openshift-marketplace -f argocd/argocd-catalog-source.yaml
$ oc new-project argocd
```
2. Deploy Infrastructure prerequisites (rbac roles, service accounts, security contexts)
```bash
$ oc apply -k argocd/infra
```
3. Deploy the ArgoCD Operator
```bash
$ oc apply -k argocd/operator
```
After a while, the operator will be installed and configured accordingly:
```bash
^ >> oc get pods -n argocd
NAME READY STATUS RESTARTS AGE
argocd-operator-f89f6b6b5-f6c9g 1/1 Running 0 16m
prometheus-operator-56467cbcbf-lh6xs 1/1 Running 0 16m
```
## ArgoCD Cluster Deployment
After operators are up and running, deploy the Argo Cluster Manifest and Application Manifests
```bash
$ oc apply -k argocd/cluster
```
This will deploy:
* The Argo CD Cluster with Dex for SSO integration with Openshift
* An "argocd-infra" Application Group
* The "rbac", "operator" and "cluster" applications to let ArgoCD manage itself.
### Add Managed Namespaces to ArgoCD Application Controller
This ArgoCD Operator Deployment is namespaced: this means that by default it only can operate in its own Namespace (argocd).
To add managed namespaces to the ArgoCD cluster:
```bash
$ argocd cluster add $(oc config current-context) --in-cluster --system-namespace=argocd --namespace argocd --namespace openshift-monitoring --namespace openshift-user-workload-monitoring --namespace openshift-operators --namespace openshift-logging --namespace argo-amq-streams-operator --upsert
```
The 'namespace' switch can be used multiple times to add more namespaces, moreover if ArgoCD needs to access Cluster-Level resources, also add '--cluster-resources=true' switch to the above command.
Once that command completes, the ArgoCD cluster should be able to work on required namespaces:
```bash
$ argocd cluster list
SERVER NAME VERSION STATUS MESSAGE
https://kubernetes.default.svc (6 namespaces) openshift-monitoring/api-cluster-0894-sandbox1221-opentlc-com:6443/mcaimi 1.22 Successful
$ argocd cluster get https://kubernetes.default.svc
config:
tlsClientConfig:
insecure: true
connectionState:
attemptedAt: "2021-11-26T09:48:32Z"
message: ""
status: Successful
info:
applicationsCount: 7
cacheInfo:
apisCount: 200
lastCacheSyncTime: "2021-11-26T09:44:15Z"
resourcesCount: 696
connectionState:
attemptedAt: "2021-11-26T09:48:32Z"
message: ""
status: Successful
serverVersion: "1.22"
name: openshift-monitoring/api-cluster-0894-sandbox1221-opentlc-com:6443/mcaimi
namespaces:
- argocd
- openshift-monitoring
- openshift-user-workload-monitoring
- openshift-operators
- openshift-logging
- argo-amq-streams-operator
server: https://kubernetes.default.svc
serverVersion: "1.22"
```
## Deployment of Additional OCP Components with ArgoCD
Additional components can be deployed as ArgoCD Applications by deploying the relevant manifests:
- Local Development Users
- Elasticsearch
- Jaeger Tracing
- Kiali
- Istio Operator
- Istio Control Plane
- Openshift Pipelines Operator (Tekton)
- Openshift Serverless (KNative)
- Kubernetes NMState Operator (Tech Preview)
- RedHat Codeready Workspaces
- RedHat Advanced Cluster Manager
- Camel-K
To install these components, deploy with kustomize:
1. Local development users
```bash
$ oc apply -k apps/config
```
This will create an htpasswd-based OAuth provider with two users: a "developer" user with no specific roles granted, and a "localadmin" user with cluster-admin roles.
Passwords are the same as the username. To modify these users, look inside ocp-config/auth/htpasswd-secret.yaml.
2. Elasticsearch Operator
```bash
$ oc apply -k apps/elasticsearch
```
3. Jaeger Operator
```bash
$ oc apply -k apps/jaeger
```
4. Kiali Operator
```bash
$ oc apply -k apps/kiali
```
5. Service Mesh Operator
Service Mesh Installation is split into two distinct steps: first thing is to deploy the Istio Operator:
```bash
$ oc apply -k apps/servicemesh
```
once that has successfully finished, deploy the Istio Control Plane:
```bash
$ oc apply -k apps/istio-ctlplane
```
6. Openshift Pipelines Operator
```bash
$ oc apply -k apps/ocp-pipelines
```
7. Openshift Serverless
```bash
$ oc apply -k apps/serverless
```
8. Camel-K
deploy the operator:
```bash
$ oc apply -k apps/camelk
```
9. Advanced Cluster Manager
```bash
$ oc apply -k apps/acm
```
after the deployment of the operator has finished, deploy the Cluster Hub
```bash
$ oc apply -k apps/acm-clusterhub
```
10. Kubernetes NMState Operator
deploy the operator:
```bash
$ oc apply -k apps/nmstate
```
then deploy the NMState Instance:
```bash
$ oc apply -k apps/nmstate-instance
```
11. RedHat Codeready Workspaces
deploy the operator:
```bash
$ oc apply -k apps/codeready
```
then deploy the Codeready Cluster
```bash
$ oc apply -k apps/codeready-cluster
```
12. Openshift Logging
deploy the operator:
```bash
$ oc apply -k apps/logging-operator
```
then deploy the logging instance
```bash
$ oc apply -k apps/logging-instance
```
13. Openshift Cluster Monitoring Configuration
deploy the configmaps
```bash
$ oc apply -k apps/monitoring
```