Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🎉 Release controller 0.15.0 and helm chart 0.17.0 🎉 #595

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,32 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## 0.15.0

**Full Changelog**: /~https://github.com/ngrok/ngrok-operator/compare/ngrok-operator-0.14.3...ngrok-operator-0.15.0

### Added

- Gateway API to Endpoints conversion by @Alice-Lilith in [#588](/~https://github.com/ngrok/ngrok-operator/pull/588)

- Gateway API ReferenceGrant support (endpoints only) by @Alice-Lilith in [#589](/~https://github.com/ngrok/ngrok-operator/pull/589). When using the Gateway API configuration and translating to endpoints, ReferenceGrants will be required for cross-namespace references as dictated by Gateway API. You may opt-out of support for ReferenceGrants and always allow cross namespace references using the `--disable-reference-grants` in the pod arguments or using the helm value `gateway.disableReferenceGrants`.

- Support for the `k8s.ngrok.com/bindings` annotation (endpoints only) to set bindings on endpoints generated from Ingresses and Gateway API config by @Alice-Lilith in [#593](/~https://github.com/ngrok/ngrok-operator/pull/593).

- Implemented support for configuring upstream client certificates in the `AgentEndpoint` respirces and Gateway API Gateway Backend TLS config to configure client certificates to be sent to upstream services (endpoints only) bby @Alice-Lilith in [#594](/~https://github.com/ngrok/ngrok-operator/pull/594)

### Changed

- Endpoints are now the default for translations from `Ingress`, LoadBalancer Service, and Gateway API config by @Alice-Lilith in [#596](/~https://github.com/ngrok/ngrok-operator/pull/596) The `k8s.ngrok.com/mapping-strategy: endpoints` annotation is no longer required for endpoints conversion. Similarly, you may still use Edges instead with the `k8s.ngrok.com/mapping-strategy: edges` annotation, but Edges will be removed in a future release.

- Auto enable Gateway API support by @Alice-Lilith in [#592](/~https://github.com/ngrok/ngrok-operator/pull/592). Instead of needing to opt-in to Gateway API support, we now enable it by default if the Gateway API CRDs are detected. You may still opt-out using the `enable-feature-gateway` flag on the pod arguments or using the helm value `gateway.enabled`.

- Replaced binding name printcolumn with endpoint selectors for KubernetesOperator resources by @masonj5n in [#586](/~https://github.com/ngrok/ngrok-operator/pull/586)

- Updated notes.txt to reflect bindings API changes by @masonj5n in [#585](/~https://github.com/ngrok/ngrok-operator/pull/585)

- Support for latest bindings configuration (endpoints only) with the `k8s.ngrok.com/bindings` annotation to set bindings on endpoints generated from LoadBalancer Service resoruces by @Megalonia in [#590](/~https://github.com/ngrok/ngrok-operator/pull/590)

## 0.14.3
**Full Changelog**: /~https://github.com/ngrok/ngrok-operator/compare/ngrok-operator-0.14.2...ngrok-operator-0.14.3

Expand Down
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.14.3
0.15.0
26 changes: 26 additions & 0 deletions helm/ngrok-operator/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,32 @@ All notable changes to the helm chart will be documented in this file. Please se
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## 0.17.0

**Full Changelog**: /~https://github.com/ngrok/ngrok-operator/compare/helm-chart-0.17.0-rc.4...helm-chart-0.17.0

### Added

- Gateway API to Endpoints conversion by @Alice-Lilith in [#588](/~https://github.com/ngrok/ngrok-operator/pull/588)

- Gateway API ReferenceGrant support (endpoints only) by @Alice-Lilith in [#589](/~https://github.com/ngrok/ngrok-operator/pull/589). When using the Gateway API configuration and translating to endpoints, ReferenceGrants will be required for cross-namespace references as dictated by Gateway API. You may opt-out of support for ReferenceGrants and always allow cross namespace references using the `--disable-reference-grants` in the pod arguments or using the helm value `gateway.disableReferenceGrants`.

- Support for the `k8s.ngrok.com/bindings` annotation (endpoints only) to set bindings on endpoints generated from Ingresses and Gateway API config by @Alice-Lilith in [#593](/~https://github.com/ngrok/ngrok-operator/pull/593).

- Implemented support for configuring upstream client certificates in the `AgentEndpoint` respirces and Gateway API Gateway Backend TLS config to configure client certificates to be sent to upstream services (endpoints only) bby @Alice-Lilith in [#594](/~https://github.com/ngrok/ngrok-operator/pull/594)

### Changed

- Endpoints are now the default for translations from `Ingress`, LoadBalancer Service, and Gateway API config by @Alice-Lilith in [#596](/~https://github.com/ngrok/ngrok-operator/pull/596) The `k8s.ngrok.com/mapping-strategy: endpoints` annotation is no longer required for endpoints conversion. Similarly, you may still use Edges instead with the `k8s.ngrok.com/mapping-strategy: edges` annotation, but Edges will be removed in a future release.

- Auto enable Gateway API support by @Alice-Lilith in [#592](/~https://github.com/ngrok/ngrok-operator/pull/592). Instead of needing to opt-in to Gateway API support, we now enable it by default if the Gateway API CRDs are detected. You may still opt-out using the `enable-feature-gateway` flag on the pod arguments or using the helm value `gateway.enabled`.

- Replaced binding name printcolumn with endpoint selectors for KubernetesOperator resources by @masonj5n in [#586](/~https://github.com/ngrok/ngrok-operator/pull/586)

- Updated notes.txt to reflect bindings API changes by @masonj5n in [#585](/~https://github.com/ngrok/ngrok-operator/pull/585)

- Support for latest bindings configuration (endpoints only) with the `k8s.ngrok.com/bindings` annotation to set bindings on endpoints generated from LoadBalancer Service resoruces by @Megalonia in [#590](/~https://github.com/ngrok/ngrok-operator/pull/590)

## 0.17.0-rc.4

**Full Changelog**: /~https://github.com/ngrok/ngrok-operator/compare/helm-chart-0.17.0-rc.2...helm-chart-0.17.0-rc.4
Expand Down
4 changes: 2 additions & 2 deletions helm/ngrok-operator/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
apiVersion: v2
name: ngrok-operator
description: The official ngrok Kubernetes Operator.
version: 0.17.0-rc.4
appVersion: 0.14.3
version: 0.17.0
appVersion: 0.15.0
keywords:
- ngrok
- networking
Expand Down

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.