Oc export: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * oc =Overview= Export objects in project in template form: <pre> oc export all --as-template=<template_name> </pre>") |
No edit summary |
||
| Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
Export objects in | Export objects into configuration files that can be used for backups or to create similar objects elsewhere in the cluster. Fields that cannot be specified on create, or which will be signed upon creation, will be emptied. The status part of objects is also cleared. | ||
Options: | |||
* The --exact flag configure export not to clear fields. | |||
* The --raw flag <font color=red>?</font> | |||
* The --as-template flag generates an API structure for a template to which parameters and object labels can be added. | |||
* "-o json|yaml" exports to JSON | |||
<pre> | <pre> | ||
oc export all --as-template=<template_name> | oc export all --as-template=<template_name> | ||
</pre> | </pre> | ||
Revision as of 00:13, 31 July 2017
Internal
Overview
Export objects into configuration files that can be used for backups or to create similar objects elsewhere in the cluster. Fields that cannot be specified on create, or which will be signed upon creation, will be emptied. The status part of objects is also cleared.
Options:
- The --exact flag configure export not to clear fields.
- The --raw flag ?
- The --as-template flag generates an API structure for a template to which parameters and object labels can be added.
- "-o json|yaml" exports to JSON
oc export all --as-template=<template_name>