Ask HN: What is the fastest way to ramp up on DevOps, k8 and GCP?

1

A Cloud Guru

#Education #Online Learning #Online Courses 137 social mentions

2

Kubernetes

We put together the Kubernetes Developer Learning Center for folks looking to bootstrap their k8s hands-on experience: https://www.getambassador.io/kubernetes-learning-center/ Combined with the K8s official docs https://kubernetes.io/docs/home/ and GCP getting started guide, this will give you a good tour of the tech: https://cloud.google.com/gcp/getting-started For a general overview of DevOps and the principles behind this, you can't go wrong with reading "The DevOps Handbook" and researching the "Accelerate" metrics.

#Developer Tools #DevOps Tools #Containers As A Service 280 social mentions

That's a really nice documentation page, however what's missing in my eyes is an example or two for each parameter in YAML format. Personally, when attempting to use Docker Swarm, things like that were immensely useful, even more so for Hashicorp Nomad and its somewhat niche HCL. I know that people like to use something like Kustomize (https://kustomize.io/) and Helm (https://helm.sh/) at least last I checked, but it's also really nice to be able to read up on everything without necessarily following tutorials and such. For example, with Docker Swarm, if I want to change how restarts would be handled, I have a really easy reference available: https://docs.docker.com/compose/compose-file/compose-file-v3/#restart_policy But with Kubernetes, in the first linked page I find a short description (just scroll down a bit or CTRL+F "restartPolicy") which doesn't offer further parameters: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#pod-v1-core To its credit, there is a link to another page as well which contains more information: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy That said, usability wise I'd have to spend more time to figure out how to get my containers/pods restarting just once every 1 minute as opposed to whatever the default is (say, low end cluster with limited resources) with Kubernetes instead of other technologies, due to this difference.

#Development #Management #Tool 48 social mentions

4

Helm.sh

That's a really nice documentation page, however what's missing in my eyes is an example or two for each parameter in YAML format. Personally, when attempting to use Docker Swarm, things like that were immensely useful, even more so for Hashicorp Nomad and its somewhat niche HCL. I know that people like to use something like Kustomize (https://kustomize.io/) and Helm (https://helm.sh/) at least last I checked, but it's also really nice to be able to read up on everything without necessarily following tutorials and such. For example, with Docker Swarm, if I want to change how restarts would be handled, I have a really easy reference available: https://docs.docker.com/compose/compose-file/compose-file-v3/#restart_policy But with Kubernetes, in the first linked page I find a short description (just scroll down a bit or CTRL+F "restartPolicy") which doesn't offer further parameters: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#pod-v1-core To its credit, there is a link to another page as well which contains more information: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy That said, usability wise I'd have to spend more time to figure out how to get my containers/pods restarting just once every 1 minute as opposed to whatever the default is (say, low end cluster with limited resources) with Kubernetes instead of other technologies, due to this difference.

#Developer Tools #DevOps Tools #Containers As A Service 134 social mentions