fix: only use one secret for weave-gitops and make README more clear on usage

Signed-off-by: Devin Buhl <devin@buhl.casa>
This commit is contained in:
Devin Buhl committed 2023-06-08 08:00:05 -04:00
1 parent d0fd43da93
commit b20bb7492b
3 files changed
+7 -8

No files matched your search

+2
View File
@@ -198,6 +198,8 @@ In order to expose services to the internet you will need to create a [Cloudflar
task configure
```
⚠️ This will print out the clear-text passwords for Grafana and Weave Gitops if you had them set to `generated` in your `.config.env`. Take note of these, you'll need them to log into the applications.
### ⚡ Preparing Ubuntu Server with Ansible
📍 Here we will be running an Ansible Playbook to prepare Ubuntu server for running a Kubernetes cluster.
@@ -28,7 +28,7 @@ spec:
values:
adminUser:
create: true
username: admin
createSecret: false
ingress:
enabled: true
className: nginx
@@ -51,8 +51,3 @@ spec:
impersonationResourceNames: ["admin"]
podAnnotations:
secret.reloader.stakater.com/reload: weave-gitops-secret
valuesFrom:
- kind: Secret
name: weave-gitops-secret
valuesKey: adminPassword
targetPath: adminUser.passwordHash
@@ -1,8 +1,10 @@
---
apiVersion: v1
kind: Secret
metadata:
name: weave-gitops-secret
name: cluster-user-auth
namespace: flux-system
type: Opaque
stringData:
adminPassword: "${BOOTSTRAP_WEAVE_GITOPS_ADMIN_PASSWORD}"
username: admin
password: "${BOOTSTRAP_WEAVE_GITOPS_ADMIN_PASSWORD}"