Kubernetes: Difference between revisions
Brian Wilson (talk | contribs) Created page with "I started with plain Docker then moved to using Docker Compose so that I could manage groups of containers. When I found out healthcheck in Docker and Docker Compose reported status but would not restart unhealthy container(s) for me, I started looking at Docker Swarm. Months and years passed and [https://kubernetes.io/ Kubernetes] became the hip thing so here I am, trying to jump past Docker Swarm straight to Kubernetes. Henceforth "K8s". An example of tha..." |
Brian Wilson (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
I spent at least an hour looking at Kubernetes. I did not see a reason to use it over [[Docker Swarm]] so I am back on that. Don't even bother to read the rest of this page. | |||
I started with plain [[Docker]] then moved to using [[Docker Compose]] so that I could manage groups of containers. | I started with plain [[Docker]] then moved to using [[Docker Compose]] so that I could manage groups of containers. | ||
| Line 5: | Line 7: | ||
Months and years passed and [https://kubernetes.io/ Kubernetes] became the hip thing so here I am, trying to jump past Docker Swarm straight to Kubernetes. Henceforth "K8s". | Months and years passed and [https://kubernetes.io/ Kubernetes] became the hip thing so here I am, trying to jump past Docker Swarm straight to Kubernetes. Henceforth "K8s". | ||
An example of that "time passing" thing, I spent a year making ArcGIS Enterprise work in Docker Compose (and never finished), now Esri supports it in Kubernetes. | An example of that "time passing" thing, I spent a year making ArcGIS Enterprise work in Docker Compose (and never finished), now Esri supports it in Kubernetes. | ||
== Single node? == | == Single node? == | ||
| Line 23: | Line 23: | ||
# A way to maintain the certificates for HTTPS (certbot) | # A way to maintain the certificates for HTTPS (certbot) | ||
# A sample web server. | # A sample web server. | ||
== Controller == | |||
I am going with that guide's suggestions so, it looks like I can try out minikube on Bellman. | |||
== Resources == | == Resources == | ||
The home page. https://kubernetes.io/ | The home page. https://kubernetes.io/ | ||
Latest revision as of 18:36, 21 April 2023
I spent at least an hour looking at Kubernetes. I did not see a reason to use it over Docker Swarm so I am back on that. Don't even bother to read the rest of this page.
I started with plain Docker then moved to using Docker Compose so that I could manage groups of containers.
When I found out healthcheck in Docker and Docker Compose reported status but would not restart unhealthy container(s) for me, I started looking at Docker Swarm.
Months and years passed and Kubernetes became the hip thing so here I am, trying to jump past Docker Swarm straight to Kubernetes. Henceforth "K8s". An example of that "time passing" thing, I spent a year making ArcGIS Enterprise work in Docker Compose (and never finished), now Esri supports it in Kubernetes.
Single node?
Well, at this moment in time all I want is a working healthcheck / restart thing. Maybe K8s offers a nice web interface? I have no idea. Once I have a single node functioning 100%, I can think about > 1 node. (I have Raspberry Pis!!!)
Even if you pine for a life in the Cloud with hundreds or thousands of servers at your beck and call, a single node is a good starting point.
Here is a guide! I love guides. https://bell-sw.com/announcements/2022/09/14/how-to-create-a-single-node-kubernetes-cluster/ Dmitry makes the case for a single node.
For a test, what I want is
- Varnish as a reverse proxy, with HTTPS supported.
- A way to maintain the certificates for HTTPS (certbot)
- A sample web server.
Controller
I am going with that guide's suggestions so, it looks like I can try out minikube on Bellman.
Resources
The home page. https://kubernetes.io/
