Open johnnally opened 3 years ago
Should kubedriver be expected to work with an Amazon EKS Cluster ?
I'd say yes, we'd like it to, but it's never been tested. The assumption has been that the kubernetes client we use supports everything kubectl does, as it uses the same config file. However, based on No such file or directory: 'aws': 'aws'"
it's possible that EKS authentication requires additional libraries to be installed? As this is not installed, I assume authentication cannot be completed but the client continue anyway, which causes the Forbidden error seen later in the logs.
Not sure if the "Create kubeconfig manually" section in this will help: https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html
Otherwise, we may have to look into adding the aws
command line tool into the docker image?
Hi Daniel,
we actually built a kubedriver image with asw cli installed on it. it got us past the aws cli error, and now we are restricted by user permissions it seems on amazon eks side of things. we will be looking into more detail later, but for now this is fine and can be closed.
Thanks, John
Hi,
We are investigating using kubedriver with EKS Cluster. We load a deployment location for the EKS Cluster based on the
kubectl config view --raw
output. In the kubectl config view output the user definition section looks similar to below ( i have replaced some info with <> below):afterwards I added the deployment location to CP4NA:
When I try a simple pod instance installation on EKS Cluster via a CP4NA assembly I get the below error in the kubedriver log:
afterwards in the kubedriver logs you can see some more stack messages that mention openshift client (/usr/local/lib/python3.7/site-packages/openshift/dynamic/client.py) etc,...
should kubedriver be expected to work with an Amazon EKS Cluster ? or would require a change request for the driver etc..,