THREESCALE-11346 Backport support for Backend CRs using wss protocol

[carlkyrillos]

Issue Link

JIRA: THREESCALE-11346

What

This PR backports #994 to the 3scale-2.14-stable branch for the 2.14.3 release.

This PR allows users to create a Backend CR that uses the WSS protocol for the privateBaseURL. This was already allowed for Backends created through the 3scale portal.

Verification Steps

1. Checkout this PR

2. Run the operator locally or via OLM using prebuilt image

BUNDLE_IMG=quay.io/ckyrillo/3scale-operator-bundles:threescale-11346 make bundle-run

3. Create a Namespace, dummy s3 Secret, and APIManager CR:

export NAMESPACE=3scale-test
oc new-project $NAMESPACE
cat << EOF | oc create -f -
kind: Secret
apiVersion: v1
metadata:
  name: s3-credentials
  namespace: $NAMESPACE
data:
  AWS_ACCESS_KEY_ID: c29tZXRoaW5nCg==
  AWS_BUCKET: c29tZXRoaW5nCg==
  AWS_REGION: dXMtd2VzdC0xCg==
  AWS_SECRET_ACCESS_KEY: c29tZXRoaW5nCg==
type: Opaque
EOF

DOMAIN=$(oc get routes console -n openshift-console -o json | jq -r '.status.ingress[0].routerCanonicalHostname' | sed 's/router-default.//')
cat << EOF | oc create -f -
kind: APIManager
apiVersion: apps.3scale.net/v1alpha1
metadata:
  name: 3scale
  namespace: $NAMESPACE
spec:
  wildcardDomain: $DOMAIN
  system:
    fileStorage:
      simpleStorageService:
        configurationSecretRef:
          name: s3-credentials
EOF

4. Wait for the install to complete:

oc get apimanager 3scale -n 3scale-test -oyaml -w

5. Create a Backend CR with a privateBaseURL that uses WSS:

cat << EOF | oc create -f -
kind: Backend
apiVersion: capabilities.3scale.net/v1beta1
metadata:
  name: wss-backend
  namespace: $NAMESPACE
spec:
  name: WSS Backend
  privateBaseURL: 'wss://api.examplewss.com'
  systemName: wssbackend
EOF

6. Verify that the Backend CR is ready

oc get backend wss-backend -n 3scale-test -oyaml | yq e '.status.conditions[] | select(.type == "Synced")' 

7. Login to the admin portal and confirm the WSS Backend exists

[austincunningham]

@carlkyrillos do we need to verify this again. I would say its verified and on master and if the e2e pass we are good. WDYT?

[carlkyrillos]

@carlkyrillos do we need to verify this again. I would say its verified and on master and if the e2e pass we are good. WDYT?

@austincunningham I verified it myself yesterday and it was already verified on master like you said so I think it's fine to merge

[austincunningham]

/lgtm

[austincunningham]

/approve