-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
2.14.0 GA, 2.15.0 GA, 2.13.2 GA
-
5
-
False
-
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
-
Current behavior:
The restoring guide doesn't mention that in order to restore the secrets and configmaps in another environment / project you must delete the following metadata:
- For secrets, you must delete .metadata.creationTimestamp, .metadata.namespace, .metadata.resourceVersion, .metadata.uid
- For configmaps, the same as above plus . metadata.ownerReferences.
If the metadata is not deleted, the configmap restoration fails silently.
These steps are not mentioned in the documentation and it creates confusion to customers.
Expected behavior:
Update the backup and restoring guide with the commands shown in this KCS for the configmaps and secrets which doesn't copy the metadata.
- is related to
-
THREESCALE-11496 DeploymentConfg and dc references in Operating Red Hat 3scale API Management
-
- Closed
-
-
THREESCALE-10851 Review backup and restore steps for zync-database
-
- To Document
-
- relates to
-
THREESCALE-11697 backend-redis restore procedure doesn't work
-
- To Document
-
-
THREESCALE-11702 system-redis restore procedure doesn't work
-
- To Document
-
- links to