THREESCALE-12178 - Add SECRET_KEY_BASES to zync init containers

[tkan145]

What

Fix THREESCALE-12178

Verification steps

• Checkout this branch
• Prepare namespace

make cluster/prepare/local

• Setup APIM with image from alpha branch

export NAMESPACE=3scale-test

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:
  externalComponents:
    backend:
      redis: true
    system:
      database: true
      redis: true
  resourceRequirementsEnabled: true
  system:
    fileStorage:
      simpleStorageService:
        configurationSecretRef:
          name: s3-credentials
  appLabel: 3scale-api-management
  zync:
    image: 'quay.io/an_tran/zync:1.15.0-229'
  tenantName: 3scale
  apicast:
    managementAPI: status
    openSSLVerify: false
    productionSpec:
      replicas: 0
    stagingSpec:
      replicas: 0
  wildcardDomain: apps-crc.testing
EOF

• Run the operator

make run

• You should see zync/zync-que pods running as normal

[briangallagher]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[akostadinov]

This looks legit. Since some time Rails added full environment for database tasks because they added the encrypted stuff stuff. Thank you!