lytedev/k8s-clusters
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Use installed apiversion

Browse source 
I gathered this by using `kubectl api-resources | grep -i helmrelease`
This commit is contained in:
Daniel Flanagan 2022-02-08 16:44:26 -06:00
parent 284d72727d
commit 2daddc7a3c
Signed by: lytedev
GPG key ID: 5B2020A0F9921EF4
2 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
cluster/home/longhorn-system/longhorn-helm.yml
View file

@ -1,4 +1,4 @@
apiVersion: helm.fluxcd.io/v1 apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease kind: HelmRelease
metadata: metadata:
name: longhorn name: longhorn

3
readme.md
View file

@ -28,6 +28,9 @@ Before we interact with the cluster, we have some manual work to do.
- Have `python3` installed - Have `python3` installed
- Need to be `ssh`-able from a controller (my workstation) - Need to be `ssh`-able from a controller (my workstation)
- `curl -L files.lyte.dev/key.pub >> ~/.ssh/authorized_keys` - `curl -L files.lyte.dev/key.pub >> ~/.ssh/authorized_keys`
- Nodes must support Longhorn: https://longhorn.io/docs/1.2.3/deploy/install/#installation-requirements
- Nodes must be running on a host filesystem that supports `file extents`
- Provisioning takes care of the rest
### Automated Provisioning ### Automated Provisioning