2 ms·
Do keep a gitops folder / repository to keep your cluster in sync with expectations, do not let adhoc edits become the norm. Use tools like kustomize to reduce
by CameronBarre 7y ago
Do keep a gitops folder / repository to keep your cluster in sync with expectations, do not let adhoc edits become the norm.
Use tools like kustomize to reduce proliferation of duplicate k8s resource files.
Do make sure you are using health and liveness checks.
Definitely take care to specify resource requests and limits.
Do use annotations to control provider resources, rather than manually tweaking provider resources that are auto generated by basic k8s files with no annotations.
Aggregate your logs.
- TuringNYC 7y agoCould you comment more on your log aggregation tooling? Did you set up an ELK stack? Self installed or paid? That is the most frustrating part for me — why some of the tooling is not built in.
- CameronBarre 7y agoWe don't have the most sophisticated setup, we're on AWS so we use a fluentd daemonset to ship logs to cloudWatch. In many respects kubernetes is just a really nice piece of marble to start with, you still have to carve your statue. If certain tooling was built-in they would be making stack-specific subjective decisions for you, which is somewhat antithetical to the kubernetes model. They'll make critical operational decisions for you (e.g. core competencies like scheduling work across a pool of resources), but when it comes to supporting tooling, you still have to make some decisions on your own. For a lesser burden, there are most likely helm charts or other prepackaged log aggregation tools out there.