Not here to spoonfeed you. Just to mock you. You want to learn why Kubernetes is useful then take a fricking class. Or get a job.
2 months ago
Anonymous
I'm not OP. I do k8s garbage for a living and it's shit. You gaytrons don't know what it does or how it works and are overpaid losers who should be fired for incompetence.
Just because you're employed doesn't mean anything and makes me suspect that you're just a worthless Black person homosexual.
2 months ago
Anonymous
And I develop web apps that I then have to containerize, deploy, and maintain in a K8s cluster. My experience is K8s is a godsend for maintaining these things and keeping uptime high so our customers b***h at us less. Sounds like you've got a skill issue.
to be an "agnostic" runtime for your shitware. that's almost about it. It's not very good, but it works if you need half assed, mostly-stateless code to be executed and ideally have it run in multiple places.
don't believe the lies of scale though, it will give you redundancy assuming you properly set up external dns and a bunch of other shit, but that's about it.
reminder that k8s won't save you from shitty software btw.
In fact, in many respects, software that doesn't just outright fail in the case of any infrastructure related error will continue to fail forever until someone complains.
the other warning I have to k8s anons, avoid Azure AKS or if you go with AKS, make sure to byo storage and not use Azure CSI. Azure CSI is based on SMB3 and (You) will have a bad time.
The fact that something as basic as storage isn't prescribed by k8s is one of the many things about it that make it overly complex and broken. It's good for a very narrow case of software built a very specific way and avoiding state.
oh and, remember, IPv4 is a limited resource and if your cluster is xbox heug, you will very easily use over 2^16 - 1 IPs easily.
Most shitware can't handle IPv6 ULAs and it's complicated to setup NAT64 for your cluster, pods, etc as well. networking is a shitshow just like storage.
also, make sure you talk to your networking team before your moronicly start squatting on 192.168/16, random 10/x subnets or 172.16/12's
oh and, remember, IPv4 is a limited resource and if your cluster is xbox heug, you will very easily use over 2^16 - 1 IPs easily.
Most shitware can't handle IPv6 ULAs and it's complicated to setup NAT64 for your cluster, pods, etc as well. networking is a shitshow just like storage.
also, make sure you talk to your networking team before your moronicly start squatting on 192.168/16, random 10/x subnets or 172.16/12's
SMB != Linux semantics.
example
you have three (mis)configured software which writes out a logfile and they write to the same file.
they have log rotate logic built in
one deletes, other 2 can no longer rotate/reopen because Linux will ENOENT a file that will be enumerated by readdir.
the fact is Windows does not behave like Linux and the CIFS driver (Linux) does a lot of weird shit to cover up the semantics mismatch.
btw this is an example that happened to me. services started crash looping because they literally could not open their logfile or rotate it. it was hilarious.
I didn't write the software or configmaps and yet I had to fix it.
this is just ONE example as well. I have other examples where heisenbug file-handles were keeping files from being replaced/deleted/opened.
only recently did Azure add file-handle force closing into azure-cli and you don't need to deal with this stupid bullshit Powershitter thing Azure is supposed to use.
Modern devs are so fricking moronic that the only way that you can make their software work is to ship the machine the dev team is using (since it werks on their machines, after all.)
You would understand if you were employed.
FPBP. Came here to say this.
employed cuckolds who don't know how to actually describe anything will be our downfall.
Not here to spoonfeed you. Just to mock you. You want to learn why Kubernetes is useful then take a fricking class. Or get a job.
I'm not OP. I do k8s garbage for a living and it's shit. You gaytrons don't know what it does or how it works and are overpaid losers who should be fired for incompetence.
Just because you're employed doesn't mean anything and makes me suspect that you're just a worthless Black person homosexual.
And I develop web apps that I then have to containerize, deploy, and maintain in a K8s cluster. My experience is K8s is a godsend for maintaining these things and keeping uptime high so our customers b***h at us less. Sounds like you've got a skill issue.
>employed cuckolds
unreal cope
truth hurts wagie.
to be an "agnostic" runtime for your shitware. that's almost about it. It's not very good, but it works if you need half assed, mostly-stateless code to be executed and ideally have it run in multiple places.
don't believe the lies of scale though, it will give you redundancy assuming you properly set up external dns and a bunch of other shit, but that's about it.
Thank you anon.
useless shit for an individual person
imagine learning this shit just to get employed
i only learn shit that is useful to me
reminder that k8s won't save you from shitty software btw.
In fact, in many respects, software that doesn't just outright fail in the case of any infrastructure related error will continue to fail forever until someone complains.
the other warning I have to k8s anons, avoid Azure AKS or if you go with AKS, make sure to byo storage and not use Azure CSI. Azure CSI is based on SMB3 and (You) will have a bad time.
The fact that something as basic as storage isn't prescribed by k8s is one of the many things about it that make it overly complex and broken. It's good for a very narrow case of software built a very specific way and avoiding state.
oh and, remember, IPv4 is a limited resource and if your cluster is xbox heug, you will very easily use over 2^16 - 1 IPs easily.
Most shitware can't handle IPv6 ULAs and it's complicated to setup NAT64 for your cluster, pods, etc as well. networking is a shitshow just like storage.
also, make sure you talk to your networking team before your moronicly start squatting on 192.168/16, random 10/x subnets or 172.16/12's
no one is reading this LOL get fricked glowie
>The fact that something as basic as storage isn't prescribed by k8s is one of the many things about it that make it overly complex and broken
moron
what's wrong with SMB
SMB != Linux semantics.
example
you have three (mis)configured software which writes out a logfile and they write to the same file.
they have log rotate logic built in
one deletes, other 2 can no longer rotate/reopen because Linux will ENOENT a file that will be enumerated by readdir.
the fact is Windows does not behave like Linux and the CIFS driver (Linux) does a lot of weird shit to cover up the semantics mismatch.
btw this is an example that happened to me. services started crash looping because they literally could not open their logfile or rotate it. it was hilarious.
I didn't write the software or configmaps and yet I had to fix it.
this is just ONE example as well. I have other examples where heisenbug file-handles were keeping files from being replaced/deleted/opened.
only recently did Azure add file-handle force closing into azure-cli and you don't need to deal with this stupid bullshit Powershitter thing Azure is supposed to use.
Modern devs are so fricking moronic that the only way that you can make their software work is to ship the machine the dev team is using (since it werks on their machines, after all.)