jarvusinnovations/cluster-template

cluster-template's Issues

embed github workflows in template repo?

Would it make sense to embed a standard deploy flow within the cluster-template repo? Or should that be left to downstream repos to paste and tailor

publish GitHub action to apply a holobranch to a k8s cluster

Publish a javascript action for deploying a holobranch to a cluster

Potential inputs:

• holobranch: Name of holobranch containing Kubernetes content
• kubeconfig: Contents of kubeconfig file to use for authentication
• ref: Commit-ish to read holobranch from (defaults to action context)
• diff-since: Commit-ish of the last deployed source to compute a diff from to apply a changeset to the cluster
  • only way to have k8s resources get deleted when they're removed from git
  • defaults to unset, so entire content tree gets applied recursively
  • might typically be set to the previous head github action variable in pull request events
• namespace: Namespace to apply manifests within, defaults to whatever is in kubeconfig

If the action is triggered from a PR, it should post comments back to the PR throughout the deploy process, documenting when projection starts, when deployment starts, each cohort of resources and their results, and the final result

Add lens for loki

minimize cluster-deployer clusterrole

Some projects are using a clusterrole provided in the jarvus library to create auth for github actions to kubectl diff and kubectl apply the whole cluster. The current example uses total * wildcards, perhaps the verbs could be restricted and still support deployment?

Also, should the manifests for such a role be baked into the cluster-template?