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
Is your feature request related to a problem? Please describe.
In AWS or GCP, one can assign a mapping between cloud specific identities and k8s service accounts. Since Conjur already has AWS IAM, GCP and Azure authentication methods it would be desirable to use said identities for authentication rather than using the kubernetes authentication method.
Describe the solution you would like
Allow side car container to support alternative authentication methods like GCP, AWS IAM or Azure.
Describe alternatives you have considered
None
Additional context
Operational overhead is reduced since the k8s authenticator can be cumbersome because an authenticator must be configured per k8s cluster.
Time spent troubleshooting will be reduced since non k8s authentication methods are less complex since we are leveraging already existing cloud identities.
Sidecar deployment is simplified in managed k8s clusters because we are leveraging already existing cloud identities.
I have added GCP authentication in the forked repository below by implementing a factory design pattern (which could easily be implement AWS IAM and Azure authentication methods): AndrewCopeland#1
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In AWS or GCP, one can assign a mapping between cloud specific identities and k8s service accounts. Since Conjur already has AWS IAM, GCP and Azure authentication methods it would be desirable to use said identities for authentication rather than using the kubernetes authentication method.
Describe the solution you would like
Allow side car container to support alternative authentication methods like GCP, AWS IAM or Azure.
Describe alternatives you have considered
None
Additional context
I have added GCP authentication in the forked repository below by implementing a factory design pattern (which could easily be implement AWS IAM and Azure authentication methods):
AndrewCopeland#1
The text was updated successfully, but these errors were encountered: