feat/dev/openshift

[roivaz]

Several features that improve the local-setup to make it usable also in a publicly accessible Openshift cluster:

• Adds an option to retrieve secret values from a known seed secret. This finally breaks the dependence of saas-operator from Vault. The override option was only usable in a local environment because secrets shouldn't be hard coded in a setup where the endpoints are published to the internet. Example usage:

https://github.com/3scale-ops/saas-operator/blob/3c91c7e514c5e8912ebca0efe26ec71dd128bd3d/config/local-setup/workloads/backend.yaml#L2-L20

• Reworks the local-setup to use a tekton pipeline for database setup. See:

https://github.com/3scale-ops/saas-operator/blob/3c91c7e514c5e8912ebca0efe26ec71dd128bd3d/config/local-setup/workloads/system.yaml#L115-L164

• local-setup kustomize config hard coded secrets have been removed. The user of the config is now expected to provide a file with the secret values. Check https://github.com/3scale-ops/saas-operator/blob/feat/dev/openshift/config/local-setup/README.md for more instructions.

• github actions have been upgraded

• Several options have been added to the System CR so domains can be properly configured via the CR.

/kind feature /priority important-soon /assign

[roivaz]

/retitle feat/dev/openshift

[3scale-robot]

LGTM label has been added.

Git tree hash: 74267bbaf444e57b9b820dcbfa97ed087dc1d896

[roivaz]

/approve

[3scale-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: roivaz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/3scale-ops/saas-operator/blob/main/OWNERS)~~ [roivaz] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment