Kubernetes Data Source
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.
Connection configuration
This data source establishes a connection to Kubernetes for extracting data. Due to authentication differences, the data source has to distinguish between Amazon Elastic Kubernetes Service (AWS EKS) and other Kubernetes instances.
For the connection it is necessary to provide the following parameters:
| Parameter | Description |
|---|---|
| Username | Your Kubernetes username |
| Password | Your Kubernetes password |
| Kubernetes Master URL | The endpoint URL of your Kubernetes cluster |
| CA Certificate | The CA certificate for secure connection (more information about the certificates can be found in the Kubernetes documentation) |
Importable types
The Kubernetes Importer has a fixed schema:
Asset types
| Asset-Type | Description |
|---|---|
| NODE | A 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. |
| NAMESPACE | Kubernetes supports multiple virtual clusters backed by the same physical cluster. These virtual clusters are called namespaces where the phase can be imported. |
| DEPLOYMENT | A Deployment object contains the desired state and information about Replicas. |
| REPLICA_SET / REPLICATION_CONTROLLER | ReplicaSet 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. |
| POD | Pods are the smallest deployable units of computing that can be created and managed in Kubernetes. |
| SERVICE | A 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. |
| ENDPOINT | Endpoint is an address (ip and port) that implements a Service. |
Link types
| Link-Type | Description |
|---|---|
| DEPLOYMENT_TO_REPLICA_SET | Links between deployments and replica sets will be established: which deployment is the owner of which replica set? |
| REPLICA_SET_TO_POD | Links between replica set and pods will be established: which pod is the owner of which replica set? |
| REPLICATION_CONTROLLER_TO_POD | Links between replication controller and pods will be established: which pod is the owner of which replication controller? |
| POD_TO_NODE | Links between pods and nodes will be established: which pod is connected to which node? |
| SERVICE_TO_ENDPOINT | Links between services and endpoints will be established: which service is reachable at which endpoint? |
| ENDPOINT_TO_POD | Links between endpoints and pods will be established: what is the endpoint of the pod? |