You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might be useful to add the option to label and annotate the different pods from the values.yaml. That enables service meshes like consul to autoinject sidecars through hooks.
The text was updated successfully, but these errors were encountered:
We are leveraging Azure Workload Identity for managed identity access to the metastore database. A new requirement for the feature (as it gets ready for GA) is a label added to each pod. To get around this we are using Helm's Kustomize post-processor to add the label, but it'd be nice for it to have first class representation in the chart.
Similarly, while we wait for Seq 2023.x (which includes the latest Azure.Identity and native support for AZWI) we must also annotate the pods to add a sidecar that enables AZWI for applications lacking first-class support. We have to use the same post-processor to add the annotation. While this is a temporary requirement for us, I can see the need to support annotations generally.
For now we'll continue to use the Helm post-processor but a thumbs up for supporting both labels and annotations
It might be useful to add the option to label and annotate the different pods from the values.yaml. That enables service meshes like consul to autoinject sidecars through hooks.
The text was updated successfully, but these errors were encountered: