0beb3d02f7
- If authentication token is not specified in provider, attempt to get the token using workload identity. = Add new field .spec.serviceAccountName to support multi-tenant workload identity as defined in RFC-0010 to use an identity with a service account other than the notification-controller. - Use proxy to get the token if specified in provider spec. - Cache the tokens if enabled in the notification controller options. - If address has SAS connection string, use that for authentication, this takes priority over token-authentication - If static JWT token is specified in the secret reference, use it for authentication, this takes priority over workload identity-acquired token. - Update RBAC for notification-controller to be able to create service token requests. - Add unit tests for the 3 authentication mechanisms (SAS, JWT, managed identity). - Add documentation for using single-tenant and multi-tenant approaches of workload identity with azureeventhub provider. - Add operation post to github helpers and provider controller for cache event metrics - Enable token cache by default. Signed-off-by: Dipti Pai <diptipai89@outlook.com> review comments Signed-off-by: Dipti Pai <diptipai89@outlook.com> enable cache by default Signed-off-by: Dipti Pai <diptipai89@outlook.com> |
||
|---|---|---|
| .. | ||
| v1 | ||
| v1beta1 | ||
| v1beta2 | ||
| v1beta3 | ||
| go.mod | ||
| go.sum | ||