Stable release 0.14.0

[slopezz]

Create stable release v0.14.0, main changes included:

• Zync controller has been migrated to the new workload reconciler v2 https://github.com/3scale-ops/saas-operator/pull/162
• Apicast controller has been migrated to the new workload reconciler v2 https://github.com/3scale-ops/saas-operator/pull/163
• Fix replicas reconcile https://github.com/3scale-ops/saas-operator/pull/164
• Improve testing with resources introspection ad resources updates https://github.com/3scale-ops/saas-operator/pull/168 https://github.com/3scale-ops/saas-operator/pull/169 https://github.com/3scale-ops/saas-operator/pull/170 https://github.com/3scale-ops/saas-operator/pull/171 https://github.com/3scale-ops/saas-operator/pull/172 https://github.com/3scale-ops/saas-operator/pull/173 https://github.com/3scale-ops/saas-operator/pull/174 https://github.com/3scale-ops/saas-operator/pull/175 https://github.com/3scale-ops/saas-operator/pull/176 https://github.com/3scale-ops/saas-operator/pull/177 https://github.com/3scale-ops/saas-operator/pull/178
• Add a profiler for debugging https://github.com/3scale-ops/saas-operator/pull/180
• ExternalSecrets have replaced SecretDefinition to manage Secrets https://github.com/3scale-ops/saas-operator/pull/181
• Improve logging configuration https://github.com/3scale-ops/saas-operator/pull/182
• Fix redis clients memory leak https://github.com/3scale-ops/saas-operator/pull/183

What to do before

Related to v2 reconcile and traffic label

• Before approving manually the install-plan in pro-saas cluster, it is needed to manually add the following labels to each pertinent k8s Deployment:

  saas.3scale.net/traffic: apicast-production
  saas.3scale.net/traffic: apicast-staging
  saas.3scale.net/traffic: zync

• The reason is, saas-operator will add that label immediately as label selector on every k8s Service, but Deployment new pods will take a few seconds to be running with that new label, so it can cause a downtime. Adding previously the label manually to every Deployment will have no negative impact and there will be no downtime. The rest of deployment were already updated on https://github.com/3scale-ops/saas-operator/pull/160

Related to secrets

• Set secrets-manager operator to 0 pods

What to do after

Related to secrets

• Approve the install plan
• ExternalSecret will be created by saas-operator, and will adopt current target secret without doing changes on the secrets data, which is the one used by saas-operator hashes:
  • It will add owner references to target secret (you can check it on argo now, an ExternalSecret resource which creates a Secret resource
  • Target secret labels will be merged with ExternalSecrets propagated labels and current ones from secrets-manager (last updated date, and updatedBy secrets-manager)
• You need to manually delete the SecretDefinitions, and to do so you need to manually edit each SecretDefinition by removing the metadata.finalizers field, then the SecretDefinition can ve finally deleted
• Delete manually secret-manager labels last updated date and updatedBy secrets-manager from target secrets
• Set secrets-manager operator to 1 pod
• Target secrets won't be updated anymore by secrets-manager

/kind feature /priority important-soon /assign

[raelga]

/lgtm

[3scale-robot]

LGTM label has been added.

Git tree hash: da31f5883b83bcb3c2e79642e69fe7f075b5da60

[slopezz]

/approve

[3scale-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: slopezz

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)~~ [slopezz] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment