This field is required.

This field must consist of lower case alphanumeric characters, '-' or '.', and contain at most 63 characters, and must start and end with an alphanumeric character.

A configuration with the same name already exists inside the selected namespace.

Namespace
This namespace has exhausted its resource capacity and you will not be able to deploy the configuration. Contact your administrator to expand the capacity of the namespace.
You do not have access to any namespace. Contact your administrator to get access to a namespace.
Configuration kind
Select the kind of data that you want to save in the configuration.
Information
More information about types of secret can be found in the official kubernetes documentation.
You should only create a service account token Secret object if you can't use the TokenRequest API to obtain a token, and the security exposure of persisting a non-expiring token credential in a readable API object is acceptable to you.
See service account token secrets in the kubernetes documentation.
Ensure the Secret data field contains a .dockercfg key whose value is content of a legacy ~/.dockercfg file.
Ensure the Secret data field contains a .dockerconfigjson key whose value is content of a ~/.docker/config.json file.
Ensure the Secret data field contains a tls.key key and a tls.crt key.
Ensure the Secret data field contains a token-id key and a token-secret key. See bootstrap token secrets in the kubernetes documentation for optional keys.

This field is required.

This field must consist of lower case alphanumeric characters, '-' or '.', and contain at most 63 characters, and must start and end with an alphanumeric character.

This field is required.

{{ ctrl.state.secretWarningMessage }}
Actions