kubevirt_vm_info – Describe VirtualMachines on Kubernetes
Note
This module is part of the kubevirt.core collection.
To install it, use: ansible-galaxy collection install kubevirt.core
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: kubevirt.core.kubevirt_vm_info
.
Synopsis
Use the Kubernetes Python client to perform read operations on KubeVirt VirtualMachines.
Pass options to find VirtualMachines as module arguments.
Authenticate using either a config file, certificates, password or token.
Supports check mode.
Requirements
The below requirements are needed on the host that executes this module.
python >= 3.6
kubernetes >= 12.0.0
Parameters
Parameter |
Comments |
---|---|
Token used to authenticate with the API. Can also be specified via K8S_AUTH_API_KEY environment variable. |
|
Use this to set the API version of KubeVirt. Default: |
|
Path to a CA certificate used to authenticate with the API. The full certificate chain must be provided to avoid certificate validation errors. Can also be specified via K8S_AUTH_SSL_CA_CERT environment variable. |
|
Path to a certificate used to authenticate with the API. Can also be specified via K8S_AUTH_CERT_FILE environment variable. |
|
Path to a key file used to authenticate with the API. Can also be specified via K8S_AUTH_KEY_FILE environment variable. |
|
The name of a context found in the config file. Can also be specified via K8S_AUTH_CONTEXT environment variable. |
|
List of field selectors to use to filter results Default: |
|
Provide a URL for accessing the API. Can also be specified via K8S_AUTH_HOST environment variable. |
|
Group(s) to impersonate for the operation. Can also be specified via K8S_AUTH_IMPERSONATE_GROUPS environment. Example: Group1,Group2 |
|
Username to impersonate for the operation. Can also be specified via K8S_AUTH_IMPERSONATE_USER environment. |
|
Path to an existing Kubernetes config file. If not provided, and no other connection options are provided, the Kubernetes client will attempt to load the default configuration file from ~/.kube/config. Can also be specified via K8S_AUTH_KUBECONFIG environment variable. Multiple Kubernetes config file can be provided using separator ‘;’ for Windows platform or ‘:’ for others platforms. The kubernetes configuration can be provided as dictionary. This feature requires a python kubernetes client version >= 17.17.0. Added in version 2.2.0. |
|
List of label selectors to use to filter results Default: |
|
Specify the name of the VirtualMachine. |
|
Specify the namespace of VirtualMachines. |
|
The comma separated list of hosts/domains/IP/CIDR that shouldn’t go through proxy. Can also be specified via K8S_AUTH_NO_PROXY environment variable. Please note that this module does not pick up typical proxy settings from the environment (e.g. NO_PROXY). This feature requires kubernetes>=19.15.0. When kubernetes library is less than 19.15.0, it fails even no_proxy set in correct. example value is “localhost,.local,.example.com,127.0.0.1,127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16” |
|
Provide a password for authenticating with the API. Can also be specified via K8S_AUTH_PASSWORD environment variable. Please read the description of the |
|
Whether or not to save the kube config refresh tokens. Can also be specified via K8S_AUTH_PERSIST_CONFIG environment variable. When the k8s context is using a user credentials with refresh tokens (like oidc or gke/gcloud auth), the token is refreshed by the k8s python client library but not saved by default. So the old refresh token can expire and the next auth might fail. Setting this flag to true will tell the k8s python client to save the new refresh token to the kube config file. Default to false. Please note that the current version of the k8s python client library does not support setting this flag to True yet. The fix for this k8s python library is here: https://github.com/kubernetes-client/python-base/pull/169 Choices:
|
|
The URL of an HTTP proxy to use for the connection. Can also be specified via K8S_AUTH_PROXY environment variable. Please note that this module does not pick up typical proxy settings from the environment (e.g. HTTP_PROXY). |
|
The Header used for the HTTP proxy. Documentation can be found here https://urllib3.readthedocs.io/en/latest/reference/urllib3.util.html?highlight=proxy_headers#urllib3.util.make_headers. |
|
Colon-separated username:password for basic authentication header. Can also be specified via K8S_AUTH_PROXY_HEADERS_BASIC_AUTH environment. |
|
Colon-separated username:password for proxy basic authentication header. Can also be specified via K8S_AUTH_PROXY_HEADERS_PROXY_BASIC_AUTH environment. |
|
String representing the user-agent you want, such as foo/1.0. Can also be specified via K8S_AUTH_PROXY_HEADERS_USER_AGENT environment. |
|
Provide a username for authenticating with the API. Can also be specified via K8S_AUTH_USERNAME environment variable. Please note that this only works with clusters configured to use HTTP Basic Auth. If your cluster has a different form of authentication (e.g. OAuth2 in OpenShift), this option will not work as expected and you should look into the community.okd.k8s_auth module, as that might do what you need. |
|
Whether or not to verify the API server’s SSL certificates. Can also be specified via K8S_AUTH_VERIFY_SSL environment variable. Choices:
|
|
Whether to wait for the VirtualMachine to end up in the ready state. Choices:
|
|
Number of seconds to sleep between checks. Ignored if Default: |
|
How long in seconds to wait for the resource to end up in the desired state. Ignored if Default: |
Notes
Note
To avoid SSL certificate validation errors when
validate_certs
is True, the full certificate chain for the API server must be provided viaca_cert
or in the kubeconfig file.
Examples
- name: Get an existing VirtualMachine
kubevirt.core.kubevirt_vm_info:
name: testvm
namespace: default
register: default_testvm
- name: Get a list of all VirtualMachines
kubevirt.core.kubevirt_vm_info:
namespace: default
register: vm_list
- name: Get a list of all VirtualMachines from any namespace
kubevirt.core.kubevirt_vm_info:
register: vm_list
- name: Search for all VirtualMachines labelled app=test
kubevirt.core.kubevirt_vm_info:
label_selectors:
- app=test
- name: Wait until the VirtualMachine is Ready
kubevirt.core.kubevirt_vm_info:
name: testvm
namespace: default
wait: yes
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Whether the specified api_version and VirtualMachine kind were successfully mapped to an existing API on the targeted cluster. Returned: always |
|
The VirtualMachine(s) that exists Returned: success |
|
The versioned schema of this representation of an object. Returned: success |
|
Represents the REST resource this object represents. Returned: success |
|
Standard object metadata. Includes name, namespace, annotations, labels, etc. Returned: success |
|
Specific attributes of the VirtualMachine. Can vary based on the api_version. Returned: success |
|
Current status details for the VirtualMachine. Returned: success |