top | item 41400463

(no title)

paulglx | 1 year ago

Looks very interesting !

Is it not confusing to call k8s deployments "Containers", as they could be mixed up with Docker containers ?

discuss

order

umit-cakmak|1 year ago

Hi there, This is Umit, the maker of Agnost. I think you are right it can be confusing. By container we actually mean resources such as deployments, statefulsets, cronjobs. It is not related to containers in a pod.

from-nibly|1 year ago

I mean they are containers. They used to be docker containers, and I believe you can still choose to have them be docker containers.

antonyt|1 year ago

Parent is referring to Agnost's own concept of Containers, which are a different concept and further overloading the term. I agree with their take that this is confusing. Your Agnost Container is an abstraction over several K8S abstractions over actual containers. https://agnost.dev/guides/containers/

shawnz|1 year ago

Strictly speaking, k8s deployments describe a number of pods, and pods describe a number of containers. So creating a deployment in k8s could result in the creation of many containers as a result.