Skip to content

Latest commit

 

History

History
69 lines (41 loc) · 3.42 KB

README.md

File metadata and controls

69 lines (41 loc) · 3.42 KB

#TODO

Whole this example needs testing.

Cluster Example

This example reflects a more real-world scenario. We are starting with a completely empty cluster, then use a "cluster seed" custom resource (CR) to provision all components and end up with a fully functioning and fully configured Kubernetes cluster.

Video

You can watch a video of this demo here: https://youtu.be/W__MvizKo3w

Structure

In order to keep things simple, we're going to use the same git repo with a folder structure under it. In the real world, you would break out the various team folders into at least one repo each. How exactly this would look like, heavily depends on your requirements and organizational structure.

cluster-seed-tree.png

  1. Eunomia needs to be initially installed via whatever orchestration you use for your Kubernetes installation. In our example, we simply execute it via the command line.

  2. The cluster seed is the main custom resource and uses a service account with superpowers (cluster-admin), since it is responsible for all the cluster-level tasks.

  3. The cluster seed provions the "team seeds", which all use service accounts with less access (you delegate responsibilities to those teams). It also provisions resources that are needed to run the whole K8S cluster (monitoring, logging, etc.). Our example showcases how Eunomia is used to manage itself.

  4. The team seeds manage the various applications. In our example, each team deploys 3 demo hello-world applications that are completely managed through GitOps.

This is it! You now have a fully functiontioning and fully configured K8S cluster!

Executing the demo

# Deploy the operator pre-requisites, which require cluster-admin access
helm template -f examples/cluster/teams/platform/eunomia-operator/parameters/values.yaml deploy/helm/prereqs/ | kubectl apply -f -

# Deploy the operator
helm template -f examples/cluster/teams/platform/eunomia-operator/parameters/values.yaml deploy/helm/operator/ | kubectl apply -f -

# Deploy the cluster seed
helm template -f examples/cluster/teams/platform/cluster-seed/parameters/values.yaml examples/cluster/teams/platform/cluster-seed/templates/ | kubectl apply -f -

At this point the cluster should be "magically" configuring itself and within a few minutes all resources should be available.

# Watch the magic happening
kubectl get pods --all-namespaces -w

Using your own repo

If you would like to test with your own repo, we added a simple overwrite for the main repo URL.

Simply set URI to your eunomia repo, and REF to the Git reference. For example:

export URI="https://github.com/Smiley73/eunomia"
export REF="splithelm"

# Deploy the operator pre-requisites with custom repo, which require cluster-admin access
helm template -f examples/cluster/teams/platform/eunomia-operator/parameters/values.yaml deploy/helm/prereqs/ --set overwrite.uri="${URI}" --set overwrite.ref="${REF}" | kubectl apply -f -

# Deploy the operator with custom repo
helm template -f examples/cluster/teams/platform/eunomia-operator/parameters/values.yaml deploy/helm/operator/ --set overwrite.uri="${URI}" --set overwrite.ref="${REF}" | kubectl apply -f -

# Deploy the cluster seed with custom repo
helm template -f examples/cluster/teams/platform/cluster-seed/parameters/values.yaml examples/cluster/teams/platform/cluster-seed/templates/ --set overwrite.uri="${URI}" --set overwrite.ref="${REF}" | kubectl apply -f -