Skip to main content

Kubernetes

Kubernetes as a management tool for container orchestration gained a lot of traction recently. Txture provides direct access to a Kubernetes cluster and is capable of importing your assets directly. You need to provide the following informations:

Parameters
Username
Password
Kubernetes Master URL (Endpoint URL)
CA Certificate (more information about the certificates can be found in the kubernetes documentation: kubernetes.io)

The Kubernetes Importer has a fixed schema:

Asset-TypeDescription
NODEA node may be a virtual or physical machine, depending on the cluster. Each node contains the services necessary to run pods and is managed by the master components. It is possible to choose "only running", if you do, only the machines which are actually running at the given moment will be imported.
NAMESPACEKubernetes supports multiple virtual clusters backed by the same physical cluster. These virtual clusters are called namespaces where the phase can be imported.
DEPLOYMENTA Deployment object contains the desired state and information about Replicas.
REPLICA_SET / REPLICATION_CONTROLLERReplicaSet is the next-generation Replication Controller. The only difference between a REPLICA_SET and a REPLICATION_CONTROLLER right now is the selector support and the additional information "TemplateApp" and "TemplatePodHash" can be retrieved with the REPLICA_SET.
PODPods are the smallest deployable units of computing that can be created and managed in Kubernetes.
SERVICEA Kubernetes Service is an abstraction which defines a logical set of Pods and a policy by which to access them - sometimes called a micro-service.
ENDPOINTEndpoint is an address (ip and port) that implement a Service.
Link-TypeDescription
DEPLOYMENT_TO_REPLICA_SETLinks between deployments and replica sets will be established: which deployment is the owner of which replica set?
REPLICA_SET_TO_PODLinks between replica set and pods will be established: which pod is the owner of which replica set?
REPLICATION_CONTROLLER_TO_PODLinks between replication controller and pods will be established: which pod is the owner of which replication controller?
POD_TO_NODELinks between pods and nodes will be established: which pod is connected to which node?
SERVICE_TO_ENDPOINTLinks between services and endpoints will be established: which service is reachable at which endpoint?
ENDPOINT_TO_PODLinks between endpoints and pods will be established: what is the endpoint of the pod?