Polygon
/
stackspout
2
0
Fork 0
Code Issues Pull Requests Releases Activity
43 Commits 1 Branch 0 Tags 697 KiB
Shell 100%
Go to file
xeruf 39ef8084ad gitea: fix configmap typo 
Kustomization reconciliation failed: ConfigMap/stackspout/stackspin-gitea-values dry-run failed, error: failed to create typed patch object (stackspout/stackspin-gitea-values; /v1, Kind=ConfigMap): .data.values.yaml: expected string, got &value.valueUnstructured{Value:map[string]interface {}{"ingress":map[string]interface {}{"annotations":map[string]interface {}{"kubernetes.io/tls-acme":"true"}, "enabled":true, "hosts":[]interface {}{map[string]interface {}{"host":"dev.${domain}", "paths":[]interface {}{map[string]interface {}{"path":"/", "pathType":"Prefix"}}}}, "tls":[]interface {}{map[string]interface {}{"hosts":[]interface {}{"dev.${domain}"}, "secretName":"gitea-tls"}}}}}
 		2022-06-28 11:07:31 +01:00
basic gitea: fix configmap typo 2022-06-28 11:07:31 +01:00
.gitignore Fix name 2022-03-31 16:51:08 +02:00
README.md Remove podinfo 2022-04-14 10:51:41 +01:00

README.md

Example repository for customizing a Stackspin cluster

Example boilerplate for a custom flux repository which can be added to a Stackspin cluster. The main use-case is to add additional applications which are not integrated into Stackspin (yet).

For a more advanced example see the flux2-kustomize-helm-example repository. This repo's directory structure is similar to the flux2-kustomize-helm-example one.

Basic configuration

We'll start with a very basic configuration:

  • It uses a public git repo
  • No secrets are included
  • No forking/modifications needed, install as it is

Apply it to your cluster:

basic/install.sh

List the resource created by this flux repo:

kubectl -n stackspout get gitrepositories
kubectl -n stackspout get kustomizations
kubectl -n stackspout get helmreleases
kubectl -n stackspout get pods

Customizations

  • Nextcloud apps overrides
  • Gitea installed

What's next ?

There are two ways of using a custom flux repo to host your custom config/apps on a Stackspin cluster.

A) Manage secrets manually

This approach is easier to start with, because you don't need to configure your cluster to handle encrypted secrets and access to a private git repository.

  • Fork this repository into a public git repo, cloneable via https://

Everything in version control, including secrets