Container discovery identifies resources in Docker and Kubernetes environments. It discovers Docker containers and Kubernetes pods, services, and nodes.
Use this job type when you need visibility into container environments in addition to the underlying physical or virtual infrastructure.
Example: An infrastructure administrator creates a Container discovery job to identify Kubernetes nodes, the pods running in the environment, and the services associated with those workloads.
To create a new job for discovering Container devices, perform the following steps:
Click Workspace > ITAM > Asset > Discovery > Discovery Jobs.
The Discovery Jobs list page is displayed.Click New Job.
On New Job, select the job type that matches your discovery source.
Figure: New JobJob type
Purpose shown on the selection screen
Network
Discover Windows through WMI, Linux through SSH, and network devices through SNMP.
Cloud
Enumerate virtual machines and resources across AWS, Azure, GCP, and Oracle Cloud.
Container
Discover Docker containers and Kubernetes resources.
Hypervisor
Discover guest VMs through virtualization platforms.
Database
Connect to database engines to discover instances and inventory.
Directory
Discover Active Directory information without an agent.
Storage / SAN
Discover storage systems through supported platform interfaces.
Select Container on the new job.
On Identity, select the tenant and enter a descriptive job name.

Figure: IdentityField name
Description
Tenant *
Tenant context associated with the job. The demonstration displays Information Technology.
Job Name *
Name used to identify the job in the jobs list and run details. Example: Kubernetes-container.
Status
Activation state selected for the job. The demonstration shows Active.
Description (optional)
Purpose, scope notes, ownership, or other context for the team.
Next
Continues to the next wizard stage.
Cancel
Leaves the wizard. Confirm any save or discard behavior presented by the application.
Click Next to open Type and Credentials.
The Type & Credentials step lets you select Docker or Kubernetes container services and associate credentials with the respective container services you want to discover.
For each selected method, add a stored credential. Use quick creation if a suitable credential is not yet available.
Use the up and down controls to arrange the displayed execution order.
Review the methods and selected credentials, then click Next.

Figure: Container CredentialsField Name
Description
Docker
Select to discover Docker containers.
Kubernetes
Select to discover Kubernetes pods, services, and nodes.
Execution Order & Credentials
Displays the selected platforms in their configured execution order and the credentials assigned to each.
Selected credential
Displays a credential assigned to the platform. Click the × beside it to remove the assignment.
PRIMARY
Identifies the credential used first for the selected platform.
Add KUBERNETES credential
Select an existing Kubernetes credential to add to the job.
Quick-create KUBERNETES credential
Creates a Kubernetes credential and adds it to the current job.
Manage credentials
Opens credential management to review or maintain stored credentials.
Up / Down arrows
Moves the platform earlier or later in the execution order when multiple platforms are selected.
Remove platform (×)
Removes the platform from the job configuration.
Create Kubernetes Credential.
Enter the credential name, API Server URL, Bearer Token, CA Certificate, and CA Cert Path.
Click Create & Add.

Figure: Create Nutanix credentialField Name
Description
Credential Name *
Enter a descriptive name to identify the Kubernetes credential.
API Server URL
Enter the Kubernetes API server endpoint, including
https://and the port if required.Bearer Token*
Enter the authentication token used to access the Kubernetes API for discovery.
CA Certificate (PEM, recommended)
Paste the cluster’s Certificate Authority (CA) certificate in PEM format to verify the API server’s TLS certificate. Include the
BEGIN CERTIFICATEandEND CERTIFICATElines.CA Cert Path (advanced / legacy)
Enter the path to the CA certificate file accessible to the discovery engine.
Skip TLS verify
Select to skip verification of the API server’s TLS certificate. Leave cleared to verify the certificate.
Create and Add
Saves the credential and adds it to the current discovery job.
Cancel
Closes the dialog without creating the credential.
Credential Selection Guidance
Use AWS credentials with read access to the resources being discovered. Specify the AWS Region and provide the matching access key ID and secret access key. For temporary STS credentials, include the session token. Leave keys blank only if the discovery engine host has an instance profile.
Similarly, for Azure, GCP, or OCI you can create the credentials. Parameters may change depending on the Cloud Service Provider for which you are trying to create the credentials.
The Settings screen lets you control cloud discovery performance and diagnostic capture. Configure API concurrency to set the number of parallel API collectors and Job timeout to limit the overall execution duration.
You can also enable Coverage Score to assess collection completeness, Capture Engine Logs to support troubleshooting, and Capture Per-Host Results to retain detailed results for individual hosts. These options help balance discovery performance, visibility, and storage use.
Click Next to configure the discovery schedule.

Figure: Settings | API concurrency, job timeout, and logging
Field Name
Description
API concurrency
Sets the number of container API collectors that run in parallel for the discovery job. The displayed value is 10.
Job timeout (hours)
Sets the overall execution time limit for the discovery workflow. The screen specifies a minimum of 24 hours.
Coverage Score
Calculates a per-device score showing which parameters were collected and why others were not. Enable to assess discovery completeness.
Capture Engine Logs
Stores detailed discovery engine logs for each run to support troubleshooting. Enabling this option increases storage use.
Capture Per-Host Results
Stores detailed results for each host, allowing individual results to be investigated by IP address. Disable to reduce storage use.
Click Next.
Execution and Scheduling: The Schedule step lets you define when the discovery job starts, how often it repeats, and when the recurring schedule ends.
Select the effective task queue and if you want to schedule it, enable the Enable Schedule Runs toggle button.

Figure: Scheduling and ExecutionField Name
Description
Effective task queue
Displays the selected worker’s task queue used to execute scheduled runs and Run Now requests.
Enable scheduled runs
Enable to run the discovery job automatically according to the configured schedule.
Repeat Job
Select to repeat the discovery job at the specified interval.
Recurrence Type
Select how frequently the job repeats. The selection shown is Daily.
Recurs Every
Enter the interval between recurring runs. For example, 1 with Daily runs the job every day.
End Condition
Select when the recurring schedule ends. Select No end to continue recurring runs without an end date.
Start Date*
Specify the date and time when the schedule begins. The value is displayed in your time zone and stored in Coordinated Universal Time (UTC).
Previous
Return to the Settings step.
Cancel
Cancel the discovery job configuration.
Create Job
Create the discovery job using the configured scope, credentials, settings, and schedule.
Once you click Scan and Run Now, you will get a message mentioning Job started.

Figure: Job saved successfully