THREESCALE-10683 Bump Go, controller-runtime, and k8s dependencies

[carlkyrillos]

Issue Link

JIRA: THREESCALE-10683

NOTE: The e2e and unit tests will fail until this PR to openshift/release is merged - it bumps the version of Go that PROW uses to 1.20.

What

This PR bumps a number of dependencies, the notable ones being:

• go: 1.19 -> 1.20
• ginkgo: 1.16.5 -> 2.13.0
• client-go: 0.24.3 -> 0.28.3
• apimachinery: 0.24.3 -> 0.28.3
• controller-runtime: 0.12.2 -> 0.16.5

NOTE: This PR doesn't bump the version of operator-sdk, that will be done in a separate PR.

Verification Steps

Prerequisites

1. Go v1.20 - I recommend using the gvm CLI to quickly switch between Go versions
2. Provisioned OSD cluster

Cluster Scoped Scenario

1. Create the CatalogSource and install the operator (note: feel free to build your own images or use the ones provided)

make bundle-run quay.io/ckyrillo/3scale-operator-bundles:threescale-10683

2. Create a Namespace and s3-credentials Secret:

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

3. Create the APIManager CR (make sure to replace <REPLACE_WITH_CLUSTER_NAME> with the name of your cluster):

export CLUSTER_NAME=<REPLACE_WITH_CLUSTER_NAME>

export WILDCARD_DOMAIN=$(ocm get /api/clusters_mgmt/v1/clusters --parameter search="name is '$CLUSTER_NAME'" | jq -r '.items[].console.url' | cut -d'.' -f2-)

cat << EOF | oc create -f -
kind: APIManager
apiVersion: apps.3scale.net/v1alpha1
metadata:
  name: 3scale
  namespace: $NAMESPACE
spec:
  wildcardDomain: $WILDCARD_DOMAIN
  monitoring:
    enabled: true
  system:
    fileStorage:
      simpleStorageService:
        configurationSecretRef:
          name: s3-credentials
EOF

4. Verify the installation completes successfully:

oc get apimanager -n $NAMESPACE -o yaml -w

5. Delete the test namespace to prepare for the namespace scoped scenario

oc delete project $NAMESPACE

6. Uninstall the cluster scoped operator to prepare for the namespace scoped scenario

Namespace Scoped Scenario

1. Create a fresh Namespace and s3-credentials Secret:

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

2. Navigate to the OperatorHub in the OpenShift UI, search for 3scale, and install the dev version the 3scale-operator in the 3scale-test Namespace.

3. Create the APIManager CR:

cat << EOF | oc create -f -
kind: APIManager
apiVersion: apps.3scale.net/v1alpha1
metadata:
  name: 3scale
  namespace: $NAMESPACE
spec:
  wildcardDomain: $WILDCARD_DOMAIN
  monitoring:
    enabled: true
  system:
    fileStorage:
      simpleStorageService:
        configurationSecretRef:
          name: s3-credentials
EOF

4. Verify the installation completes successfully:

oc get apimanager -n $NAMESPACE -o yaml -w

[carlkyrillos]

/retest

[MStokluska]

Verified with target ns, cluster scoped and own ns installations. All looks good.
Given the code changes are pretty much same as the apicast operator one (already merged) and I see no issues with them
/lgtm
lets wait for e2e to pass before merging please

[MStokluska]

/retest