Also see the Arch Meeting recording on Apr 2nd 2024

How to handle accommodating different conflicting featuregate defaults for the same global in different parts of kubernetes (e.g. streaming lists in kube-controller-manager and kube-apiserver)

• • Best way to detect when this comes up?
  • What's the best way to handle it?
  • this will be true for kcm and false for kube-apiserver https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/client-go/features/known_features.go#L39 
  • OverrideDefault method https://github.com/kubernetes/component-base/blob/master/featuregate/feature_gate.go#L304
    • Nothing seems to be calling that in kube as-of today https://github.com/search?q=org%3Aopenshift+OverrideDefault&type=code
  • Options for short-term fix
    • MicroShift uses OverrideDefault to set 1 value for the flag (probably have to patch out the code elsewhere that calls the same function differently)
    • Add a carry patch to force one code path to not use the global feature flag to determine its behavior
  • Options for long-term identifying this class of problem coming up again
    • Add to rebase process a step that builds each component we compile together and asks for its default feature flag settings so we can identify conflicts