Debug School

Ankit Aggarwal
Ankit Aggarwal

Posted on

List of resources in K8s

  1. Namespaces: Namespace is something like an isolated environment in cluster keep resource within it like PODs, PVC and few others. By default we have default namespace created kubectl get ns
  2. POD: Pod is atomic unit of k8s where we run one or more container which actually runs application within it kubectl get pod -n=yournamespace
  3. ReplicationController: this resource will help us create replica of a POD. kubectl get rs

  4. Deployments: This will help us to deploy pod with more features replication+controller+versioning+rollingoutupdate + rollback.

    kubectl get deploy -n=namespace

  5. PV: it is referred as persistent volume in K8S which is usually created by admin. It is a permanent volume which is not deleted even if pod is deleted

  6. PVC: it is referred as persistent volumne claim which can be claimed by user or admin and then attached to pod. It is for claiming persistent volume available

  7. Secrets: It is a kind of volume in etcd within cluster storage to store meta or config or data or file in encoded form. It will be in key value pair format

  8. ConfigMap: It is kind of volume in etcd which stores information which is available to all the Nodes. It will be in key value form format. It can also be used for storing environment variables

  9. Service account: These are the sa for process runs in PODs

  10. Daemonsets:It also creates a pod. It is mainly for stateless application like application which never changes like apache. It is mainly used by admin where one pod each worker kind of requirement is there. like prometheous or monitoring or logging etc

  11. Stateful sets: As the name suggests it is for creating PODS in stateful manner. It also create pods sequentially like Pod1, Pod2, Pod2 1 by 1.

  12. role: It is there for authorization purpose so that role based access can be given to user.

  13. rolebindings: It will do user, role and namespace binding for authorization of user.

  14. Clusterroles: It is a cluster level roles created

  15. Clusterrolesbinding: It will binding users to cluster level roles so that user will have cluster level access to resources

  16. jobs: These are process which runs at one for specific purpose

  17. cronjobs: These are process which runs recurrently or repeatedly

  18. services: There are like a internal load balancers for pods so that if requests can be redirected to pods randomly

Top comments (0)