DescribeNodePoolVuls - Container Service for Kubernetes - Alibaba Cloud Documentation Center

This topic is generated by a machine translation engine without any human intervention. ALIBABA CLOUD DOES NOT GUARANTEE THE ACCURACY OF MACHINE TRANSLATED CONTENT. To request a human-translated version of this topic or provide feedback on this translation, please include it in the feedback form.

Queries the vulnerability information of a node pool, such as vulnerability names and severity levels, by specifying the ID of the node pool. We recommend that you periodically scan node pools for vulnerabilities to enhance cluster security.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
cs:DescribeNodePoolVuls	get	*Cluster `acs:cs:{#regionId}:{#accountId}:cluster/{#cluster_id}`	none	none

Request syntax

GET /clusters/{cluster_id}/nodepools/{nodepool_id}/vuls HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
cluster_id	string	Yes	Cluster ID.	c17e742cee942410486f237293d66****
nodepool_id	string	Yes	Node pool ID.	np38f32fdbc60e4a1e957ffde77846****
necessity	string	No	The priority to fix the vulnerability. Separate multiple priorities with commas (,). Valid values: `asap`: high `later`: medium `nntf`: low	asap

Response parameters

Parameter	Type	Description	Example
	object
vul_records	array<object>	The node pool vulnerabilities.
vul_records	object	The node vulnerabilities.
instance_id	string	The ID of the node.	i-t4n2qolb0wtzt0pz****
vul_list	array<object>	A list of vulnerabilities.
vul_list	object	Vulnerabilities
name	string	The name of the vulnerability.	oval:com.redhat.rhsa:def:20193197
alias_name	string	The alias of the vulnerability.	RHSA-2019:3197-Important: sudo security update
necessity	string	The severity level of the vulnerability. Valid values: nntf: You can ignore the vulnerability. later: You can fix the vulnerability later. asap: You need to fix the vulnerability at the earliest opportunity.	asap
cve_list	array	A list of CVE names corresponding to the vulnerabilities.
cve_list	string	The CVE name of the vulnerability.	CVE-2017-10268
need_reboot	boolean	Indicates whether a restart is required.	false
node_name	string	The node name. This name is the identifier of the node in the cluster.	cn-hangzhou.192.168.x.x
vuls_fix_service_purchased	boolean	Whether the Cloud Security CVE Remediation Service has been purchased	false

Examples

Sample success responses

JSONformat

{
  "vul_records": [
    {
      "instance_id": "i-t4n2qolb0wtzt0pz****",
      "vul_list": [
        {
          "name": "oval:com.redhat.rhsa:def:20193197",
          "alias_name": "RHSA-2019:3197-Important: sudo security update",
          "necessity": "asap",
          "cve_list": [
            "CVE-2017-10268"
          ],
          "need_reboot": false
        }
      ],
      "node_name": "cn-hangzhou.192.168.x.x"
    }
  ],
  "vuls_fix_service_purchased": false
}

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation
2024-06-19	The response structure of the API has changed	View Change Details