Kubernetes resource model

• Config maps: holds configuration data for pods to consume
• Daemon sets: ensures that each node in the cluster runs this pod
• Deployments: defines a desired state of a deployment object
• Events: provides life cycle events on pods and other deployment objects
• Endpoints: allows an inbound connections to reach the cluster services
• Ingress: a collection of rules that allows inbound connections to reach the cluster services
• Jobs: creates one or more pods and when they complete successfully, the job is marked as completed
• Node: a worker machine in Kubernetes
• Namespaces: multiple virtual clusters backed by the same physical cluster
• Pods: the smallest deployable units of computing that can be created and managed in Kubernetes
• Persistent volumes: provides an API for users and administrators to abstract details about how storage is provided from how it is consumed
• Replica sets: ensures that a specified number of pod replicas are running at any given time
• Secrets: holds sensitive information, such as passwords, OAuth tokens, and SSH keys
• Service accounts: provides an identity for processes that run in a pod
• Services: an abstraction that defines a logical set of pods and a policy by which to access them, sometimes called a microservice
• Stateful sets: the workload API object that manages stateful applications