kubernetes_param

Configuration for Kubernetes params used in triton config resource.

(click to see Operations)

Properties

(click to see Operations)

Name	Data Type	Permissions	Description
client_key	<String>	Read-write	Path to the Client key for client certificate based authentication.
parent_name	<String>	Read-write	.
ca_data	<String>	Read-write	CA certificate data (plain or 64base encoded).
ca	<String>	Read-write	Path to the CA certificate.
parent_id	<String>	Read-write	.
username	<String>	Read-write	User to be used for basic authentication.
client_cert_data	<String>	Read-write	Client certificate data for client certificate based authentication (plain or 64base encoded) .
password	<String>	Read-write	User's Password for basic authentication.
insecure_skip_verify	<Boolean>	Read-write	Whether to skip verifying server certificate.
client_cert	<String>	Read-write	Path to the Client certificate for client certificate based authentication.
token	<String>	Read-write	Token for bearer tokens based authentication.
kubeconfig	<String>	Read-write	Path to the kubeconfig file to be used for kubernetes configuration.
apiserver	<String>	Read-write	URL to be used to connect to API server.
client_key_data	<String>	Read-write	Client key data for client certificate based authentication (plain or 64base encoded).

Operations

(click to see Properties)

Some options that you can use for each operations:

• Getting warnings in response:NITRO allows you to get warnings in an operation by specifying the "warning" query parameter as "yes". For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:

  http://<netscaler-ip-address>/nitro/v1/config/login?warning=yes

  If any, the warnings are displayed in the response payload with the HTTP code "209 X-NITRO-WARNING".

• Authenticated access for individual NITRO operations:NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,

  To do this, you must specify the username and password in the request header of the NITRO request as follows:

  X-NITRO-USER:<username>

  X-NITRO-PASS:<password>

  Note: In such cases, make sure that the request header DOES not include the following:

  Cookie:NITRO_AUTH_TOKEN=<tokenvalue>

Note:

Mandatory parameters are marked in red and placeholder content is marked in <green>.