BCDevOps / OpenShift4-Migration

Scripts and info for Ministry teams migration from OpenShift 3.11 to 4.x
Apache License 2.0
3 stars 0 forks source link

Why can't my application on OCP4 talk to SSO on OCP3? #5

Closed jleach closed 2 years ago

jleach commented 3 years ago

TL;DR

The current Pathfinder cluster on OCP3.11 is considered an external system to the new OCP4 Silver cluster. As a result, Aporeto needs you to grant permission for your Pod(s) to talk to said external system

Talking to External System

Your newly minted namespace on OCP4 comes with the bare minimum Network Security Policy (NSP); it's just enough for very common tasks that every pod needs, like for example, talking to the Kubernetes API. Anything beyond this requires you to grant permission. You do this by wringing NSP. In this case, you need to do two things:

  1. Create an External Network exposing ports 80 and 443.
  2. Create NSP to let your Pod(s) talk to this External Network.

Here is a PR agains some existing NSP to do (1) and (2) above. In that example my API has a label role=api and I use that to help identify what is permitted to talk to the external network:

      source:
        - - '$namespace=${NAMESPACE}'
          - 'role=api'
      destination:
        - - 'ext:name=all-things-external'