Feature Flags are loaded randomly in the ConfigMap

[simonmalletrc]

Hello,

We have just finished configuring AppConfiguration Kubernetes Provider in our infrastructure and everything seems to be working except for the feature flags.

When I use the spec.featureFlag.refresh in conjuction with stakater/reloader, every refresh it does a rolling update.

Rolling updates are done only when changes are detected.
After investigation we found out that the order in which feature flags are loaded in the ConfigMap are completely random instead of being in alphabetical order which triggers a rolling update every refresh.

        featureFlag: #Optional. it is the content spec.featureFlag in the doc https://learn.microsoft.com/en-ca/azure/azure-app-configuration/reference-kubernetes-provider?tabs=default.
          selectors:
          - keyFilter: "*"
          - keyFilter: "*"
            labelFilter: dev
          - keyFilter: "*"
            labelFilter: dev35
          refresh:
            enabled: true
            interval: 1m

Expected Result

Rolling update only when actual changes

Actual Result

Rolling update with same Feature Flag values (because of feature flags being loaded randomly in the ConfigMap)

[linglingye001]

Hi @simonmalletrc , currently the Kubernetes provider pulls the latest feature flag settings from the app config store every refresh interval and regenerate the ConfigMap (even if the content hasn't changed). We already have PR aimed at optimizing this refresh process, so that the ConfigMap will only be updated when the selected keyValues/featureFlags really change. This enhancement will be included in the next version, please stay tuned.

[simonmalletrc]

Thank you !

[RichardChen820]

It's been fixed in the latest v2.1.0.