Merge pull request #378 from ritza-co/docs-19.03.03

Docs 19.03.03 release (Week 42, 2024)

docs/auto-discovery/hypervisors-and-containers-supported-in-auto-discovery.md

@@ -3,16 +3,20 @@ title: "Supported Hypervisors and Containers List"
 sidebar_position: 30
 ---
 
-If you were looking for how-to instructions to get started with Hypervisor, Linux (\*nix), or Windows discovery, see either: 
+import ThemedImage from '@theme/ThemedImage'
+import useBaseUrl from '@docusaurus/useBaseUrl'
+
+Device42 autodiscovery supports various platforms, operating systems (OSes), and container platforms. The full list, including the details and limitations of the Docker, Cisco ASA/NX OS, and Nutanix autodiscovery processes, can be found below.
+
+If you are looking for instructions to get started with Hypervisor, Linux (\*nix), or Windows discovery, see either: 
 - the [Windows / Hyper-V Discovery](/auto-discovery/windows-and-hyper-v-auto-discovery.mdx) page 
 - or the [Linux / UNIX server auto-discovery](/auto-discovery/linux-unix-server-auto-discovery.mdx) page.
 
-## Supported Hypervisor / Container Platforms
-
-Device42 is constantly expanding its list of hypervisor and container platforms supported by autodiscovery. For instructions on how to configure and run these discovery jobs, please refer to [Hypervisor Autodiscovery](auto-discovery/virtual-machine-auto-discovery.md). The list of supported platforms currently includes:
+## Supported Hypervisor and Container Platforms
 
-![](/assets/images/D42-25011_supported-hyperv-platforms.png)
+Device42 is constantly expanding the hypervisor and container platforms supported by autodiscovery. 
 
+The list of supported platforms currently includes:
 
 - \*nix
 - AIX HMC
@@ -36,29 +40,39 @@ Device42 is constantly expanding its list of hypervisor and container platforms
 - Windows
 - WinRM
 
-**Note that both Windows and \*nix (Linux/UNIX) can be found in this drop-down as well; use those options to discover Windows servers, Linux servers, guest instances, or VMs themselves, as opposed to their hosts.**
+<ThemedImage
+  alt="Supported HyperV platforms"
+  sources={{
+    light: useBaseUrl('/assets/images/hypervisors-and-containers-supported-in-auto-discovery/platforms-list-light.png'),
+    dark: useBaseUrl('/assets/images/hypervisors-and-containers-supported-in-auto-discovery/platforms-list-dark.png'),
+  }}
+/>
+
+Both Windows and \*nix (Linux/UNIX) can be found in this dropdown menu as well. Use those options to discover Windows servers, Linux servers, guest instances, or VMs themselves, as opposed to their hosts.
+
+For instructions on how to configure and run these discovery jobs, please refer to [Hypervisor Autodiscovery](auto-discovery/virtual-machine-auto-discovery.md). 
 
 :::tip
 If you are using a hypervisor, a container platform, or an orchestration tool you would like to see supported - please let us know! Open a support ticket or email [[email protected]](mailto:[email protected]).
 :::
 
-### Notes on Docker / Docker API Autodiscovery
+### Docker and Docker API Autodiscovery Notes
 
 - Docker API discovery returns basic container data with IPs and MAC addresses.
 - Regular Docker discovery also returns service ports.
 - By running Docker and connecting to the host, you can map connections to the container.
-- You can see on the Docker host how to get the source ports of containers, without having to login to the container to identify the connection.
-- You can use the **docker top** command and supply just the container ID; you would need to use sudo commands for this.
-- We support all standard Docker cloud operating systems such as EKS (AWS Kubernetes), GKE (Google Kubernetes), AKS (Azure Kubernetes), and standalone Kubernetes, as well as Ubuntu, CentOS, Debian, Arch Linux and Fedora.
+- You can see on the Docker host how to get the source ports of containers, without having to log in to the container to identify the connection.
+- You can use the `docker top` command and supply just the container ID; you would need to use `sudo` commands for this.
+- We support all standard Docker cloud operating systems such as EKS (AWS Kubernetes), GKE (Google Kubernetes), AKS (Azure Kubernetes), and standalone Kubernetes, as well as Ubuntu, CentOS, Debian, Arch Linux, and Fedora.
 
-### Notes on Cisco ASA/NX OS Autodiscovery
+### Cisco ASA/NX OS Autodiscovery Notes
 
 Device42's Cisco ASA/NX OS autodiscovery augments firewall/ASA discoveries with information gathered via SSH. If you run virtual firewall instances, Device42 will discover your virtual firewalls and list them as firewall “contexts” underneath the parent firewall. Note that this discovery method has had only limited testing.
 
-### Notes on Nutanix Autodiscovery
+### Nutanix Autodiscovery Notes
 
-If you have previously ran a D42 discovery job, and are discovering new resources, then in some cases, you will need to delete and re-run to have a complete view. Note that this is a discovery workaround for the time being.
+If you have previously run a Device42 discovery job, and are discovering new resources, then in some cases, you will need to delete and re-run to have a complete view. Note that this is a discovery workaround for the time being.
 
-### Ignore IP/MAC Addresses From Autodiscovery
+### Ignore IP and MAC Addresses From Autodiscovery
 
 You have the option to ignore specific IP and MAC addresses globally and for specific jobs. See [Windows and Hyper-V Autodiscovery](/auto-discovery/windows-and-hyper-v-auto-discovery/#option-to-ignore-ipsmac-addresses.md) for more details.