Even though Kubernetes is an automation and orchestration framework, it involves collaboration among individuals at various stages including: Choosing a host cloud platform Choosing availability zones: Kubernetes is a distributed framework and the availability zones must be selected through collaboration among individuals Choosing an Application platform: Kubernetes could be run as a standalone, but users need to decide if an application platform such as Openshift should be used. OpenShift, with an embedded Kubernetes cluster manager, is an open source platform providing full application life-cycle management
Working software is a top priority with Kubernetes. Kubernetes is based on a decoupled, microservices based architecture so that no single point of failure disrupts the functionality of the software. Upgrades and updates can be made without any significant downtime. High availability and fault tolerance are built into a distributed Kubernetes cluster.
A user may set scheduling by using a scheduling policy involving predicates and priority functions. Scheduling could be used to filter out nodes using filtering policy predicates. A user may want to filter out nodes that do not meet certain requirements of a Pod. A user could use priority functions to rank nodes. Node affinity may be set using node labels and annotations to match Pods with nodes. A Pod is scheduled onto the node with the highest priority. A user may set resource usage. While a Kubernetes node capacity is fixed in terms of allocatable resources...
[
add
]
[
|
|
...
]