fix: add ingresses task and update readme for ssh auth

Signed-off-by: Devin Buhl <devin@buhl.casa>
This commit is contained in:
Devin Buhl committed 2022-06-15 08:07:31 -04:00
1 parent 0eb89d9eee
commit fc7ddff94a
2 files changed
+17 -5

No files matched your search

+6
View File
@@ -64,6 +64,11 @@ tasks:
- kubectl get certificates {{.CLI_ARGS | default "-A"}} - kubectl get certificates {{.CLI_ARGS | default "-A"}}
- kubectl get certificaterequests {{.CLI_ARGS | default "-A"}} - kubectl get certificaterequests {{.CLI_ARGS | default "-A"}}
ingresses:
desc: List all the helmreleases in your cluster
cmds:
- kubectl get ingress {{.CLI_ARGS | default "-A"}}
resources: resources:
desc: Gather common resources in your cluster, useful when asking for support desc: Gather common resources in your cluster, useful when asking for support
cmds: cmds:
@@ -73,4 +78,5 @@ tasks:
- task: helmrepositories - task: helmrepositories
- task: gitrepositories - task: gitrepositories
- task: certificates - task: certificates
- task: ingresses
- task: pods - task: pods
+11 -5
View File
@@ -364,6 +364,12 @@ task cluster:resources
task cluster:certificates task cluster:certificates
``` ```
7. View all the ingresses
```sh
task cluster:ingresses
```
🏆 **Congratulations** if all goes smooth you'll have a Kubernetes cluster managed by Flux, your Git repository is driving the state of your cluster. 🏆 **Congratulations** if all goes smooth you'll have a Kubernetes cluster managed by Flux, your Git repository is driving the state of your cluster.
☢️ If you run into problems, you can run `task ansible:nuke` to destroy the k3s cluster and start over. ☢️ If you run into problems, you can run `task ansible:nuke` to destroy the k3s cluster and start over.
@@ -459,7 +465,7 @@ The benefits of a public repository include:
ssh-keygen -t ecdsa -b 521 -C "github-deploy-key" -f ./cluster/github-deploy-key -q -P "" ssh-keygen -t ecdsa -b 521 -C "github-deploy-key" -f ./cluster/github-deploy-key -q -P ""
``` ```
2. Paste public key in the deploy keys section of your repository settings 2. Paste public key in the deploy keys section of your repository settings
3. Create sops secret in `cluster/base/flux-system/github-deploy-key.sops.yaml` with the contents of: 3. Create sops secret in `cluster/flux/flux-system/github-deploy-key.sops.yaml` with the contents of:
```yaml ```yaml
# yamllint disable # yamllint disable
apiVersion: v1 apiVersion: v1
@@ -481,19 +487,19 @@ The benefits of a public repository include:
``` ```
4. Encrypt secret: 4. Encrypt secret:
```sh ```sh
sops --encrypt --in-place ./cluster/base/flux-system/github-deploy-key.sops.yaml sops --encrypt --in-place ./cluster/flux/flux-system/github-deploy-key.sops.yaml
``` ```
5. Apply secret to cluster: 5. Apply secret to cluster:
```sh ```sh
sops --decrypt cluster/base/flux-system/github-deploy-key.sops.yaml | kubectl apply -f - sops --decrypt cluster/flux/flux-system/github-deploy-key.sops.yaml | kubectl apply -f -
``` ```
6. Update `cluster/base/flux-system/gotk-sync.yaml`: 6. Update `cluster/flux/flux-system/flux-cluster.yaml`:
```yaml ```yaml
--- ---
apiVersion: source.toolkit.fluxcd.io/v1beta2 apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: GitRepository kind: GitRepository
metadata: metadata:
name: flux-installation name: flux-cluster
namespace: flux-system namespace: flux-system
spec: spec:
interval: 10m interval: 10m