Docker / Kubernetes

[Sinbad]

Also, the costs for enterprise support from DeadRat (ptoooi IBM) or Rancher are prohibitive in South Africa.

 

[MirageF1]

Its not exactly a light hearted discussion that's easy to do in a forum format. I think if you narrow things down a lot you will get much more interaction.

Right I'll shoot.
From a DevOps angle:

1.Docker (dockershim/engine) support being deprecated from Kub v1.22/3, apparently towards year end '21.
Impact on existing installations?

2 . Looking forward, containerd or cri-o as replacement.Anyone actually involved in investigating this currently or planned/completed a switch over.

 

[Sinbad]

Right I'll shoot.
From a DevOps angle:

1.Docker (dockershim/engine) support being deprecated from Kub v1.22/3, apparently towards year end '21.
Impact on existing installations?

2 . Looking forward, containerd or cri-o as replacement.Anyone actually involved in investigating this currently or planned/completed a switch over.

No biggie.

You do not need to panic. It’s not as dramatic as it sounds.

TL;DR Docker as an underlying runtime is being deprecated in favor of runtimes that use the Container Runtime Interface (CRI) created for Kubernetes. Docker-produced images will continue to work in your cluster with all runtimes, as they always have.

If you’re an end-user of Kubernetes, not a whole lot will be changing for you. This doesn’t mean the death of Docker, and it doesn’t mean you can’t, or shouldn’t, use Docker as a development tool anymore. Docker is still a useful tool for building containers, and the images that result from running docker build can still run in your Kubernetes cluster.

Don't Panic: Kubernetes and Docker

Authors: Jorge Castro, Duffie Cooley, Kat Cosgrove, Justin Garrison, Noah Kantrowitz, Bob Killen, Rey Lejano, Dan “POP” Papandrea, Jeffrey Sica, Davanum “Dims” Srinivas Kubernetes is deprecating Docker as a container runtime after v1.20. You do not need to panic. It’s not as dramatic as it...

kubernetes.io

 

[s0lar]

Right I'll shoot.
From a DevOps angle:

1.Docker (dockershim/engine) support being deprecated from Kub v1.22/3, apparently towards year end '21.
Impact on existing installations?

2 . Looking forward, containerd or cri-o as replacement.Anyone actually involved in investigating this currently or planned/completed a switch over.

I am running containerd in multiple clusters. Totally transparent to me. Think of a docker subsystem that is purpose built to the task. Less features than needed for local dev, lightning fast, better logging .etc

 

[Solarion]

Seeing more and more Kubernetes requirements in the job market. This is something worth learning?

 

[shadow_man]

Seeing more and more Kubernetes requirements in the job market. This is something worth learning?

100% - you're relatively useless as a (good) dev nowadays unelss you understand some form of CI/CD / containerization / orchestration.

I'd recommend - the below two courses for a nice intro in to k8s with real world examples / labs that push you to certify and show employers some validated skills:

Kubernetes Certified Application Developer (CKAD) Training

Learn concepts and practice for the Kubernetes Certification with hands-on labs right in your browser - DevOps - CKAD

www.udemy.com

Certified Kubernetes Administrator (CKA) Practice Exam Tests

Prepare for the Certified Kubernetes Administrators Certification with live practice tests right in your browser - CKA

www.udemy.com

 

[shadow_man]

My biggest gripe with Kubernetes is that it feels like it's incomplete. Sure, there's a lot of functionality there, but to actually make use of it in a manageable and sustainable way you need something like rancher or openshift.
The whole paradigm of "create a yaml file then run kubectl -f" is absolutely barbaric.
If nothing else, they could at least templatise the damn thing... Run a command to create a PVC, for example, and it pops up a text editor with the yaml prepopulated in it so you can just fill in the values....

100% - we're running bare metal k8s and It's horrible compared to OpenShift / OKD in terms of the management aspects.

 

[Napalm2880]

I have seen an old school architect build microservices on his own with exe processes, only thing was that these microservices all needed to be on the same VM so when they scaled out because the server was under load, it just added more load to the server. Then in came plan B which was to deploy the entire monolith server to serarate VMs as a "micro-service" setup.

 

[Solarion]

100% - you're relatively useless as a (good) dev nowadays unelss you understand some form of CI/CD / containerization / orchestration.

I'd recommend - the below two courses for a nice intro in to k8s with real world examples / labs that push you to certify and show employers some validated skills:

Kubernetes Certified Application Developer (CKAD) Training

Learn concepts and practice for the Kubernetes Certification with hands-on labs right in your browser - DevOps - CKAD

www.udemy.com

Certified Kubernetes Administrator (CKA) Practice Exam Tests

Prepare for the Certified Kubernetes Administrators Certification with live practice tests right in your browser - CKA

www.udemy.com

Thanks I'll check these out.

 

[MirageF1]

Kubernetes alone won't help you getting a job in DevOps, a good understanding of CI/CD and automation s/w like Jenkins or Travis CI is a must as well ... just started learning this as well

I've spent a good 6 months learning more than just basic Kubernetes from the ground up, building my own HA cluster on GCP using KTHW, including accessing internal services externally securely, using ingress controller and cert manager, Letsencrypt certificates and more... Yet not seen a single position that just requires in depth Kubernetes skills alone.

 

[Solarion]

Yeah it's usually their shopping list of Kubernetes and and and and and you know, jack of all tards and master of none. Poor sod full stack does the work of several devs for a quarter of the salary. Companies have quickly latched onto this Fullstack quicksaver trend.

 

[MirageF1]

Yeah it's usually their shopping list of Kubernetes and and and and and you know, jack of all tards and master of none. Poor sod full stack does the work of several devs for a quarter of the salary. Companies have quickly latched onto this Fullstack quicksaver trend.

But in reality how many folks can confidently apply for these positions ( well paid as they are £70k+ ) with the requested skillsets.
I doubt a handful in reality.

Solid Cloud (Azure, GCP, etc) exposure, Kubernetes, CI/CD pipelines, Ansible or Terraform, and 1 or 2 programming languages like Python, Go, Ruby might get you a foot in the door...

It's tough out there. Half of India to complete against as well.

 

[shadow_man]

But in reality how many folks can confidently apply for these positions ( well paid as they are £70k+ ) with the requested skillsets.
I doubt a handful in reality.

Solid Cloud (Azure, GCP, etc) exposure, Kubernetes, CI/CD pipelines, Ansible or Terraform, and 1 or 2 programming languages like Python, Go, Ruby might get you a foot in the door...

It's tough out there. Half of India to complete against as well.

Good thing more than half of India are still currently requiring others to "do the needful" for them. Think abusing AWS, GCP, Azure etc support engineers and demanding they do their work for them. The other percentage are damn good at what they do, but those are the guys who will probably be working FAANG level jobs.

 

[_kabal_]

Use what works for you and your company and your customers.

docker(-compose) is a no brainer for local development. If you cannot clone a repo, and have it running in your browser in a couple of minutes using docker/podman, then that just seems like time that could be better spent onboarding in other areas.

we actually use docker a lot to host “mocked” “3rd party” APIs locally (mock them with express if they are small, or use wiremock with proxy enabled to generate mocks).

not all teams have dedicated “devops” engineers. These teams should NOT be managing their own k8s clusters. Much better to leverage platforms like digital ocean’s k8s, AWS fargate, etc. Worry about your product and it’s required infrastructure, rather than what is needed to keep those things running.

It’s also fine to not use docker in production.
everyone likes to claim they are working on very complicated systems, when reality is that 90+% of software is likely an front end + API / MVC and a database.
There are also obviously a lot of cases where using this technology can be the absolute right choice for you.


been a while since a good “microservices” discussion has gone down.
If you have multiple services/APIs that are making http calls to each other, congratulations, you are doing microservices wrong - welcome to distributed monolith hell