1. Typically `argocd.<FQDN>` is used, not `argo.<FQDN>`. 2. The repoUrl could be added as a value in values.yaml, instead of having to replace it everywhere. 3. We should update the acme email in cert-manager 4. sealed-secrets is installed with the default service in kube-system, so theres no need to use any arguments when sealing secrets 5. Do I need to perfom this? https://aarhusai.github.io/documentation/technical/installation/deployment.html#seal-a-secret-example 6. litellm doesnt sync as it tries to migrate with a job before applying the database 7. improve notes around creating first user, allow signup and allow login form 8. General secret handling - perhaps define some 'variables' and note when to use them in the secrets.
Typically
argocd.<FQDN>is used, notargo.<FQDN>.The repoUrl could be added as a value in values.yaml, instead of having to replace it everywhere.
We should update the acme email in cert-manager
sealed-secrets is installed with the default service in kube-system, so theres no need to use any arguments when sealing secrets
Do I need to perfom this? https://aarhusai.github.io/documentation/technical/installation/deployment.html#seal-a-secret-example
litellm doesnt sync as it tries to migrate with a job before applying the database
improve notes around creating first user, allow signup and allow login form
General secret handling - perhaps define some 'variables' and note when to use them in the secrets.