Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Kubectl get, edit, delete and describe work roughly the same way on every object type. If that's a service, pod, deployment, or cronjob, once you know the verbs you can interact with all of them.

Every object has a kind, metadata, and spec.

If that doesn't lead to some intuition on how to use it...



The complexity is in what is a service, pod, job, etc. not in the CRUD model. It's like describing driving a car as "the accelerator, brake, and clutch are all pedals; you press them to activate their functionality; pretty intuitive"


I would think a vehicle is a better analogy.

This car has tires, you create, delete and patch them. It also has an axels, gas tank, etc.

This truck has tires, axels, has tank

This motorcycle has tires, axels, etc


when the user simply wants to get from point A to point B - you give them API to deal with axles, pedals, tires, transmission, etc...

sounds like kubernetes?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: