#590 added a new fetchStrategy called platforms which is the new encouraged strategy.
It is a confusing experience that you can still define multiple fetchStrategies (anonHTTP and platforms) but we don't fallback.
We could update the Shim CRD to define custom logic using x-kubernetes-validation. For example: https://github.com/kate-goldenring/runtime-class-manager/compare/arch-agnostic-fetch-strategy...kate-goldenring:runtime-class-manager:disallow-multiple-fetch-strategies?expand=1.
Or we could deprecate anonHTTP #594 and cross this bridge if we ever introduce any other strategy.
#590 added a new
fetchStrategycalledplatformswhich is the new encouraged strategy.It is a confusing experience that you can still define multiple
fetchStrategies(anonHTTPandplatforms) but we don't fallback.We could update the
ShimCRD to define custom logic using x-kubernetes-validation. For example: https://github.com/kate-goldenring/runtime-class-manager/compare/arch-agnostic-fetch-strategy...kate-goldenring:runtime-class-manager:disallow-multiple-fetch-strategies?expand=1.Or we could deprecate
anonHTTP#594 and cross this bridge if we ever introduce any other strategy.