From c4eec906b37ef105a52966ffdd0c0a0997a04c54 Mon Sep 17 00:00:00 2001 From: Jerome Petazzoni Date: Sat, 13 Jul 2019 11:22:43 -0500 Subject: [PATCH] Tweak what's next --- slides/k8s/whatsnext.md | 71 ----------------------------------------- 1 file changed, 71 deletions(-) diff --git a/slides/k8s/whatsnext.md b/slides/k8s/whatsnext.md index 48ec0550..f284472f 100644 --- a/slides/k8s/whatsnext.md +++ b/slides/k8s/whatsnext.md @@ -136,77 +136,6 @@ And *then* it is time to look at orchestration! --- -## HTTP traffic handling - -- *Services* are layer 4 constructs - -- HTTP is a layer 7 protocol - -- It is handled by *ingresses* (a different resource kind) - -- *Ingresses* allow: - - - virtual host routing - - session stickiness - - URI mapping - - and much more! - -- [This section](kube-selfpaced.yml.html#toc-exposing-http-services-with-ingress-resources) shows how to expose multiple HTTP apps using [Træfik](https://docs.traefik.io/user-guide/kubernetes/) - ---- - -## Logging - -- Logging is delegated to the container engine - -- Logs are exposed through the API - -- Logs are also accessible through local files (`/var/log/containers`) - -- Log shipping to a central platform is usually done through these files - - (e.g. with an agent bind-mounting the log directory) - -- [This section](kube-selfpaced.yml.html#toc-centralized-logging) shows how to do that with [Fluentd](https://docs.fluentd.org/v0.12/articles/kubernetes-fluentd) and the EFK stack - ---- - -## Metrics - -- The kubelet embeds [cAdvisor](https://github.com/google/cadvisor), which exposes container metrics - - (cAdvisor might be separated in the future for more flexibility) - -- It is a good idea to start with [Prometheus](https://prometheus.io/) - - (even if you end up using something else) - -- Starting from Kubernetes 1.8, we can use the [Metrics API](https://kubernetes.io/docs/tasks/debug-application-cluster/core-metrics-pipeline/) - -- [Heapster](https://github.com/kubernetes/heapster) was a popular add-on - - (but is being [deprecated](https://github.com/kubernetes/heapster/blob/master/docs/deprecation.md) starting with Kubernetes 1.11) - ---- - -## Managing the configuration of our applications - -- Two constructs are particularly useful: secrets and config maps - -- They allow to expose arbitrary information to our containers - -- **Avoid** storing configuration in container images - - (There are some exceptions to that rule, but it's generally a Bad Idea) - -- **Never** store sensitive information in container images - - (It's the container equivalent of the password on a post-it note on your screen) - -- [This section](kube-selfpaced.yml.html#toc-managing-configuration) shows how to manage app config with config maps (among others) - ---- - ## Managing stack deployments - The best deployment tool will vary, depending on: