How to: Customise deployed services/pods/etc

[pms1969]

Although I'm pretty sure I've got my head around the physical kit (in AWS anyway), I'm not sure I quite understand yet how to customise the kubernetes setup, so that after a terraform apply, I have a setup that's ready to go as one of my environments. I'd like to make prometheus/nginx-ingress/grafana/heapster and cluo all part of the pre-deployed architecture, and I'm thinking about adding weave and maybe swapping out nginx-ingress for traefic, and I'm just starting to get around to certi-manager, and god knows what else, I think of/come across between now and the end my POC work with Kubernetes. There's so much it's mind boggling.

Is there a simple way to do this? Am I correct in thinking that I'll need to fork and amend the poseidon/terraform-render-bootkube repo to support this? Or is there a better way of attacking the problem?

Thanks for starting this repo/product too. Easily the best I've seen to date for a terraform template. The tectonic one doesn't feel like it's getting any love at present, and it's too generic to be easily followed. Especially for non-terraform ninjas.

[dghubble]

Let's please reserve issues for concrete bugs or issues. For opinions and advice, there is the IRC channel which has some fellow users. Find existing customization docs which will be updated when the story changes.

I recommend the low-level terraform-render-bootkube module only be used for manifests which are absolutely essential to produce a working cluster. Everything else can be managed the same way you normally deploy apps on Kubernetes.

Typhoon provides a minimal Kubernetes cluster on a variety of platforms. Several sets of Kubernetes manifests are maintained as optional addons you apply with kubectl. Recommendations beyond that are out of scope. How to manage apps on clusters depends very much on needs and preferences.

[dghubble]

See #140 for future plans.