Continuous Delivery - fast start¶

If you are using the OpenShift Image Registry then you need to give permission to the services accounts in the "release" namespaces to be able to pull images from the "development" namespaces.

• Grant access to service accounts in the new test or staging namespace to pull the container image from the dev namespace

oc policy add-role-to-group system:image-puller system:serviceaccounts:{TEST_NAMESPACE} -n {DEV_NAMESPACE}

If you are using the IBM Container Registry then you need to copy the pull secret all-icr-io from the default namespace and then add this secret to the service account used by your application (ie default service account)

• Use the Toolkit CLI to copy the secret and setup the service account

igc pull-secret ${TEST_NAMESPACE} -t default -z default

If you are using an external image registry from a 3rd party provider like quay.io or dockerhub.io then you need to create the pull secret of type "docker-registry" and add it to the service account. Check the OpenShift Documentation Using pull secrets

1. Log into the Argo CD user interface

2. Click on the gear icon on the left menu to access the Settings options

   

3. Select the Projects option

4. Press the New Project button at the top of the page

5. Specify the properties for the new project

   • Name - Provide the name for the project
   • Description - A brief description of the project
   • Source - Press Add source and pick the Git repository from the list that was added previously
   • Destinations
     • Add https://kubernetes.default.svc for the cluster url and ${TEST_NAMESPACE} for the namespace
     • Add https://kubernetes.default.svc for the cluster url and ${STAGING_NAMESPACE} for the namespace
   • Press Create

   Note

   Initially, the only cluster that is available is the one in which Argo CD is - https://kubernetes.default.svc. By adding the two destinations we have allowed the project to be deployed to both the ${TEST_NAMESPACE} and ${STAGING_NAMESPACE} namespaces within the current cluster.

1. Log in to the Argo CD CLI

   argocd login {GRPC_INGRESS_HOST} --grpc-web [--sso]
   

   where:

   • GRPC_INGRESS_HOST is the host name of the grpc endpoint. On Red Hat OpenShift this is the same as the UI host
   • --sso is an optional flag used when sso authentication is enabled. If not using SSO then you will be prompted for the username and password

   The grpc url and credentials can be retrieved from the igc credentials command

2. Create the project

   argocd proj create {PROJECT} --dest {CLUSTER_HOST},{TEST_NAMESPACE} --src {GIT_REPO}
   

   where:

   • {PROJECT} is the name you want to give to the project.
   • {CLUSTER_HOST} is the url for the cluster server to which the project applications can be deployed. Use https://kubernetes.default.svc to reference the same cluster where Argo CD has been deployed. * can also be used to allow deployments to any server.
   • {TEST_NAMESPACE} is the namespace in the cluster where the applications can be deployed. * can be used to indicate any namespace.
   • {GIT_REPO} is the url of the git repository where the gitops config will be located or * if you want to allow any.

   Note: The --dest and --src arguments can be provided multiple times if there are multiple destinations and/or sources that should be configured for the project

1. Log in to the cluster from the command line

2. Create a file named project.yaml with the following contents

   apiVersion: argoproj.io/v1alpha1
   kind: AppProject
   metadata:
   name: {PROJECT_NAME}
   spec:
   sourceRepos:
       - '*'
   destinations:
       - namespace: '*'
       server: https://kubernetes.default.svc
   

where:

• {PROJECT NAME} is the name of the project

• Apply the yaml to the cluster in the namespace where Argo CD has been deployed (e.g. tools)

  kubectl apply -f project.yaml -n tools
  

1. Log into Argo CD user interface

2. Press New Application and provide the following values:

   • application name - The name of the application. It is recommend to use the format of {namespace}-{image name}
   • project - The ArgoCD project with which the application should be included
   • sync-policy - The manner with which Argo CD will use to manage the deployed artifacts. Automatic is recommended
   • repository url - The Git url where the configuration is stored (restricted to git urls configured in the Argo Project)
   • revision - The Git branch where the configuration for this instance is stored
   • path - The path within the repository where the application config is located (should be the application name)
   • destination cluster - The cluster url for the deployment
   • destination namespace - The namespace where the application should be deployed (restricted to namespaces configured in the Argo Project)

3. Repeat that step for each application and each environment

1. Log in to the Argo CD CLI

   argocd login {GRPC_INGRESS_HOST} --grpc-web [--sso]
   

   where:

   • GRPC_INGRESS_HOST is the host name of the grpc endpoint. On Red Hat OpenShift this is the same as the UI host
   • --sso is an optional flag used when sso authentication is enabled. If not using SSO then you will be prompted for the username and password

   The grpc url and credentials can be retrieved from the igc credentials command

2. Create an application

   argocd app create {APP_NAME} \
   --project {PROJECT} \
   --repo {GIT_REPO} \
   --path {APP_FOLDER} \
   --dest-namespace {NAMESPACE} \
   --dest-server {SERVER_URL}
   

   where:

   • {APP_NAME} is the name you want to give the application
   • {PROJECT} is the name of the project created above or "default"
   • {GIT_REPO} is the url of the git repository where the gitops config is be located
   • {APP_FOLDER} is the path to the configuration for the application in the gitops repo
   • {DEST_NAMESPACE} is the target namespace in the cluster where the application will be deployed
   • {SERVER_URL} is the url of the cluster where the application will be deployed. Use https://kubernetes.default.svc to reference the same cluster where Argo CD has been deployed

1. Log in to the cluster from the command line

2. Create a file named application.yaml with the following contents

   apiVersion: argoproj.io/v1alpha1
   kind: Application
   metadata:
   name: {APPLICATION NAME}
   spec:
   destination:
       namespace: {TARGET NAMESPACE}
       server: {TARGET CLUSTER}
   project: {PROJECT NAME}
   source:
       path: {APPLICATION PATH}
       repoURL: {REPO URL}
       targetRevision: {REPO BRANCH}
       helm:
       valueFiles:
           - values.yaml
   syncPolicy:
       automated:
       prune: true
       selfHeal: true
   

   where:

   • {APPLICATION NAME} is the name of the application
   • {PROJECT NAME} is the name of the project (the one created in the previous step or default)
   • {TARGET NAMESPACE} is the namespace where the application should be deployed
   • {TARGET CLUSTER} is the server api url for the cluster where the application should be deployed. Use https://kubernetes.default.svc for the same cluster where Argo CD has been deployed
   • {APPLICATION PATH} is the path to the folder where the secret template was created
   • {REPO URL} is the url to the git repository
   • {REPO BRANCH} is the branch in the git repository that contains the application configuration

3. Apply the yaml to the cluster in the namespace where Argo CD has been deployed (e.g. tools)

   kubectl apply -f application.yaml -n tools
   

1. Log into Argo CD user interface

2. Press New Application and provide the following values:

   • application name - The name of the application. It is recommend to use the format of {namespace}-{image name}
   • project - The project with which the application should be included
   • sync-policy - The manner with which Argo CD will use to manage the deployed artifacts. Automatic is recommended
   • repository url - The Git url where the configuration is stored
   • revision - The branch where the configuration for this instance is stored
   • path - The path within the repository where the application config is located (should be the application name)
   • destination cluster - The cluster url for the deployment
   • destination namespace - The namespace where the application should be deployed
   • Plugin - In the last section of the UI select Plugin from the dropdown
   • key-protect-secret - Click in the name field and select key-protect-secret from the dropdown

   

3. Repeat that step for each secret application and environment

1. Log in to the Argo CD CLI

   argocd login {GRPC_INGRESS_HOST} --grpc-web [--sso]
   

   where:

   • GRPC_INGRESS_HOST is the host name of the grpc endpoint. On Red Hat OpenShift this is the same as the UI host
   • --sso is an optional flag used when SSO authentication is enabled. If not using SSO then you will be prompted for the username and password

   The grpc url and credentials can be retrieved from the igc credentials command

2. Create an application

   argocd app create {APP_NAME} \
   --project {PROJECT} \
   --repo {GIT_REPO} \
   --path {APP_FOLDER} \
   --dest-namespace {NAMESPACE} \
   --dest-server {SERVER_URL} \
   --config-management-plugin key-protect-secret
   

   where:

   • {APP_NAME} is the name you want to give the application
   • {PROJECT} is the name of the project created above or "default"
   • {GIT_REPO} is the url of the git repository where the gitops config is be located
   • {APP_FOLDER} is the path to the configuration for the application in the gitops repo
   • {DEST_NAMESPACE} is the target namespace in the cluster where the application will be deployed
   • {SERVER_URL} is the url of the cluster where the application will be deployed. Use https://kubernetes.default.svc to reference the same cluster where Argo CD has been deployed

1. Log in to the cluster from the command line

2. Create a file named secret-application.yaml with the following contents

   apiVersion: argoproj.io/v1alpha1
   kind: Application
   metadata:
   name: {APPLICATION NAME}
   spec:
   destination:
       namespace: {TARGET NAMESPACE}
       server: {TARGET CLUSTER}
   project: {PROJECT NAME}
   source:
       path: {APPLICATION PATH}
       repoURL: {REPO URL}
       targetRevision: {REPO BRANCH}
       plugin:
       name: key-protect-secret
   syncPolicy:
       automated:
       prune: true
       selfHeal: true
   

   where:

   • {APPLICATION NAME} is the name of the application
   • {PROJECT NAME} is the name of the project (the one created in the previous step or default)
   • {TARGET NAMESPACE} is the namespace where the application should be deployed
   • {TARGET CLUSTER} is the server api url for the cluster where the application should be deployed. Use https://kubernetes.default.svc for the same cluster where Argo CD has been deployed
   • {APPLICATION PATH} is the path to the folder where the secret template was created
   • {REPO URL} is the url to the git repository
   • {REPO BRANCH} is the branch in the git repository that contains the application configuration

3. Apply the yaml to the cluster in the namespace where Argo CD has been deployed (e.g. tools)

   kubectl apply -f secret-application.yaml -n tools