Re: Requirements for Router Re-encrypt destination certificates?

2018-06-02 Thread Jordan Liggitt
The only differences I see are in key usage restrictions The CA that is working in the second example has no key usage restrictions: X509v3 extensions: X509v3 Subject Key Identifier: C4:23:88:A9:1D:CB:82:24:53:E4:61:32:46:15:E0:93:CE:3F:C2:DA

Requirements for Router Re-encrypt destination certificates?

2018-06-02 Thread Marc Boorshtein
Something seems odd to be about setting up a route (origin 3.9), i can create a route with re-encrypt if the cert is signed by a self signed CA, but the route doesn't work if the destination certificate is self signed and marked as a CA. For example this destination certificate does NOT work with

Re: errors accessing egressnetworkpolicies.network.openshift.io when attempting to export project

2018-06-02 Thread Graham Dumpleton
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

Re: errors accessing egressnetworkpolicies.network.openshift.io when attempting to export project

2018-06-02 Thread Aleksandar Lazic
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: