-
Notifications
You must be signed in to change notification settings - Fork 131
Open
Description
When deploying Liqo on AWS EKS, the standard Kubernetes client certificate-based authentication mechanism isn't available natively, as EKS relies on IAM authentication and the aws-iam-authenticator mechanism. Currently, this appears to require manual configuration steps. Are there plans to develop automation for this part as well?
Metadata
Metadata
Assignees
Labels
No labels