Details
-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
None
Description
GCP uses it's own magic mechanism, EKS uses IAM, so using Kubeconfig is out the window.
Some possible solutions:
- Use the in-cluster authentication mechanism and run the log collection as some form of job (less work handles everything)
- Work out how to integrate the cloud specific authentication plugins (more work needs intervention with every new service provider)
Attachments
Issue Links
- is triggering
-
K8S-661 Handle AWS IAM in cbopinfo
- Closed
For Gerrit Dashboard: K8S-589 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
101188,2 | K8S-589: GCP & Azure Auth | master | couchbase-operator | Status: MERGED | +2 | +1 |