Key highlights:
- New paradigm, death of DevOps
- embrace sidecar
- be careful settinf up HPA
- if you are managing 1000 + pods setup node level autoscaler (you cannot manually manage them)
- outsource every fucking thing
- storage ( nfs enabled or minimum http or smb
- ip address
- fuck, SSL every single container, not pod, fucking contianer ssl
Death to devops and please welcome NoOps
멍청한 놈.. 그딴 오픈소스를 믿냐.. 걍 파이어베이스나 쳐 배워 깝싸지 말고
And RBAC everything
i don't know where you come from, but I can see definitely you're not familar with this kind of thing. Kubernetes doesn't mean NoOps. you need DevOps more than ever. enabling SSL on the ingress controller side can make web containers accessed via https but that's not one of Kubernete's features. That's just ingress controllers.
even with Kubernetes, you have so many missing holes in your production environment. one trivial one i can think of off the top of my head is: how and where are you going to run your CI/CD pipeline? how are you going to deploy your apps?
"even with Kubernetes, you have so many missing holes in your production environment. one trivial one i can think of off the top of my head is: how and where are you going to run your CI/CD pipeline? how are you going to deploy your apps?" -> Have you ever used Kubernetes before?
Kubernetes draws a clear line between what developers vs devops are responsible for your infrastructure set up. Traditionally infrastructure/cloud required heavy SA or DevOps presence in order to operate continuous integration. Example of this is installing a new system module, you no longer need to explicitly ask your SA/DevOps to install this on the server, but you provide them with
Kubernetes/Docker resources. That's what I mean by NoOps, infrastructure is no longer a blocker in your CI.
And "you" as a DevOps or SA, you are in charge of managing hardware, Kubernetes master cluster and provide external resources (e.g. Ip address, storage, infrastructure level monitoring)
oh man. You clearly haven't operated any serious production grade Kubernetes clusters. You don't give devs access to Kubernetes directly. Yes, you don't need to ask your DevOps guy to install your app if you have your CI/CD pipeline set up. That's why you need it. You seriously don't think developers would just run `kubectl` on the production cluster to deploy, do you? That'd be a huge no no.
All resources on the cloud are abstracted, but that doesn't mean you don't need DevOps. NoOps would mean that you don't have any DevOps guys in house. You would be using some kind of serverless solution.
"h man. You clearly haven't operated any serious production grade Kubernetes clusters." -> I can already see I have provoked your DevOps egoism by mentioning the word "NoOps". Son, this is basically the inevitable future of the infrastructure world (NoOps, Serverless and stateless stack). Speaking of my experience in running production grade Kubernetes clusters, I am currently managing 1000+ pods
across few different multi-region clusters. How long have in this field for? Do you even do SCRUM or just general QA in your place? Who the hell gives full kubectl (or even gcloud) access to developers?
Well, I've been running a few k8s clusters for a pre-IPO stage company in the Bay Area, and I don't identify myself as a DevOps engineer, so let's make that clear before I point out what's wrong in your argument. NoOps doesn't have any room for interpretation. NoOps means that you don't have any personnels or dedicated team in your company to manage the infrastructure. But you DO need a dedicated-
team to run Kubernetes. so your arugment can never be true.
haha what you bring up to prove your authority makes me laugh a little bit. You do need a CI/CD pipeline of some kind. Google is your best friend. There are easy examples out there. Go look up concourse-ci or even Jenkins for starters.
"You do need a CI/CD pipeline of some kind" -> This makes me giggle because I've never worked in an environment without CI/CD setup. And I have no idea why you are emphasising it. It makes no sense in this context of the conversation. " Google is your best friend." -> Do you mean GKE? Have you even touched upon multi-cloud Kube setup before?
Then clearly you don't get the full picture of how Kubernetes works if you have a proper CI/CD pipeline setup. Kubernetes is just a tool, not a silver bullet to get rid of DevOps. You have so many missing holes to prove your "death to DevOps" argument. CI/CD was one of very apparent ones from your original post. I'll stop here since you don't seem to be understanding what I say here. Learn English