Skip to content


Configuration for Kubernetes params used in triton config resource.

(click to see Operations)


(click to see Operations)

NameData TypePermissionsDescription
client_key<String>Read-writePath to the Client key for client certificate based authentication.
ca_data<String>Read-writeCA certificate data (plain or 64base encoded).
ca<String>Read-writePath to the CA certificate.
username<String>Read-writeUser to be used for basic authentication.
client_cert_data<String>Read-writeClient certificate data for client certificate based authentication (plain or 64base encoded) .
password<String>Read-writeUser's Password for basic authentication.
insecure_skip_verify<Boolean>Read-writeWhether to skip verifying server certificate.
client_cert<String>Read-writePath to the Client certificate for client certificate based authentication.
token<String>Read-writeToken for bearer tokens based authentication.
kubeconfig<String>Read-writePath to the kubeconfig file to be used for kubernetes configuration.
apiserver<String>Read-writeURL to be used to connect to API server.
client_key_data<String>Read-writeClient key data for client certificate based authentication (plain or 64base encoded).


(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:


    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:



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



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