Open willdavsmith opened 1 week ago
:wave: @willdavsmith Thanks for filing this feature request.
A project maintainer will review this feature request and get back to you soon.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
:+1: We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
We've prioritized work on this issue. Please subscribe to this issue for notifications, we'll provide updates as we make progress.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
Overview of feature request
Today, if a user installs Radius with Azure workload identity enabled but doesn't have the Azure AD Workload Identity mutating admission webhook installed, we will fail on deployment time (unauthorized deployment). We could improve this to detect if the proper prerequisites are installed (helm chart) and fail if the user specifies that they want to enable Azure workload identity in Radius.
Acceptance criteria
Additional context
No response
Would you like to support us?
AB#12619