Merge pull request #297 from acend/fix-colors

Fix background colors
acend · Apr 26, 2024 · 61f781e · 61f781e
2 parents 921d14b + 6e24390
commit 61f781e
Showing 13 changed files with 29 additions and 29 deletions.
diff --git a/content/en/docs/01/_index.md b/content/en/docs/01/_index.md
@@ -11,9 +11,9 @@ The first thing we're going to do is to explore our lab environment and get in t
 
 The namespace with the name corresponding to your username is going to be used for all the hands-on labs. And you will be using the `argocd tool` or the ArgoCD webconsole, to verify what resources and objects Argo CD created for you.
 
-{{% alert title="Note" color="primary" %}}You can also use your local installation of the cli tools. Make sure you completed [the setup](../../setup/) before you continue with this lab.{{% /alert %}}
+{{% alert title="Note" color="info" %}}You can also use your local installation of the cli tools. Make sure you completed [the setup](../../setup/) before you continue with this lab.{{% /alert %}}
 
-{{% alert title="Note" color="primary" %}}The URL and Credentials to the Web IDE will provided by the teacher. Use Chrome for the best experience.{{% /alert %}}
+{{% alert title="Note" color="info" %}}The URL and Credentials to the Web IDE will provided by the teacher. Use Chrome for the best experience.{{% /alert %}}
 
 
 Once you're successfully logged into the web IDE open a new Terminal by hitting `CTRL + SHIFT + ¨` or clicking the Menu button --> Terminal --> new Terminal and check the installed {{% param cliToolName %}}version by executing the following command:
@@ -149,7 +149,7 @@ argocd app create --help
 
 ### Task {{% param sectionnumber %}}.2: Autocompletion
 
-{{% alert title="Note" color="primary" %}}This step is only needed, when you're not working with the Web IDE we've provided. The autocompletion is already installed in the Web IDE{{% /alert %}}
+{{% alert title="Note" color="info" %}}This step is only needed, when you're not working with the Web IDE we've provided. The autocompletion is already installed in the Web IDE{{% /alert %}}
 
 A productivity booster when working with the CLI is the autocompletion feature. It can be used for `bash` and `zsh` shells. You can enable the autocompletion for the current `bash` with the following command:
 

diff --git a/content/en/docs/02/_index.md b/content/en/docs/02/_index.md
@@ -23,7 +23,7 @@ For this Training we've installed a Git Server under [https://{{% param giteaUrl
 Open your Webbrowser and navigate to [https://{{% param giteaUrl %}}](https://{{% param giteaUrl %}}/).
 Login with the training credentials provided by the trainer (Login Button is in the upper right corner).
 
-{{% alert title="Note" color="primary" %}}Users which have a personal Github account can just fork the Repository [argocd-training-examples](https://github.com/acend/argocd-training-examples) to their personal account. To fork the repository click on the top right of the Github on _Fork_.{{% /alert %}}
+{{% alert title="Note" color="info" %}}Users which have a personal Github account can just fork the Repository [argocd-training-examples](https://github.com/acend/argocd-training-examples) to their personal account. To fork the repository click on the top right of the Github on _Fork_.{{% /alert %}}
 
 {{% /onlyWhenNot  %}}
 
@@ -39,7 +39,7 @@ Users which have a personal Github account can just fork the Repository [argocd-
 
 All other users can use the provided Gitea installation of the personal lab environment. Visit [https://{{% param giteaUrl %}}](https://{{% param giteaUrl %}}/) with your browser and register a new account with your personal username and a password that you can remember ;)
 
-{{% alert title="Note" color="primary" %}}All the cli commands in this chapter must be executed in the terminal of the provided Web IDE.{{% /alert %}}
+{{% alert title="Note" color="info" %}}All the cli commands in this chapter must be executed in the terminal of the provided Web IDE.{{% /alert %}}
 
 ![Register new User in Gitea](gitea-register.png)
 
@@ -71,7 +71,7 @@ echo $USER
 
 The `USER` variable will be used as part of the commands to make the lab experience more comfortable for you.
 
-{{% alert title="Note" color="primary" %}}If you're **not** using our lab webshell to execute the labs, make sure to set the `USER` environment variable accordingly with the following command `export USER=<username>`{{% /alert %}}
+{{% alert title="Note" color="info" %}}If you're **not** using our lab webshell to execute the labs, make sure to set the `USER` environment variable accordingly with the following command `export USER=<username>`{{% /alert %}}
 
 
 Clone the forked repository to your local workspace:
@@ -120,9 +120,9 @@ argocd app create argo-$USER --repo https://{{% param giteaUrl %}}/$USER/argocd-
 
 Expected output: `application 'argo-<username>' created`
 
-{{% alert title="Note" color="primary" %}}We don't need to provide Git credentials because the repository is readable for non-authenticated users as well{{% /alert %}}
+{{% alert title="Note" color="info" %}}We don't need to provide Git credentials because the repository is readable for non-authenticated users as well{{% /alert %}}
 
-{{% alert title="Note" color="primary" %}}If you want to deploy it in a different namespace, make sure the namespaces exists before synching the app{{% /alert %}}
+{{% alert title="Note" color="info" %}}If you want to deploy it in a different namespace, make sure the namespaces exists before synching the app{{% /alert %}}
 
 Once the application is created, you can view its status:
 
@@ -569,7 +569,7 @@ Argo CD can't any longer access the protected repository without providing crede
 argocd repo add https://{{% param giteaUrl %}}/$USER/argocd-training-examples.git --username $USER
 ```
 
-{{% alert title="Note" color="primary" %}}
+{{% alert title="Note" color="info" %}}
 You can provide the password through the cli by using the flag `--password`.
 {{% /alert %}}
 
@@ -586,7 +586,7 @@ argocd repocreds add https://{{% param giteaUrl %}}/$USER --username $USER
 
 Finally make your personal Git repository public again for the following labs. Uncheck the option `Visibility: Make Repository Private` under `Settings -> Repository` in the Gitea UI.
 
-{{% alert title="Note" color="primary" %}}
+{{% alert title="Note" color="info" %}}
 TLS certificates and SSH private keys are supported alternative authentication methods by Argo CD. Proxy support can be configured as well in the repository settings.
 {{% /alert %}}
 

diff --git a/content/en/docs/03/_index.md b/content/en/docs/03/_index.md
@@ -34,11 +34,11 @@ metadata:
 
 It's basically a [Kubernetes Job](https://kubernetes.io/docs/concepts/workloads/controllers/job/) which starts a Pod that executes some sort of code.
 
-{{% alert  color="primary" title="Note" %}}
+{{% alert  color="info" title="Note" %}}
 Named hooks (i.e. ones with `/metadata/name`) will only be created once. If you want a hook to be re-created each time either use BeforeHookCreation policy or `/metadata/generateName`.
 {{% /alert %}}
 
-{{% alert  color="primary" title="Note" %}}
+{{% alert  color="info" title="Note" %}}
 Hooks are not run during a [selective sync](https://argoproj.github.io/argo-cd/user-guide/selective_sync/)
 {{% /alert %}}
 

diff --git a/content/en/docs/05/_index.md b/content/en/docs/05/_index.md
@@ -20,7 +20,7 @@ As mentioned in the [introduction](../) Argo CD supports many different formats
 
 So far you have been using **plain YAML** manifest in the previous labs.
 
-{{% alert title="Warning" color="secondary" %}}
+{{% alert title="Warning" color="warning" %}}
 Argo CD provides a mechanism to override the parameters of Argo CD applications. [The Argo CD parameter overrides](https://argoproj.github.io/argo-cd/user-guide/parameters/) feature is provided mainly as a convenience to developers and is intended to be used in dev/test environments, vs. production environments.
 
 Many consider this feature as anti-pattern to GitOps. So only use this feature when no other option is available!

diff --git a/content/en/docs/05/helm.md b/content/en/docs/05/helm.md
@@ -22,7 +22,7 @@ argocd app set argo-helm-$USER --values values-production.yaml
 ```
 The `--values` flag can be repeated to support multiple values files.
 
-{{% alert title="Info" color="primary" %}}
+{{% alert title="Info" color="info" %}}
 Values files must be in the same git repository as the Helm chart. The files can be in a different location in which case it can be accessed using a relative path relative to the root directory of the Helm chart.
 {{% /alert %}}
 
@@ -35,7 +35,7 @@ Similar to when using `helm` directly (`helm install <release> --set replicaCoun
 argocd app set argo-helm-$USER --parameter replicaCount=2
 ```
 
-{{% alert title="Warning" color="secondary" %}}
+{{% alert title="Warning" color="warning" %}}
 Argo CD provides a mechanism to override the parameters of Argo CD applications. [The Argo CD parameter overrides](https://argoproj.github.io/argo-cd/user-guide/parameters/) feature is provided mainly as a convenience to developers and is intended to be used in dev/test environments, vs. production environments.
 
 Many consider this feature as anti-pattern to GitOps. So only use this feature when no other option is available!
@@ -50,7 +50,7 @@ By default, the Helm release name is equal to the Application name to which it b
 argocd app set argo-helm-$USER --release-name <release>
 ```
 
-{{% alert title="Warning" color="secondary" %}}
+{{% alert title="Warning" color="warning" %}}
 Please note that overriding the Helm release name might cause problems when the chart you are deploying is using the app.kubernetes.io/instance label. ArgoCD injects this label with the value of the Application name for tracking purposes.
 {{% /alert %}}
 
@@ -111,7 +111,7 @@ We can set the `helm` parameter with the following command:
 argocd app set argo-helm-$USER --parameter replicaCount=2
 ```
 
-{{% alert title="Warning" color="secondary" %}}
+{{% alert title="Warning" color="warning" %}}
 Only use this way of setting params in dev and test stages. Not for Production!
 {{% /alert %}}
 

diff --git a/content/en/docs/05/kustomize.md b/content/en/docs/05/kustomize.md
@@ -98,7 +98,7 @@ argocd app get argo-kustomize-$USER
 ```
 {{% /details %}}
 
-{{% alert title="Warning" color="secondary" %}}
+{{% alert title="Warning" color="warning" %}}
 Only use this way of setting params in dev and test stages. Not for Production!
 {{% /alert %}}
 

diff --git a/content/en/docs/06/app_of_apps.md b/content/en/docs/06/app_of_apps.md
@@ -50,7 +50,7 @@ spec:
 
 Make sure to also commit and push your changes to the git repository.
 
-{{% alert title="Note" color="primary" %}}
+{{% alert title="Note" color="info" %}}
 Please make sure, to update all three application files
 {{% /alert %}}
 

diff --git a/content/en/docs/06/application_sets.md b/content/en/docs/06/application_sets.md
@@ -78,7 +78,7 @@ And now create the ArgoCD Application, which references the ApplicationSet defin
 argocd app create argo-appset-$USER --repo https://{{% param giteaUrl %}}/$USER/argocd-training-examples.git --path 'application-set/simple-example' --dest-server https://kubernetes.default.svc --sync-policy auto --dest-namespace argocd
 ```
 
-{{% alert title="Note" color="primary" %}}Please notice the `dest-namespace`, ApplicationSets needs to be deployed within the `argocd` namespace{{% /alert %}}
+{{% alert title="Note" color="info" %}}Please notice the `dest-namespace`, ApplicationSets needs to be deployed within the `argocd` namespace{{% /alert %}}
 
 You should now be able to see three ArgoCD Applications postfixed with your `<username>`:
 

diff --git a/content/en/docs/07/_index.md b/content/en/docs/07/_index.md
@@ -90,7 +90,7 @@ Now sync the application manifest
 argocd app sync project-app-$USER
 ```
 
-{{% alert title="Note" color="primary" %}}
+{{% alert title="Note" color="info" %}}
 The feature of limiting source repositories and destination clusters/namespaces is a powerful construct of Argo CD as roles and policies can be assigned to projects. With this tool you can enforce a fine grained permission model to control the access of the users to the different clusters and namespaces.
 {{% /alert %}}
 

diff --git a/content/en/docs/08/sync_windows.md b/content/en/docs/08/sync_windows.md
@@ -55,7 +55,7 @@ ID  STATUS  KIND  SCHEDULE   DURATION  APPLICATIONS  NAMESPACES  CLUSTERS  MANUA
 ```
 The window starts at 08:00 in the morning an lasts for 12 hours and denies all sync operation for all applications.
 
-{{% alert title="Note" color="primary" %}}
+{{% alert title="Note" color="info" %}}
 Paste the cron expression on [Crontab Guru](https://crontab.guru/#0_8_*_*_*) to get an explanation of it.
 {{% /alert %}}
 
@@ -70,7 +70,7 @@ This manual sync request will be blocked due to the active sync window with the
 FATA[0000] rpc error: code = PermissionDenied desc = Cannot sync: Blocked by sync window
 ```
 
-{{% alert title="Note" color="primary" %}}
+{{% alert title="Note" color="info" %}}
 If there is an active matching allow window and an active matching deny window then syncs will be denied as deny windows override allow windows.
 {{% /alert %}}
 

diff --git a/content/en/docs/_index.md b/content/en/docs/_index.md
@@ -13,7 +13,7 @@ As the name suggests, Argo CD takes care of the continuous delivery aspect of CI
 
 Argo CD is deployed and operated on a Kubernetes-based container platform. It is possible to connect multiple Kubernetes and OpenShift clusters to one Argo CD instance.
 
-{{% alert  color="primary" %}}
+{{% alert  color="info" %}}
 [Argo CD](https://argoproj.github.io/argo-cd/) is a declarative, GitOps continuous delivery tool for Kubernetes.
 {{% /alert %}}
 
@@ -29,7 +29,7 @@ Managing Kubernetes resources using a GitOps approach brings the following benef
 
 Argo CD follows the GitOps pattern of using Git repositories as the source of truth for defining the desired application state.
 
-{{% alert title="Warning" color="secondary" %}}
+{{% alert title="Warning" color="warning" %}}
 Argo CD provides a mechanism to override the parameters of Argo CD applications. [The Argo CD parameter overrides](https://argoproj.github.io/argo-cd/user-guide/parameters/) feature is provided mainly as a convenience to developers and is intended to be used in dev/test environments, vs. production environments.
 
 Many consider this feature as anti-pattern to GitOps. So only use this feature when no other option is available!

diff --git a/content/en/docs/additional/backup_restore.md b/content/en/docs/additional/backup_restore.md
@@ -4,7 +4,7 @@ weight: 902
 sectionnumber: 9.2
 ---
 
-{{% alert title="Warning" color="secondary" %}}
+{{% alert title="Warning" color="warning" %}}
 This Lab only works on your local machine.
 {{% /alert %}}
 
@@ -38,7 +38,7 @@ export VERSION=v2.6.3
 docker run -v ~/.kube:/home/argocd/.kube --rm argoproj/argocd:$VERSION argocd admin export > backup.yaml
 ```
 
-{{% alert title="Note" color="primary" %}}
+{{% alert title="Note" color="info" %}}
 If you should encounter permission errors like `error loading config file \"/home/argocd/.kube/config\": open /home/argocd/.kube/config: permission denied` you should change temporarily the permission of the kube config:
 
 ```bash

diff --git a/content/en/docs/additional/orphaned_resources.md b/content/en/docs/additional/orphaned_resources.md
@@ -24,7 +24,7 @@ Enable visualization and monitoring of Orphaned Resources for the newly created
 argocd proj set apps-$USER --orphaned-resources --orphaned-resources-warn
 ```
 
-{{% alert title="Note" color="primary" %}}
+{{% alert title="Note" color="info" %}}
 The flag `--orphaned-resources` enables the determinability of orphaned resources in Argo CD. After a refresh you will see them in the user interface on the project when selecting the checkbox _Orphaned Resources_.
 With the flag `--orphaned-resources-warn` enabled, for each Argo CD application with orphaned resources in the destination namespace a warning will be shown in the user interface.
 {{% /alert %}}
@@ -65,7 +65,7 @@ spec:
 EOF
 ```
 
-{{% alert title="Note" color="primary" %}}
+{{% alert title="Note" color="info" %}}
 This service will be detected as orphaned resource because it is not managed by Argo CD. All resources which are managed by Argo CD are marked with the label `app.kubernetes.io/instance` per default. The key of the label can be changed with the setting `application.instanceLabelKey`. See [documentation](https://argoproj.github.io/argo-cd/faq/#why-is-my-app-out-of-sync-even-after-syncing) for further details.
 {{% /alert %}}