Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "kubernetes"
Interviewer: Do you know what Kubernetes is?
Dev: Yeah, that’s the greek god of spending money in the cloud.
Interviewer: Actually Kubernetes is an orchestration tool. Have you not been on a project that uses it yet?
Current work project is microservices architecture out of 4 - 8 components.
It is fully Infrastructure as a Code automatized. I just change somewhere code, git pushing
And it automatically invokes Gitlab CI, terraform, ansible, kubernetes helm charts.
Auto checking itself with unit and integration tests in autoredeployed staging env. Then it saves tested results to docker registry and asks for one button verificating click to be rereleased to prod.
I just go for drink or eat food. While all the stuff is happening.
And I am proud that all the infrastructure, backend and frontend I made on my own.
I don't need to remember how to Deploy it. It is all automatized3
Just let me be a programmer. Why do I have to learn yaml and deploy an app with 100 lines of code to a kubernetes cluster with literally 0 users?
May be just me, but I am quite frustrated with complexity of systems nowadays, even more how it’s became a norm for developers to import a library for every little sh*t…
Like, do you even need to import that OSS library, can’t you make it without it? Is it really worth it to import that monstrous library of 10k loc, just so you can save writing those 50loc for just once?
It almost feels like it’s driven by logic “if you don’t own the code, then you don’t need to maintain it”. But ironically you still need to mantain it, only now not the code (best case), but the library itself. You have to upgrade it (for security, bug fixes) and you better pray there’re no breaking changes. And if you encounter an edge case/bug that no one addressed yet, then well, I bet you wished you didn’t use that library in the first place.
It’s so much easier to support small piece of code within your codebase, than fix a bug in a library, that possibly has thousands of unnecessary dependencies, enormous abstraction trees, and infinity loc to support all possible use cases, which your project doesn’t even care about.
Just to make it clear, I am not talking, about cases where some library would really do some heavy lifting for you, it would be non-sensical not to use it in that case.
And talking about complexity, let’s not even mention microservices, kubernetes, and other hyped stuff…
Does anyone else shares the sentiment?17
There you are, fiddling with next.js webpack settings, because your isomorphic JS-in-CSS-in-JS SSR fallback from react-native-web to react-dom throws a runtime error on your SSR prerendering server during isomorphic asynchronous data prefetching from Kubernetes backend-for-frontend edge-server with GraphQL.
You have all that tech to display a landing page with an email form, just to send spam emails with ten tracking links and five tracking beacons per email.
Your product can be replaced by an Excel document made in two days.
It was developed in two years by a team of ten developers crunching every day under twelve project managers that can be replaced with a parrot trained to say “Any updates?”
Your evaluation is $5M+. You have 10,000 dependency security warnings, 1000 likes on Product Hunt, 500 comments on Hacker News, and a popular Twitter account.
Your future looks bright. You finish your coffee, crack your knuckles and carry on writing unit tests.5
Fuck, they updated the internal move policy in my company from 1 year 9 months to move to another team to be at least in the same team for 2 years.
I hope I can find a way to gtfo faster because I am honestly so tired of this shit, the tasks are getting too repetitive, my boss is useless, spends her time shopping instead of working and being stuck with a bunch of juniors means you only have the internet to learn something new.
I really want to start delving more into PAAS and start working with docker and kubernetes. Oh well, guess we'll have to wait and see.16
I am back after 5 years
It's been a long time
After working for a shitty company, I ended up working for a startup for an interesting big project as a software architect
It was a good experience just for some stuff, but I hated every moment we needed to build some demo or prototype for potential customers or allies
I was tired... 2 years of demoing is too much. And finally I got a Senior Devops in this company working in Kubernetes
I finally discovered my role and my position, I want to solve problems for other devs and myself. I help anyway in the final product, because fast and reliable build and release cycle need to be a must
I wish everybody could find their main role. I took 12 years to find mine lol
To be honest, I'm not as excited as I was 6-7 years ago when our tech industry seen a big leap, where these ML/Deep Learning algorithms were out performing humans, Apache Spark out perfomed Hadoop in distributed computing, Docker/Kubernetes are the new phenomenon in software development and delivery, Microservices architecture, ReactJS virtual DOM concepts were so cool.
Really though, I've come realise that these software trends come and go. All you need to do is adapt and go with the flow.3
It's dangerous to be curious. And have time to spare.
This morning I was in THAT state and decided to spin up kubernetes inside an... Alpine docker container.
The day has almost passed and I think I'll have enough tinkering left for the night.
yay........... I guess...7
Can people stop using Kubernetes and over engineering shit for services which get like, 10 users at most ? Thank you.20
One good thing about working at a shitty place is you end up knowing what not to do by just pure pain.
I once consulted for a company who had the latest tech - kubernetes, bit bucket, you name it. But it didn't matter. The code was shit. It's not about the tech, it's always about the people that use the tech.5
i really hate that almost everything i've done in IT has been grouped into "SRE"
wtf is it? what's the job? well it depends
maybe you'll be working with kubernetes and cloud clusters like AWS, microservice type things
maybe it will be web dev, front end or back end, similar to a full stack position
or hell, you could just be a sys admin with a fancy title
how in the FUCK am i supposed to find a job when you can't -negate -terms or find anything meaningful with a god damn search term or job title???
edit: oh, i missed one -.- you could just be a software engineer. because you know, software reliability engineer i guess2
RAAAAAAH fuck fuck fucking shit!!! Fuck jest Typescript "on the fly" compilation esModuleInterop typeroots, missing definitions jest ts-ignore and xtest everywhere, manual npm linking with different pkg mgrs & pub to a private registry, building docker images locally and doing tag management across git, docker & kubernetes then cross fingers that prod which has 0 common setup with local & test somehow works, open architecture "tickets" and wait months before they resolve, then repeat ad infinitum. How the fuck can I be productive when I need to be all over the place all the time and deal with these meta-code shenanigans. I just wanna code, damned3
Doing a technical assessment. Slightly different stack than what I am used to!
- NGINX instead of Traefik
- Kubernetes instead of Docker Swarm
Just because the stack is different, anxiety / impostor syndrome is kicking in. I'm proud of myself for commanding my brain and body to execute:
- find simplest straightforward tutorial
The chemicals inside my body are all over the place. I really want to move out of my current job!!
why the fuck those images wouldn't load? they come corrupt from K8S, but they are fine if I run the container locally, like... wtf? is Ingress NGINX doing something to them or did I configure something wrong?!15
Oh my.. I think I'm enjoying molesting kubernetes :)
A while ago I got pissed at k8s because with 1.24 they brought backward-incompatible changes, ruling my cluster broken. Then I thought to myself: "why not create a Docker image that would run kubernetes inside? Separate images for control plane, agent and client"
Took me a while, but I think tonight I've had a breakthrough (I love how linux works...)!! The control-plane is spinning up!! Running on containerd
Still needs some work and polishing, but hey! Ephemeral k8s installation with a single docker-run command sure sounds tempting!
P.S. Yes, I know there is `kind` and 'kinder', but I'm reluctant to install a separate tool that installs a set of tools for me. Kind of... too shady. Too many moving parts. Too deeply hidden parts I may have to fix. Having a dumb-simple Dockerfile gives me the openness, flexibility and simplicity I want. + I can always use it as a base image to add my customizations later on! Reinstalling a cluster would be a breeeeeeze6
Finally!! I've managed to molest containerd and kubernetes!!
Now I can run k8s in a container :) yayy!!!
Next: figure out a way to automatically and transparently share certs6
After upgrading to kubelet 1.24 kubernetes won't even start. Complains about an unrecognized flag "--network-plugin=cni". And stackoverflow has nothing to offer to work around it.
God I hate backwards-incompatible software updates. Esp w/o vendor's scripts automatically porting old version configs to match the new configuration convention.
Now I have to learn all about something big, called dockershim.
Fuck! I so don't want to spend my whole day on this...
It's not very linuxish to push breaking updates w/o any bpo mechanism, esp for a software that's a part of the linux foundation :|15
Dear Lord, please stop people from enforcing standards and bypassing them themselves.
Take kubernetes for example. Since v1.24 CRI has been announced as the standard, and kubernetes is shifting to live by it.
But it's not.
Yes, it's got the CRI spec defined and the unix://cri.sock used for that standardised communication. What nobody's telling you, is that that socket MUST be on the same runtime as the kube. I.e. you can't simply spin up a dockerd/containerd/cri-o server and share its CRI socket via CIFS/NFS/etc. Because kube-cp will assume that contained is running on the same host as cp and will try to access its services via localhost.
So effectively you feed the container via a socket to another machine, it spins up the container and that container tries to
- bind to your local machine's IP (not the one's the container is running on)
- access its dependencies via localhost:port, while they are actually running on your local machine (not the CRI host)
I HOPE this will change some day. And we'll have a clear cut between dependencies and dependents, separated by a single communications channel - a single unix socket. That'd be a solution I'd really enjoy working with. NOT the ip-port-connect-bind spaghetti we have now.4
Job offer, searching for somebody with (amongst others):
- React, Angular
- Azure, Kubernetes, Redis
- Mongo, MySQL
Why do they want to fill 3-4 positions with a single person? I'm afraid I'm only 2 of those people they're searching for.7
kubernetes is just a config file
docker is just a chroot with quotas
i may be oversimplifying but i fail to see it as rainbows and magical as ppl make it out to be8
Anybody had experience with Hashicorp Nomad for smaller deployments (personal in this case)? Thinking of using it after having done it too many times with complex Kubernetes and Docker... 😅 Also don't wanna run this thing bare bones as i have a whole bunch of services to deploy together.
Does a basic Kubernetes ClusterIP Service run on OSI Layer 4? There's musings of calling a Service Mesh 4.5, but out-of-the-box Kubernetes services... What OSI layer would you put them on?9