Please enable JavaScript.
Coggle requires JavaScript to display documents.
Kubernetes (object model (object types (pods (scheduled together on the…
Kubernetes
object model
-
-
-
-
object types
-
controllers
-
replicaControllers
-
can be used independently, but they are mostly used by Deployments to orchestrate the Pod creation, deletion, and updates
used with Pods to handle a Pod's replication, fault tolerance, self-heal, etc
services
-
-
-
service type
-
-
-
externalName
a special ServiceType, that has no Selectors and does not define any endpoints
-
The primary use case of this ServiceType is to make externally configured services like my-database.example.com available inside the cluster, using just the name, like my-database, to other services inside the same Namespace
loadbalancer
NodePort and ClusterIP Services are automatically created, and the external load balancer will route to them
-
-
logically groups Pods and a policy to access them. This grouping is achieved via Labels and Selectors
volumes
volume types
hostPath
If the Pod dies, the content of the Volume is still available on the host
emptyDir
An empty Volume is created for the Pod as soon as it is scheduled on the Worker Node. The Volume's life is tightly coupled with the Pod. If the Pod dies, the content of emptyDir is deleted forever
-
-
-
-
secret
can pass sensitive information, such as passwords, to Pods
-
persistent volumes
a network attached storage in the cluster, which is provisioned by the administrator
-
-
-
ingress
-
-
-
-
-
Ingress controller
watches the Master Node's API Server for changes in the Ingress resources and updates the Layer 7 load balancer accordingly
-
namespaces
-
default
a special namespace, which is readable by all users and used for special purposes, like bootstrapping a cluster
-
-
-