Correct Repos Uri

Baptiste Bonnot 2024-10-31 08:48:56 +01:00
parent 687a3a8846
commit 02fe2d8365

@ -1,14 +1,5 @@
# Welcome to our Openshift user guide wiki # Welcome to our Openshift user guide wiki
## General Overview
Your namespace have been deployed and is now accessible from openshift cli or
directly through the cluster
[console](https://console-openshift-console.apps.${CLUSTER_NAME}.kvant.cloud/)
A dummy application 'echo-server' have been deployed on it. It's a good example
on how we recommend to deploy application using our flux setup. You will find
several reference in the [How](#How-To) section that README.
## About Git Ops ## About Git Ops
@ -37,18 +28,18 @@ them.
│   └── kustomization.yaml │   └── kustomization.yaml
└── kustomization.yaml └── kustomization.yaml
``` ```
We use the [`./kustomization.yaml`](${REPO_LINK}/kustomization.yaml) as our We use the [`./kustomization.yaml`](https://git.kvant.cloud/phoenix/tenant-tpl/src/branch/main/kustomization.yaml) as our
main entrypoint that will include our [flux main entrypoint that will include our [flux
kustomization](https://fluxcd.io/flux/components/kustomize/kustomizations/). kustomization](https://fluxcd.io/flux/components/kustomize/kustomizations/).
[`./echo-server/ks.yaml`](${REPO_LINK}/echo-server/ks.yaml) Is a good example [`./echo-server/ks.yaml`](https://git.kvant.cloud/phoenix/tenant-tpl/src/branch/main/echo-server/ks.yaml) Is a good example
on how create new flux kustomization definition you could use it as a template on how create new flux kustomization definition you could use it as a template
for your next kusto. You'll find inside a breakdown and comments on line that for your next kusto. You'll find inside a breakdown and comments on line that
are mandatory. are mandatory.
The echo-server [helmrelease](${REPO_LINK}/echo-server/app/helmrelease.yaml) is The echo-server [helmrelease](https://git.kvant.cloud/phoenix/tenant-tpl/src/branch/main/echo-server/app/helmrelease.yaml) is
example of a simple application that is accessible at a given URI. It use the example of a simple application that is accessible at a given URI. It use the
helmchart template [bjw-s.yaml](${REPO_LINK}/repos/helm/bjw-s.yaml). This chart helmchart template [bjw-s.yaml](https://git.kvant.cloud/phoenix/tenant-tpl/src/branch/main/repos/helm/bjw-s.yaml). This chart
should cover pretty much all you need to deploy an app. should cover pretty much all you need to deploy an app.
@ -104,7 +95,7 @@ We have already Setup a key [Private key](Path_to_sops_private_key) dedicated
to your namespace that will be able to decrypt any secret that you is in your git repository. to your namespace that will be able to decrypt any secret that you is in your git repository.
[`./sops.yaml`](${REPO_LINK}/.sops.yaml) is the configuration file that will [`./sops.yaml`](https://git.kvant.cloud/phoenix/tenant-tpl/src/branch/main/.sops.yaml) is the configuration file that will
handle how you secret will be encrypted while using sops. handle how you secret will be encrypted while using sops.
#### Quick Start #### Quick Start
@ -129,7 +120,7 @@ age-keygen -o "$HOME/Library/Application Support/sops/age/keys.txt"
``` ```
##### Propagate your Public key ##### Propagate your Public key
Edit the [`./sops.yaml`](${REPO_LINK}/.sops.yaml) file and add your public key Edit the [`./sops.yaml`](https://git.kvant.cloud/phoenix/tenant-tpl/src/branch/main/.sops.yaml) file and add your public key
that you have generated previously. that you have generated previously.
@ -174,7 +165,7 @@ key
In case add/remove a key secret generated previously will need to be In case add/remove a key secret generated previously will need to be
reencrypted with the appropriate key. We have place a [shell reencrypted with the appropriate key. We have place a [shell
script](${REPO_LINK}/scripts/rewrap-secret.sh) that will do that for you. script](https://git.kvant.cloud/phoenix/tenant-tpl/src/branch/main/scripts/rewrap-secret.sh) that will do that for you.
It will reencrypt all the secret that it will find in folder and subfolder It will reencrypt all the secret that it will find in folder and subfolder
following the .sops.yaml rules files of your directory. following the .sops.yaml rules files of your directory.