For TKU August 2023 added support for the aging feature for the hosts discovered through the API provider. For more details, see (DRDC1-20380).
For TKU March 2023 added support for API discovery of Kubernetes clusters managed by Rancher. For details, see (DRDC1-17254) and Discovering Kubernetes clusters managed by Rancher.
For TKU December 2022 the following updates were introduced:
- API queries for Pods, Services Deployments and ReplicaSets are now split by namespaces. So each API call will return objects available for certain namespace. (DRDC1-19386)
- Load Balancer Service node key has been updated with namespace to make it more unique. (DRDC1-20121)
- IP Address node discovered via API Provider is now synced to CMDB. (DRDC1-20148)
For TKU October 2022 v1beta1 Ingresses API version is replaced with v1. From now on, only v1 will be used for Ingress discovery. Please note that v1 Ingress API is already available in Kubernetes v1.19+. For details see, (DRDC1-19580).
This topic introduces Kubernetes and information on how BMC Discovery determines information on the installation. For information on how to use BMC Discovery to discover your Kubernetes deployment, see Discovering containers.
Kubernetes is an open-source platform for automating deployment, scaling, and operations of application containers across clusters of hosts, providing container-centric infrastructure. Kubernetes can schedule and run application containers on clusters of physical or virtual machines. However, Kubernetes also allows developers to ‘cut the cord’ to physical and virtual machines, moving from a host-centric infrastructure to a container-centric one, providing the full advantages and benefits inherent to containers. Kubernetes provides the infrastructure to build a container-centric development environment.
Kubernetes cluster is a set of nodes: master node and worker node. Multi-master mode is needed for deploying the HA cluster.
The following paragraph describes K8s and OpenShift cluster nodes and their attributes.