Bug-fix release of Service Binding Operator

Fixed bugs

• Fix Percona XtraDB Cluster (mysql) annotations by @pmacik in #1105
• Fix Percona XtraDB Cluster (mysql) annotations for k8s and test actual connection by @pmacik in #1106
• Project certificates together with other Crunchy Postgres bindings by @pedjak in #1084
• Fixed exposed host binding item for databases provisioned by Cloud Native Postgres Operator by @pedjak in #1081
• Make sure to return nil value when there was an error by @kadel in #1079

What's Changed

• Update Readme with spec alignment by @jasperchui in #1064
• Include operator package in existing subscription detection in install.sh by @pmacik in #1066
• [acceptance-tests] Fix oc version compare in before_all hook by @pmacik in #1067
• Add links to relevant articles/blog posts by @sadlerap in #1068
• Add architecture document by @pedjak in #1069
• test(acceptance): remove obsolete scenario by @pmacik in #1070
• test(acceptance): add annotations with nested attributes into scenario for CRD annotations by @pmacik in #1072
• Use mutil-arch generic test app image by @yselkowitz in #1075
• Use $scenario_id in acceptance tests when possible by @sadlerap in #1074
• build: add recipe for generating mocks by @sadlerap in #1076
• Introduce sample application (spring-petclinic + postgresql) to be used in quickstart by @pmacik in #1080
• Upgrade cert manager from v1.1.0 to v1.6.0 by @sadlerap in #1089
• Temporarily disable Cloud Native Postgres operator scenario for openshift 4.10 by @pmacik in #1090
• Update contribution guide and pull request template by @pedjak in #1091
• Update obsoleted release instructions by @pedjak in #1092
• Avoid expression evaluation in the script by @baijum in #1093
• Use certified-operators catalog source for Crunchy Postgres Operator in acceptance tests by @pmacik in #1096
• Update to OperatorSDK 1.16 by @pedjak in #1094
• Set channels to 'stable' for Operatorhub.io PR metadata by @pmacik in #1095
• Refactor getting started guide to use the sample spring-petclinic by @pmacik in #1085
• Fix operator-sdk version in merge-to-master GH action by @pmacik in #1099
• Switch log format back to JSON by @pmacik in #1101
• Remove unused CRDs and mock objects by @baijum in #1100
• Include pod logs while collecting kube resources in GitHub actions by @pmacik in #1108
• Bump version to v1.0.1 by @sadlerap in #1104
• Added Spring Petclinic Application Deployment yaml compatible with MySQL and custom resource yaml for creating instance of PerconaXtraDB cluster by @Kartikey-star in #1107

New Contributors

• @kadel made their first contribution in #1079
• @Kartikey-star made their first contribution in #1107

Full Changelog: v1.0.0...v1.0.1

Installing

Check OperatorHub page for installation instructions. Alternatively, you can install the operator by applying the published release.yaml file. If not installed through OLM, the operator requires that cert-manager is available on the cluster. It can be installed by:

kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.6.0/cert-manager.yaml

after that install the operator:

kubectl apply -f https://github.com/redhat-developer/service-binding-operator/releases/download/v1.0.1/release.yaml

The operator will be deployed in service-binding-operator namespace.