In June TKU 2025:
- Changed Software Container type to unified "Linux Container", Software Container id attribute changed to container_id, improved Container Image name attribute assignment, changed Software Container key attribute. (DRDC1-26135)
- Now modeling Software Pods only in running and pending phases. (DRDC1-26135)
- Reduced number of modelled Jobs: Jobs belonging to one Namespace, having the same name but different number-like suffix will be modelled as one single node. (DRDC1-26264) e.g. builder-cronjob-1738458000 ==> builder-cronjob
- Reduced number of modelled Load Balancer Services/Pools/Members for K8s Service. Now we model 1 Load Balancer Service per K8s Service.
- K8s Load Balancer Service, representing Services, won't have port attribute, but list of ports. (DRDC1-25258)
- Added support for LoadBalancer and NodePort K8s Services types. (DRDC1-25258)
- Ingress Controller (Load Balancer Instance) node for Ingress Controller will be deprecated. Added nginx_controller_version attribute to nginx controller Deployment node instead. (DRDC1-25258)
- Improved Ingress and OpenShift Routes modelling. (DRDC1-25258)
In April TKU 2025, added new versioning methods and removed "kubectl api-resources" command, for IP discovery method. (DRDC1-24415)
In March TKU 2025, we stopped modelling terminated Software Containers. Only running containers will be modelled. container_state and reason attributes were also removed from Software Container nodes. (DRDC1-25156)
In March TKU 2025, Worker/Master Software Instance node key was changed to be unified for IP and API discovery methods. (DRDC1-25231)
In February TKU 2025, added a new ContainerImage node kind. It will replace Image Detail node for Software Container. (DRDC1-23249)
In February TKU 2025, removed relationships between Load Balancer Service node and Cluster and between Load Balancer Pool and Host. Key attribute for Load Balancer Member node has been changed. (DRDC1-25078)
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.