51–60 of 82 posts
I don't think there's going to be a shortcut to learning Kubernetes to the point where you'll be comfortable setting up a production-grade cluster. I recently went down the path of learning it. Even with 6 years of experience using Docker and ~10 years of general deployment / Linux / sysadmin'y experience it took something like 180 hours of no screwing around time to get to the point where I was comfortable putting u…
I would say there is no fast way to do this. If you specifically want to learn Kubernetes on GCP as opposed to DevOps generally, there are many things to learn. Sure, you can get something basic running very quickly but if you are talking about production systems, "ramp up"? then there are many things to learn, understand and avoid and this takes an amount of time. For an example, as a very experienced Dev and Ops pe…
I would look at these topics and in this order: 1. Containerisation - can you build a hello world web app in any language then Dockerise it. 2. Now break it into two containers - one is the original hello world but now it calls an API on a 2nd container that responds with hello world in one of 10 different languages. Just hard code this the point is that it’s now 2 containers for your “app”. 3. Create a Docker reposi…
16. Avoid helm.
I see a lot of things that has to be solved on your own even when using Helm. I find their templates repulsive. But "avoid helm" is not an advise, really. How do you suggest to structure, version, deploy, encapsulate with important metadata your deployment descriptions? How do you package it? Is there anything else that integrate with larger tools like Rancher so well?
As the former owner of GKE at our company, read the official k8s docs. They are good. Read them all.
Here's a quick question: has anyone made a single page reference for the entirety of the Kubernetes manifest spec? E.g. everything that should come out of the box, except CRDs? For example, for Docker Swarm and the Compose format, you have this: https://docs.docker.com/compose/compose-file/compose-file-v3...
[0] https://kubernetes.io/docs/reference/generated/kubernetes-ap...
[1] kubectl explain deploy --recursive
Earlier quoted context omitted.
16. Avoid helm.
Why? What's the alternative? I see a lot of things that has to be solved on your own even when using Helm. I find their templates repulsive. But "avoid helm" is not an advise, really. How do you suggest to structure, version, deploy, encapsulate with important metadata your deployment descriptions? How do you package it? Is there anything else that integrate with larger tools like Rancher so well?
I would look at these topics and in this order: 1. Containerisation - can you build a hello world web app in any language then Dockerise it. 2. Now break it into two containers - one is the original hello world but now it calls an API on a 2nd container that responds with hello world in one of 10 different languages. Just hard code this the point is that it’s now 2 containers for your “app”. 3. Create a Docker reposi…
- Do the container 101 hands-on workshop (bottom of the page)
- Do the Kubernetes 101 hands-on workshop
- ???
- Profit! build and deploy applications on ANY kubernetes (not just GCP)
And then look into the GCP specifics for k8s (GKE), networking, DNS, load balancing, storage, monitoring, etc...
Earlier quoted context omitted.
16. Avoid helm.
Why? What's the alternative? I see a lot of things that has to be solved on your own even when using Helm. I find their templates repulsive. But "avoid helm" is not an advise, really. How do you suggest to structure, version, deploy, encapsulate with important metadata your deployment descriptions? How do you package it? Is there anything else that integrate with larger tools like Rancher so well?
A DevOps guy I worked with at a previous job spoke very highly of the courses at https://acloudguru.com/
Kubernetes is like the Javascript of NPM, a new tool every week, very good at complicated things, but simple things are complicated. It seems to be dominant docker server management atm, but not sure if it will stay like that.
I'm sorry but what you wrote I find very untrue. K8s is bloat, but comparing it to NPM is very unfair towards K8s. I often see developers or admins who ask questions how to setup their "simple" setup in plain docker on dev machine, while all they have trouble with - networking, volumes, exposing services - is actually very simple with minikube. There is more cool learning resources as well, IMO. It's even easier if y…