For TKU October 2020 Kubernetes Functions pattern has been updated:
This topic provides an introduction to Kubernetes and information on the way that BMC Discovery determines information on the installation. For information on how to use BMC Discovery to discover your Kubernetes deployment, see Discovering containers.
Please login or sign up. You may also need to provide your support ID if you have not already done so. 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 infrastructure, which provides the full advantages and benefits inherent to containers. Kubernetes provides the infrastructure to build a container-centric development environment. Currently we focus on "bare metal" deployment. Please login or sign up. You may also need to provide your support ID if you have not already done so.
Product Description
Architecture
6 Comments
Martijn Krop
The picture mentioned under "main diagram" is missing or has a bad link.
Philippe Boyer
I can see the picture now (10/2020)
Marcell Alzate
as for Oct 15th, 2020.. the "main diagram" is missing or has a bad link... still the same
Anastasiia Mikhieieva
Hi Marcell Alzate, please try to preview the diagram again. Thank you!
Marcell Alzate
working now, thanks!!!
Rene Forstner
is it only me who is not able to get those insights when running Kubernetes as EKS Service?
With the EKS pattern I'm able to gather some information related to the Kubernetes Cluster, but as, with EKS, I'm not able to scan the master node, i see almost no information when scanning the worker nodes.
I'd like to archive to build a service model based on Namespace, Service and Deployment and this is exactly the information which is missing from both sides (EKS on one side and only scanning the Kubernetes worker nodes on the other side)
kind regards
René