INPUT_OBJECT

KubernetesKindDeploymentSpecTemplateSpecEphemeralContainersInput

An EphemeralContainer is a container that may be added temporarily to an existing pod for user-initiated activities such as debugging. Ephemeral containers have no resource or scheduling guarantees, and they will not be restarted when they exit or when a pod is removed or restarted. If an ephemeral container causes a pod to exceed its resource allocation, the pod may be evicted. Ephemeral containers may not be added by directly updating the pod spec. They must be added via the pod's ephemeralcontainers subresource, and they will appear in the pod spec once added. This is an alpha feature enabled by the EphemeralContainers feature flag.

link GraphQL Schema definition

  • input KubernetesKindDeploymentSpecTemplateSpecEphemeralContainersInput {
  • args: [String]
  • command: [String]
  • # EnvVar represents an environment variable present in a Container.
  • env: [KubernetesKindDeploymentSpecTemplateSpecEphemeralContainersEnvInput]
  • # EnvFromSource represents the source of a set of ConfigMaps
  • envFrom: [KubernetesKindDeploymentSpecTemplateSpecEphemeralContainersEnvFromInput]
  • # Docker image name. More info:
  • # https://kubernetes.io/docs/concepts/containers/images
  • image: String
  • # Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if
  • # :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More
  • # info: https://kubernetes.io/docs/concepts/containers/images#updating-images
  • imagePullPolicy: String
  • # Lifecycle is not allowed for ephemeral containers.
  • lifecycle: KubernetesKindDeploymentSpecTemplateSpecEphemeralContainersLifecycleInput
  • # Probes are not allowed for ephemeral containers.
  • livenessProbe: KubernetesKindDeploymentSpecTemplateSpecEphemeralContainersLivenessProbeInput
  • # Name of the ephemeral container specified as a DNS_LABEL. This name must be
  • # unique among all containers, init containers and ephemeral containers.
  • name: String
  • # ContainerPort represents a network port in a single container.
  • ports: [KubernetesKindDeploymentSpecTemplateSpecEphemeralContainersPortsInput]
  • # Probes are not allowed for ephemeral containers.
  • readinessProbe: KubernetesKindDeploymentSpecTemplateSpecEphemeralContainersReadinessProbeInput
  • # Resources are not allowed for ephemeral containers. Ephemeral containers use
  • # spare resources already allocated to the pod.
  • resources: KubernetesKindDeploymentSpecTemplateSpecEphemeralContainersResourcesInput
  • # SecurityContext is not allowed for ephemeral containers.
  • securityContext: KubernetesKindDeploymentSpecTemplateSpecEphemeralContainersSecurityContextInput
  • # Probes are not allowed for ephemeral containers.
  • startupProbe: KubernetesKindDeploymentSpecTemplateSpecEphemeralContainersStartupProbeInput
  • # Whether this container should allocate a buffer for stdin in the container
  • # runtime. If this is not set, reads from stdin in the container will always
  • # result in EOF. Default is false.
  • stdin: Boolean
  • # Whether the container runtime should close the stdin channel after it has been
  • # opened by a single attach. When stdin is true the stdin stream will remain open
  • # across multiple attach sessions. If stdinOnce is set to true, stdin is opened on
  • # container start, is empty until the first client attaches to stdin, and then
  • # remains open and accepts data until the client disconnects, at which time stdin
  • # is closed and remains closed until the container is restarted. If this flag is
  • # false, a container processes that reads from stdin will never receive an EOF.
  • # Default is false
  • stdinOnce: Boolean
  • # If set, the name of the container from PodSpec that this ephemeral container
  • # targets. The ephemeral container will be run in the namespaces (IPC, PID, etc)
  • # of this container. If not set then the ephemeral container is run in whatever
  • # namespaces are shared for the pod. Note that the container runtime must support
  • # this feature.
  • targetContainerName: String
  • # Optional: Path at which the file to which the container's termination message
  • # will be written is mounted into the container's filesystem. Message written is
  • # intended to be brief final status, such as an assertion failure message. Will be
  • # truncated by the node if greater than 4096 bytes. The total message length
  • # across all containers will be limited to 12kb. Defaults to /dev/termination-log.
  • # Cannot be updated.
  • terminationMessagePath: String
  • # Indicate how the termination message should be populated. File will use the
  • # contents of terminationMessagePath to populate the container status message on
  • # both success and failure. FallbackToLogsOnError will use the last chunk of
  • # container log output if the termination message file is empty and the container
  • # exited with an error. The log output is limited to 2048 bytes or 80 lines,
  • # whichever is smaller. Defaults to File. Cannot be updated.
  • terminationMessagePolicy: String
  • # Whether this container should allocate a TTY for itself, also requires 'stdin'
  • # to be true. Default is false.
  • tty: Boolean
  • # volumeDevice describes a mapping of a raw block device within a container.
  • volumeDevices: [KubernetesKindDeploymentSpecTemplateSpecEphemeralContainersVolumeDevicesInput]
  • # VolumeMount describes a mounting of a Volume within a container.
  • volumeMounts: [KubernetesKindDeploymentSpecTemplateSpecEphemeralContainersVolumeMountsInput]
  • # Container's working directory. If not specified, the container runtime's default
  • # will be used, which might be configured in the container image. Cannot be
  • # updated.
  • workingDir: String
  • }

link Require by