Releases: infrawatch/smart-gateway-operator
v5.1.2
Smart Gateway Operator v5.1.2
Smart Gateway Operator v5.1.2 for Service Telemetry Framework 1.5.
- [zuul] Add zuul job to SGO by @elfiesmelfie in #150
- [zuul] Use the stf-crc-jobs project template by @elfiesmelfie in #151
- Support OCP v4.12 through v4.14 by @leifmadsen in #152
- Adjust auth proxy SAR to be more specific by @csibbitt in #154
- Add optional spec.replaces field to CSV for update graph compliance by @compi-migui in #155
- Set features.operators.openshift.io/disconnected to True by @vkmc in #156
- Add optional spec.replaces field to CSV for update graph compliance by @compi-migui in #157
Full Changelog: v5.1.1...v5.1.2
Contributors
Assets 2
v5.1.1
Smart Gateway Operator v5.1.1
Smart Gateway Operator v5.1.1 for Service Telemetry Framework 1.5.3.
This release is to address a missing dependency issue when deploying STF 1.5.3 on OCP v4.11. STF 1.5.3 minimum OpenShift release will be v4.12.
What's Changed
- Support OCP v4.12 through v4.14 by @leifmadsen in #153
Full Changelog: v5.1.0...v5.1.1
Contributors
Assets 2
v5.1.0
Smart Gateway Operator v5.1.0
Smart Gateway Operator v5.1.0 for Service Telemetry Framework 1.5.3.
Changes since v5.0.1
17b478c Update base image to pass security scans (#148)
a7da1f7 Next release of STF will start at OCP 4.11 (#147)
9780020 Add requires infrastructure annotations (#146)
f2bb74c Bump origin-ansible-operator base image (#145)
0f44c51 Add logs to generate bundle (#143)
9a44ff8 Bump compatibility from 4.10-4.12 to 4.10-4.14 (#144)
b028753 Honor tlsSecretName from ES application config (#142)
cd7c2f4 Change generate_bundle.sh to output JSON (#141)
f89c33f Move to newest oauth-proxy container (#140)
51a3724 maxOpenShiftVersion 4.12 in OLM properties (#138)
1d76c82 Implement changes for operator-sdk-1.26.0 testing (#137)
df23d63 GHA checkout action v2 is deprecated (#135)
db1fdcb Changes for 4.12 (#134)
07a2c71 Expand support for OCP 4.11 (#130)
e05bd8f Fix the valid-subscription annotation (#127)
29417a4 Lock the bundle to OCP v4.10 (#125)
v5.0.1
51a3724 maxOpenShiftVersion 4.12 in OLM properties (#138)
1d76c82 Implement changes for operator-sdk-1.26.0 testing (#137)
df23d63 GHA checkout action v2 is deprecated (#135)
db1fdcb Changes for 4.12 (#134)
07a2c71 Expand support for OCP 4.11 (#130)
e05bd8f Fix the valid-subscription annotation (#127)
29417a4 Lock the bundle to OCP v4.10 (#125)
v5.0.0
Smart Gateway Operator v5.0.0
Smart Gateway Operator v5.0.0 for Service Telemetry Operator 1.5.
Changes since v4.0.3
664f3f0 Lock the bundle to OCP v4.10 (#125) (#126)
db5ae97 (tag: v5.0.0-beta1) Update base image for Operator to v4.10 (#124)
b1aa07c Base changes to allow deployment on OCP v4.10 (#123)
fde553c Set placeholder namespace in role_binding.yaml (#121)
daad953 Create separate ServiceAccount for Smart Gateways (#119)
8817ec1 Resolve issues with auth delegation RBAC (#117)
349e082 Adjust cluster roles for oauth-proxy (#110) (#114)
737a30e Fix linting by locking versions (#113)
e8b5d5e Revert "Migrate to operator-sdk 1.16.0 (#108)" (#111)
8328ed8 Migrate to operator-sdk 1.16.0 (#108)
11f30de Use correct type for blockEventBus (#106)
v5.0.0-beta2
v5.0.0-beta1
Smart Gateway Operator v5.0.0-beta1
Beta release of Smart Gateway Operator v5.0.0-beta1 in preparation of STF 1.5 release.
Changes since v4.0.3
db5ae97 Update base image for Operator to v4.10 (#124)
b1aa07c Base changes to allow deployment on OCP v4.10 (#123)
fde553c Set placeholder namespace in role_binding.yaml (#121)
daad953 Create separate ServiceAccount for Smart Gateways (#119)
8817ec1 Resolve issues with auth delegation RBAC (#117)
349e082 Adjust cluster roles for oauth-proxy (#110) (#114)
737a30e Fix linting by locking versions (#113)
e8b5d5e Revert "Migrate to operator-sdk 1.16.0 (#108)" (#111)
8328ed8 Migrate to operator-sdk 1.16.0 (#108)
11f30de Use correct type for blockEventBus (#106)
v4.0.3
Smart Gateway Operator v4.0.3
Modify the Smart Gateway Operator so that it has permissions to create ServiceAccounts, ClusterRoles, and ClusterRoleBindings. Update the smart-gateway-operator Ansible role so that it creates a new smart-gateway ServiceAccount for the Smart Gateway pods to use. Create a ClusterRole so that the oauth-proxy container has appropriate permissions to run, and then create a ClusterRoleBinding to bind the ClusterRole to the smart-gateway ServiceAccount.
This should resolve issues with the Smart Gateway Operator creating Smart Gateway workloads that are unable to be scraped by Prometheus due to missing RBAC permissions by the oauth-proxy.
Changes since v4.0.2
e13398a Create separate ServiceAccount for Smart Gateways (#119) (#120)