Deployments can be used with a service tier for scaling horizontally or ensuring availability. Deployments: These building blocks can be used to create and manage a group of pods.Containers in a pod run on the same node and share resources such as filesystems, kernel namespaces, and an IP address. Pods: Kubernetes deploys and schedules containers in groups called pods.The following list provides some other common terms associated with Kubernetes: Kubelet: This component receives pod specifications from the API Server and manages pods running in the host.Scheduler: This component places the workload on the appropriate node – in this case all workloads will be placed locally on your host.Controller Manager: This component ensures that the clusters’ desired state matches the current state by scaling workloads up and down.It facilitates communication between the various components, thereby maintaining cluster health. API Server: This component is the management hub for the Kubernetes master node.etcd: This component stores configuration data which can be accessed by the Kubernetes master’s API Server by simple HTTP or JSON API.The master node places container workloads in user pods on worker nodes or itself. The architecture for Kubernetes, which relies on this experience, is shown below:Īs you can see from the figure above, there are a number of components associated with a Kubernetes cluster.
Overview of KubernetesĪccording to the Kubernetes website, “Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications.” Kubernetes was built by Google based on their experience running containers in production using an internal cluster management system called Borg (sometimes referred to as Omega). We’ll walk you through a high-level discussion of Kubernetes and Mesos with Marathon, look at their features, and cover their pros and cons.
In this updated blog post we’ll compare Kubernetes with the Mesos + Marathon container orchestration solution.
0 kommentar(er)
