Argo Workflows · JSON Structure

Argo Workflows Io K8S Api Core V1 Secret Projection Structure

Adapts a secret into a projected volume. The contents of the target Secret's Data field will be presented in a projected volume as files using the keys in the Data field as the file names. Note that this is identical to a secret volume source without the default mode.

Type: object Properties: 3
CNCFContainersData ProcessingKubernetesMachine LearningOpen SourceWorkflow Engine

io.k8s.api.core.v1.SecretProjection is a JSON Structure definition published by Argo Workflows, describing 3 properties. It conforms to the https://json-structure.org/meta/core/v0/# meta-schema.

Properties

items name optional

Meta-schema: https://json-structure.org/meta/core/v0/#

JSON Structure

Raw ↑ 
{
  "$schema": "https://json-structure.org/meta/core/v0/#",
  "$id": "https://raw.githubusercontent.com/api-evangelist/argo-workflows/refs/heads/main/json-structure/argo-workflows-io-k8s-api-core-v1-secret-projection-structure.json",
  "name": "io.k8s.api.core.v1.SecretProjection",
  "description": "Adapts a secret into a projected volume.\n\nThe contents of the target Secret's Data field will be presented in a projected volume as files using the keys in the Data field as the file names. Note that this is identical to a secret volume source without the default mode.",
  "type": "object",
  "properties": {
    "items": {
      "description": "items if unspecified, each key-value pair in the Data field of the referenced Secret will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the Secret, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'.",
      "type": "array",
      "items": {
        "$ref": "#/definitions/io.k8s.api.core.v1.KeyToPath"
      },
      "x-kubernetes-list-type": "atomic"
    },
    "name": {
      "description": "Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names",
      "type": "string"
    },
    "optional": {
      "description": "optional field specify whether the Secret or its key must be defined",
      "type": "boolean"
    }
  }
}