Interface V1.EphemeralVolumeSourceOrBuilder

All Superinterfaces:
com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
All Known Implementing Classes:
V1.EphemeralVolumeSource, V1.EphemeralVolumeSource.Builder
Enclosing class:
V1

public static interface V1.EphemeralVolumeSourceOrBuilder extends com.google.protobuf.MessageOrBuilder
  • Method Summary

    Modifier and Type
    Method
    Description
    Will be used to create a stand-alone PVC to provision the volume.
    Will be used to create a stand-alone PVC to provision the volume.
    boolean
    Will be used to create a stand-alone PVC to provision the volume.

    Methods inherited from interface com.google.protobuf.MessageLiteOrBuilder

    isInitialized

    Methods inherited from interface com.google.protobuf.MessageOrBuilder

    findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
  • Method Details

    • hasVolumeClaimTemplate

      boolean hasVolumeClaimTemplate()
       Will be used to create a stand-alone PVC to provision the volume.
       The pod in which this EphemeralVolumeSource is embedded will be the
       owner of the PVC, i.e. the PVC will be deleted together with the
       pod.  The name of the PVC will be `<pod name>-<volume name>` where
       `<volume name>` is the name from the `PodSpec.Volumes` array
       entry. Pod validation will reject the pod if the concatenated name
       is not valid for a PVC (for example, too long).
       An existing PVC with that name that is not owned by the pod
       will *not* be used for the pod to avoid using an unrelated
       volume by mistake. Starting the pod is then blocked until
       the unrelated PVC is removed. If such a pre-created PVC is
       meant to be used by the pod, the PVC has to updated with an
       owner reference to the pod once the pod exists. Normally
       this should not be necessary, but it may be useful when
       manually reconstructing a broken cluster.
       This field is read-only and no changes will be made by Kubernetes
       to the PVC after it has been created.
       Required, must not be nil.
       
      optional .k8s.io.api.core.v1.PersistentVolumeClaimTemplate volumeClaimTemplate = 1;
    • getVolumeClaimTemplate

      V1.PersistentVolumeClaimTemplate getVolumeClaimTemplate()
       Will be used to create a stand-alone PVC to provision the volume.
       The pod in which this EphemeralVolumeSource is embedded will be the
       owner of the PVC, i.e. the PVC will be deleted together with the
       pod.  The name of the PVC will be `<pod name>-<volume name>` where
       `<volume name>` is the name from the `PodSpec.Volumes` array
       entry. Pod validation will reject the pod if the concatenated name
       is not valid for a PVC (for example, too long).
       An existing PVC with that name that is not owned by the pod
       will *not* be used for the pod to avoid using an unrelated
       volume by mistake. Starting the pod is then blocked until
       the unrelated PVC is removed. If such a pre-created PVC is
       meant to be used by the pod, the PVC has to updated with an
       owner reference to the pod once the pod exists. Normally
       this should not be necessary, but it may be useful when
       manually reconstructing a broken cluster.
       This field is read-only and no changes will be made by Kubernetes
       to the PVC after it has been created.
       Required, must not be nil.
       
      optional .k8s.io.api.core.v1.PersistentVolumeClaimTemplate volumeClaimTemplate = 1;
    • getVolumeClaimTemplateOrBuilder

      V1.PersistentVolumeClaimTemplateOrBuilder getVolumeClaimTemplateOrBuilder()
       Will be used to create a stand-alone PVC to provision the volume.
       The pod in which this EphemeralVolumeSource is embedded will be the
       owner of the PVC, i.e. the PVC will be deleted together with the
       pod.  The name of the PVC will be `<pod name>-<volume name>` where
       `<volume name>` is the name from the `PodSpec.Volumes` array
       entry. Pod validation will reject the pod if the concatenated name
       is not valid for a PVC (for example, too long).
       An existing PVC with that name that is not owned by the pod
       will *not* be used for the pod to avoid using an unrelated
       volume by mistake. Starting the pod is then blocked until
       the unrelated PVC is removed. If such a pre-created PVC is
       meant to be used by the pod, the PVC has to updated with an
       owner reference to the pod once the pod exists. Normally
       this should not be necessary, but it may be useful when
       manually reconstructing a broken cluster.
       This field is read-only and no changes will be made by Kubernetes
       to the PVC after it has been created.
       Required, must not be nil.
       
      optional .k8s.io.api.core.v1.PersistentVolumeClaimTemplate volumeClaimTemplate = 1;