Telekube runs its own local Docker registry which is used as aĬluster-level cache for container images. This means that any node can go down without disrupting Telekube always configures Kubernetes to run in a highly available ("HA")Ĭonfiguration. Telekube to monitor Kubernetes' health and perform cluster updates. This includes the followingĪll Kubernetes services such as kubelet or kube-apiserver always runĮnclosed inside Telekube's own Gravity container. Greatly reducing the need for ongoing active management. However, Telekube pre-configures Kubernetes to be as reliable as possible The standard Kubernetes tools will work and Kubernetes rules will apply.
Kubernetes EnvironmentĮvery Telekube Cluster is a standalone instance of Kubernetes running multiple nodes, so Tasks such as watching logs, seeing stats for pods or volumes or managing configurations. You can also use familiar Kubernetes tools such as kubectl to perform regular cluster Each Telekube ClusterĪlso has a graphical, web-based UI to view and manage the Cluster. The Telekube interface that can be used to manage the Cluster.
Custom engineering kube 200 driver xp software#
Telekube uses software we call "Gravity" for managing Clusters. Telekube tooling such as the Teleport SSH server.The application and its services: workers, databases, caches, etc.
This means that every application running on a cluster ("Telekube Cluster" or "Cluster") consists This chapter covers Telekube Cluster administration.Įvery application packaged with Telekube ("Application Bundle") is a self-contained Kubernetes system.
0 kommentar(er)
