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
We have different namespaces (teams), accessing external (azure resources) metrics.
We would like those teams each to use it's own Azure AAD Identity - to ensure least privilege access.
At the best scenario, we would even like to access each resource with separate Identity ,(AAD Pod Identity project).
We are fine with both installing single shared Keda metrics server, Wich will pick the identities from CRD per resource or something like that, or having KEDA metrics server installed per namespace.
We just looking the external requests for the metrics to be done at least by per-namespace identities.
If you think it is impossible with current Keda architecture - can you explain which workaround can be taken, and to provide some draft of estimation for this effort - we'd consider the contribution here.
This discussion was converted from issue #48 on November 30, 2021 09:40.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What we are trying to achieve:
We have different namespaces (teams), accessing external (azure resources) metrics.
We would like those teams each to use it's own Azure AAD Identity - to ensure least privilege access.
At the best scenario, we would even like to access each resource with separate Identity ,(AAD Pod Identity project).
We are fine with both installing single shared Keda metrics server, Wich will pick the identities from CRD per resource or something like that, or having KEDA metrics server installed per namespace.
We just looking the external requests for the metrics to be done at least by per-namespace identities.
If you think it is impossible with current Keda architecture - can you explain which workaround can be taken, and to provide some draft of estimation for this effort - we'd consider the contribution here.
Beta Was this translation helpful? Give feedback.
All reactions