oc-adm-migrate-storage man page
oc adm migrate storage — Update the stored version of API objects
oc adm migrate storage [Options]
Migrate internal object storage via update
This command invokes an update operation on every API object reachable by the caller. This forces the server to write to the underlying storage if the object representation has changed. Use this command to ensure that the most recent storage changes have been applied to all objects (storage version, storage encoding, any newer object defaults).
To operate on a subset of resources, use the --include flag. If you encounter errors during a run the command will output a list of resources that received errors, which you can then re-run the command on. You may also specify --from-key and --to-key to restrict the set of resource names to operate on (key is NAMESPACE/NAME for resources in namespaces or NAME for cluster scoped resources). --from-key is inclusive if specified, while --to-key is exclusive.
By default, events are not migrated since they expire within a very short period of time. If you have significantly increased the expiration time of events, run a migration with --include=events
WARNING: This is a slow command and will put significant load on an API server. It may also result in significant intra-cluster traffic.
Migrate objects in all namespaces. Defaults to true.
If true, all requested objects will be migrated. Defaults to false.
- -f, --filename=
Filename, directory, or URL to docker-compose.yml file to use
If specified, only migrate items with a key (namespace/name or name) greater than or equal to this value
Resource types to migrate. Passing --filename will override this flag.
When using the default or custom-column output format, don't print headers (default print headers).
- -o, --output=""
Output the modified objects instead of saving them, valid values are 'yaml' or 'json'
If specified, only migrate items with a key (namespace/name or name) less than this value
Options Inherited from Parent Commands
DEPRECATED: The API version to use when talking to the server
Username to impersonate for the operation
Path to the file container Azure container registry configuration information.
Path to a cert. file for the certificate authority
Path to a client certificate file for TLS
Path to a client key file for TLS
The name of the kubeconfig cluster to use
Path to the config file to use for CLI requests.
The name of the kubeconfig context to use
The Google Cloud Platform Service Account JSON Key to use for authentication.
If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
Maximum number of seconds between log flushes
Require server version to match client version
- -n, --namespace=""
If present, the namespace scope for this CLI request
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.
The address and port of the Kubernetes API server
Bearer token for authentication to the API server
The name of the kubeconfig user to use
# Perform a dry-run of updating all objects oc adm migrate storage # To actually perform the update, the confirm flag must be appended oc adm migrate storage --confirm # Only migrate pods oc adm migrate storage --include=pods --confirm # Only pods that are in namespaces starting with "bar" oc adm migrate storage --include=pods --confirm --from-key=bar/ --to-key=bar/\xFF
June 2016, Ported from the Kubernetes man-doc generator