OC(1)

NAME

oc volumes - DEPRECATED: set volume

SYNOPSIS

oc volumes [OPTIONS]

DESCRIPTION

DEPRECATED: This command has been moved to "oc set volume"

OPTIONS

--add=false
    If true, add volume and/or volume mounts for containers

--all=false
    If true, select all resources in the namespace of the specified resource types

--allow-missing-template-keys=true
    If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats.

--claim-class=""
    StorageClass to use for the persistent volume claim

--claim-mode="ReadWriteOnce"
    Set the access mode of the claim to be created. Valid values are ReadWriteOnce (rwo), ReadWriteMany (rwm), or ReadOnlyMany (rom)

--claim-name=""
    Persistent volume claim name. Must be provided for persistentVolumeClaim volume type

--claim-size=""
    If specified along with a persistent volume type, create a new claim with the given size in bytes. Accepts SI notation: 10, 10G, 10Gi

--configmap-name=""
    Name of the persisted config map. Must be provided for configmap volume type

--confirm=false
    If true, confirm that you really want to remove multiple volumes

-c, --containers="*"
    The names of containers in the selected pod templates to change - may use wildcards

--default-mode=""
    The default mode bits to create files with. Can be between 0000 and 0777. Defaults to 0644.

-f, --filename=[]
    Filename, directory, or URL to file to use to edit the resource.

--list=false
    If true, list volumes and volume mounts for containers

-m, --mount-path=""
    Mount path inside the container. Optional param for --add or --remove

--name=""
    Name of the volume. If empty, auto generated for add operation

--no-headers=false
    When using the default or custom-column output format, don't print headers.

-o, --output=""
    Output format. One of: json|yaml|wide|name|custom-columns=...|custom-columns-file=...|go-template=...|go-template-file=...|jsonpath=...|jsonpath-file=... See custom columns [ ⟨http://kubernetes.io/docs/user-guide/kubectl-overview/#custom-columns⟩], golang template [ ⟨http://golang.org/pkg/text/template/#pkg-overview⟩] and jsonpath template [ ⟨http://kubernetes.io/docs/user-guide/jsonpath⟩].

--output-version=""
    Output the formatted object with the given group version (for ex: 'extensions/v1beta1').

--overwrite=false
    If true, replace existing volume source and/or volume mount for the given resource

--path=""
    Host path. Must be provided for hostPath volume type

--remove=false
    If true, remove volume and/or volume mounts for containers

--secret-name=""
    Name of the persisted secret. Must be provided for secret volume type

-l, --selector=""
    Selector (label query) to filter on

-a, --show-all=true
    When printing, show all resources (false means hide terminated pods.)

--show-labels=false
    When printing, show all labels as the last column (default hide labels column)

--sort-by=""
    If non-empty, sort list types using this field specification. The field specification is expressed as a JSONPath expression (e.g. '{.metadata.name}'). The field in the API resource specified by this JSONPath expression must be an integer or a string.

--source=""
    Details of volume source as json string. This can be used if the required volume type is not supported by --type option. (e.g.: '{"gitRepo": {"repository": <git-url>, "revision": <commit-hash>}}')

--template=""
    Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [ ⟨http://golang.org/pkg/text/template/#pkg-overview⟩].

-t, --type=""
    Type of the volume source for add operation. Supported options: emptyDir, hostPath, secret, configmap, persistentVolumeClaim

OPTIONS INHERITED FROM PARENT COMMANDS

--api-version=""
    DEPRECATED: The API version to use when talking to the server

--as=""
    Username to impersonate for the operation

--azure-container-registry-config=""
    Path to the file container Azure container registry configuration information.

--certificate-authority=""
    Path to a cert. file for the certificate authority

--client-certificate=""
    Path to a client certificate file for TLS

--client-key=""
    Path to a client key file for TLS

--cluster=""
    The name of the kubeconfig cluster to use

--config=""
    Path to the config file to use for CLI requests.

--context=""
    The name of the kubeconfig context to use

--google-json-key=""
    The Google Cloud Platform Service Account JSON Key to use for authentication.

--insecure-skip-tls-verify=false
    If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure

--log-flush-frequency=0
    Maximum number of seconds between log flushes

--match-server-version=false
    Require server version to match client version

-n, --namespace=""
    If present, the namespace scope for this CLI request

--request-timeout="0"
    The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.

--server=""
    The address and port of the Kubernetes API server

--token=""
    Bearer token for authentication to the API server

--user=""
    The name of the kubeconfig user to use

EXAMPLE

      # List volumes defined on all deployment configs in the current project
      oc volume dc --all

      # Add a new empty dir volume to deployment config (dc) 'registry' mounted under
      # /var/lib/registry
      oc volume dc/registry --add --mount-path=/var/lib/registry

      # Use an existing persistent volume claim (pvc) to overwrite an existing volume 'v1'
      oc volume dc/registry --add --name=v1 -t pvc --claim-name=pvc1 --overwrite

      # Remove volume 'v1' from deployment config 'registry'
      oc volume dc/registry --remove --name=v1

      # Create a new persistent volume claim that overwrites an existing volume 'v1'
      oc volume dc/registry --add --name=v1 -t pvc --claim-size=1G --overwrite

      # Change the mount point for volume 'v1' to /data
      oc volume dc/registry --add --name=v1 -m /data --overwrite

      # Modify the deployment config by removing volume mount "v1" from container "c1"
      # (and by removing the volume "v1" if no other containers have volume mounts that reference it)
      oc volume dc/registry --remove --name=v1 --containers=c1

      # Add new volume based on a more complex volume source (Git repo, AWS EBS, GCE PD,
      # Ceph, Gluster, NFS, ISCSI, ...)
      oc volume dc/registry --add -m /repo --source=<json-string>

SEE ALSO

oc(1),

HISTORY

June 2016, Ported from the Kubernetes man-doc generator