You should avoid exporting secrets without being more specific by using a label
selector or by name. This is because you will pick up special secrets related
to that project instance. Loading those special secrets into a new project may
break that project. Similar reason as to why have to be
Hi.
On 02/06/2018 13:18, Graham Dumpleton wrote:
For the basic Python application you wouldn't need to export most of
those and for some doing so would cause problems when you try to load
them again.
For a basic application with no secrets, configmaps or persistent
volumes, all you need is:
For the basic Python application you wouldn't need to export most of those and
for some doing so would cause problems when you try to load them again.
For a basic application with no secrets, configmaps or persistent volumes, all
you need is:
oc export is,bc,dc,svc,route -o yaml
Do not
I guess that means your admin user doesn’t have the cluster-admin role
On Sat, 2 Jun 2018 at 4:02 am, Brian Keyes wrote:
> I am attempting to follow these instructions
>
>
> https://docs.openshift.com/container-platform/3.7/day_two_guide/project_level_tasks.html
>
> I want to backup THE sample
I am attempting to follow these instructions
https://docs.openshift.com/container-platform/3.7/day_two_guide/project_level_tasks.html
I want to backup THE sample python app and I created a script like this (
from the documentation)
$ for object in rolebindings serviceaccounts secrets
