-
Notifications
You must be signed in to change notification settings - Fork 73
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
Kubernetes provider 1.2.0 release notes #866
Kubernetes provider 1.2.0 release notes #866
Conversation
releaseNotes/KubernetesProvider.md
Outdated
|
||
### New Features | ||
* Added support for feature flags, which allows feature flag settings to be saved to a Kubernetes ConfigMap. | ||
* Added the `featureFlag.selectors` property for feature flag filtering. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added support for feature flags, which allows projecting feature flags to the target ConfigMap.
- Added the
spec.featureFlag.selectors
property for filtering the feature flags by multiple combinations ofkeyFilter
andlabelFilter
. - Added the
sepc.featureFlag.refresh
property for periodically updating feature flags with the latest data from App Configuration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit too many details. We can point people to the documentation. The release notes aren't documentation.
releaseNotes/KubernetesProvider.md
Outdated
* Added the `featureFlag.refresh` property for periodically fetching latest feature flag values and update Kubernetes ConfigMap accordingly. | ||
|
||
### Enhancements | ||
* Added support for setting `nodeSelector`, `affinity` and `tolerations` when use helm to install Azure App Configuration Kubernetes Provider. It's useful to control which nodes the Kubernetes Provider pod can be scheduled. [#858](https://github.com/Azure/AppConfiguration/issues/858) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added support for setting nodeSelector
, affinity
and tolerations
when using helm to install Azure App Configuration Kubernetes Provider. It's useful for node assignment management
releaseNotes/KubernetesProvider.md
Outdated
|
||
### Enhancements | ||
* Added support for setting `nodeSelector`, `affinity` and `tolerations` when use helm to install Azure App Configuration Kubernetes Provider. It's useful to control which nodes the Kubernetes Provider pod can be scheduled. [#858](https://github.com/Azure/AppConfiguration/issues/858) | ||
* Added support for setting `autoscaling.enabled` when use helm to install Azure App Configuration Kubernetes Provider. It defaults to `false` and must be set to `true` for enabling [HorizontalPodAutoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) to automatically manage scale for Kubernetes Provider. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added support for setting autoscaling
when using helm to install Azure App Configuration Kubernetes Provider. Setting autoscaling.enabled
to true
to use HorizontalPodAutoscaler for managing pod autoscaling of Kubernetes Provider. autoscaling
is disabled by default.
releaseNotes/KubernetesProvider.md
Outdated
## 1.2.0 - | ||
|
||
### New Features | ||
* Added support for feature flags, which allows feature flag settings to be saved to a Kubernetes ConfigMap. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This depends on the release of FM libraries of other languages. We will need some coordination before we can declare the support for feature flags.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. So the release sequence should be FM libraries (dotnet/java spring) -> k8s provider.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, something like that, and in k8s provider release, we will say which version of FM library people need to use and on which platform. We will need quickstart/tutorial docs for k8s provider FM as well.
releaseNotes/KubernetesProvider.md
Outdated
@@ -2,6 +2,17 @@ | |||
|
|||
[Image][image] | [Sample][sample] | |||
|
|||
## 1.2.0 - | |||
|
|||
### New Features |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New features are enhancement too.
releaseNotes/KubernetesProvider.md
Outdated
@@ -6,8 +6,8 @@ | |||
|
|||
### Enhancements | |||
* Added support for feature flags, which allows projecting feature flags to the target ConfigMap using [Microsoft Feature Flag schema](https://github.com/Azure/AppConfiguration/blob/main/docs/FeatureManagement/FeatureFlag.v1.1.0.schema.json). The ConfigMap can be consumed by Feature Management libraries in all languages. | |||
* [.NET Feature Management](https://github.com/microsoft/FeatureManagement-Dotnet) v3.2.0 | |||
* [Spring Cloud Azure Feature Management](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/spring/spring-cloud-azure-feature-management) v5.9.0-beta.1 | |||
* [.NET Feature Management](https://github.com/microsoft/FeatureManagement-Dotnet) (version 3.2.0 or later) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
v3.2.0 or later
releaseNotes/KubernetesProvider.md
Outdated
## 1.2.0 - | ||
|
||
### Enhancements | ||
* Added support for feature flags, which allows projecting feature flags to the target ConfigMap using [Microsoft Feature Flag schema](https://github.com/Azure/AppConfiguration/blob/main/docs/FeatureManagement/FeatureManagement.v1.0.0.schema.json). The ConfigMap can be consumed by Feature Management libraries in all languages. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not something that can be explained in a sentence or two. The support in other languages is independent on this release. In this case, I would skip most of the details and have something like below. We can include a link to a document if we have one ready when this release note is published.
- Added support for downloading feature flags from Azure App Configuration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure the "link to a doc" refers to what doc, and where the link to include.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The quickstart for feature management using the k8s provider.
No description provided.