Rediscovery occurs when you rerun the same discoveries to update, delete, and import new cloud resources based on discovery tasks you ran before. This is useful when technical or security restrictions prevent you from running visibilty tasks on your cloud infrastructure.
For more details on setting up your system to support rediscovery, see Rediscovery of cloud resources.
Only certain actions are tracked by GCP rediscovery. These actions are as follows:
- VPC/Subnets
- Creating a new VPC/Subnet
- Updating a CIDR of a VPC/Subnet
- Deleting a VPC/Subnet
- Virtual Machines
- Creating a new virtual machine
- Updating a virtual machine state
- Deleting a virtual machine
- Load balancers
- Creating a new load balancer
- Deleting a load balancer
- DNS Records
- Creating a new zone
- Creating a new record
- Deleting a zone
- Deleting a record
- Private Endpoint:
- Creating a new Private Endpoint
- Deleting an existing Private Endpoint
- Kubernetes Engine
- Creating a Kubernetes cluster
- Creating a node pool
- Updating a node pool (resizing)
- Deleting a node pool
- Deleting a Kubernetes cluster
Attention:
- Selective Deployment of changes is not supported for rediscovery.
- If the name or value of a Cloud DNS record changes, the record is deleted and reimported into Address Manager as a new record upon rediscovery.