Secret
Secret holds secret data of a certain type. The total bytes of the values in the Data field must be less than MaxSecretSize bytes. Note: While Pulumi automatically encrypts the 'data' and 'stringData' fields, this encryption only applies to Pulumi's context, including the state file, the Service, the CLI, etc. Kubernetes does not encrypt Secret resources by default, and the contents are visible to users with access to the Secret in Kubernetes using tools like 'kubectl'. For more information on securing Kubernetes Secrets, see the following links: https://kubernetes.io/docs/concepts/configuration/secret/#security-properties https://kubernetes.io/docs/concepts/configuration/secret/#risks
Properties
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
Data contains the secret data. Each key must consist of alphanumeric characters, '-', '_' or '.'. The serialized form of the secret data is a base64 encoded string, representing the arbitrary (possibly non-string) data value here. Described in https://tools.ietf.org/html/rfc4648#section-4
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
stringData allows specifying non-binary secret data in string form. It is provided as a write-only input field for convenience. All keys and values are merged into the data field on write, overwriting any existing values. The stringData field is never output when reading from the API.