adding definitions to cheatsheet
draft for part 3
redoing migration tool topic
adding content for service exposure
adding images and source
improving content
finishing draft of 'expose services'
drafting section on healthchecks
more content
finishing healthcheck draft
minor edits
drafting schedule workload doc
adding image
adding a bunch of images and a wip draft of scheduling workloads
adding gifs
adding more content
minor changes
linked files in sequence
adding content to last two topics
adding image
adding video
updating content, adding comments
adding new content
changing occurences of 2.0 to 2.x and 1.6 to v1.6
made updates per Denise
adding new content
fixing typos
changed 'kubernetes yaml' to 'kubernetes manifest'
edits to get started
app migration
updating headers and titles
fixing images
made Kubernetes intro section
checking in progress
adding directives table, updating image
editing service exposure and app migration topics
continuing edits
pushing all kinds of improvements
working on service scheduling
updates for service deployment
editing service discovery
updaing load balancer section
finishing draft, rdy for it to be trashed by Prachi/Alena :)
The TLS args given in this example were misleading, because they were preventing the Docker daemon to listen on the port 2376 (even if the daemon still succeeds to start...).
The reason is very simple: when using `sudo ros tls gen --server ...`, the server and CA certificates will be stored in `/etc/docker/tls`. But their paths were given as relative paths, and not absolute paths, in the previous example.
Currently, if you take the contents of `ingress-default-cert.yaml` and paste it into your RKE config, the secret will get created in the namespace `default` which is not desired behavior. By specifying `-n ingress-nginx`, the secret will be created in the correct namespace.
Mark Bishop
Sebastiaan van Steenis
dnoland1
Jan B
Denise
Adrian Goins
Alexandre Figura
Chris Kim