Recently, I am preparing for CKAD exam and I need to see the doc. I found there are too many concepts, items and configurations, even more and more. It is really a big challenge for me to make it. For example, Job, I feel it has some unuseful configs, like success policy and job patterns. Maybe users actually don’t need them or they can process in their own applications.
K8S is not OS, it shouldn’t bear too much for users. Although it is making things easier, itself is being more complex. I think is not a good way. Why not cut off some inessential and marginal functions, to make K8S lean and easy-to-use, not fat and complex ?
Are you just learning Kubernetes to learn it or do you have a legitimate use case for it?
The thing is that Kubernetes does simplify managing deployment of complex systems across nodes. Try managing something like a FoundationDB cluster natively across servers and then compare that to having managed it in Kubernetes with the operator.
The experience is night and day for the end user. Troubleshooting is easier for the system administrator.
The complexity your seeing is already distilled and there’s something to be said for having prior experience in the space to see the value it adds.
I am a developer and I use Kubernetes almost everyday, but just build tags and do some deployments, some service and ingress works. But we seldom use Job or CronJob, instead we have a job application. It is easy to use and with no so many configs like Kubernetes Job. Maybe Kubernetes Job is for some operation or complex task, and maybe I would use them in the future.
BTW, I prepare for CKAD for my career considerations. I like Kubernetes and I think it does simplify my works. But still, I hope it is easy to learn and use.