Brainstorm big picture OAS installation workflow
Discussion topics / open questions
-
From where do we deploy ? Laptop or OAS host Right now, install scripts a[re copied over to the cluster, then you login and install from there. While this has the advantage that it doesn't require an open k8s API port, this approach has its limitations in managed k8s setups where sometimes you don't even have ssh access to the nodes/masters by default. The overall practice is that you deploy from your machine and I'd like OAS to follow that.
Actionable items
-
Rip the k3s setup out of the OAS setup to put in a separate repo - This repo can/should function as the recommended way of setting up Kubernetes on a VPS for people that want to use OAS, but can also function as a generic way of setting up k3s on a VPS for other purposes.
- This has not completely been done yet, but you can now run
python -m openappstack <cluster> install --no-install-openappstack --install-kubernetes
to only set up the cluster. Installing OAS is a separate set of scripts in theinstall
folder.
-
Look into setting up OAS on a devstack/local machine (#528)
Done
-
Look into ArgoCD / or the flux2 upgrade (#677 (closed)) -
Change “local flux” so that it doesn’t set up the Git repository on the host machine - Local flux was removed, update to flux 2 is finished (!405 (merged)) and ArgoCD turned out to be not the ideal candidate because it is about as monolithic as Flux 1, whereas flux 2 is super flexible.
-
-
How can we do secret management? (#73 (closed)) - See comment in #73 (closed)
Notes from previous meetings
From the meeting notes 2021-03-10:
- How can we bootstrap this?
- We can do it next week. Maarten will prepare a plan and everyone can poke holes in it in the meeting.
- To take into account: how would we install OAS on something like k3os, or managed k8s, where you don’t have (python) binaries on the target system that
- Maybe we want to split the repo?
- setting up instance
- setting up the apps using k8s apis
- There is PF funding available to do exactly this
- Meeting moment: Thursday 18 March, 10:30
Edited by Varac