New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation fails on Amazon EKS #1488
Comments
I've never seen that before on GKE or minikube; nor have I seen it before. My guess is that something about EKS leads to you being prompted for a username and our script doesn't allow for entering input. You can try to work around this by cd'ing to the directory containing your ksonnet app
And then running
And entering username when prompted. You could also emit YAML manifests for all the resources e.g
And try applying them using kubectl which is hopefully configured to correctly talk to your cluster. |
Tried:
What username is expected?
|
Not sure where the username is coming from. I'm guessing its an issue with ksonnet trying to connect to your Kubernetes cluster using basic auth. ks should read your KUBECONFIG file and use that to configure how it talks to your cluster. So it seems like an issue with ksonnet. As a work around can you try
You might also want to try deleting and recreating a new ksonnet environment
|
@Bryani any idea? @arun-gupta since I think its a ksonnet issue you might want to try https://kubernetes.slack.com/messages/ksonnet |
Amazon EKS uses aws-iam-authenticator and an IAM role to authenticate to the k8s cluster. Do you think ksonnet might be having trouble configuring that instead? Are there any other non-ksonnet ways to deploy kubeflow? |
@jlewi the suggested workaround:
seems to work. Here is the output:
Is there anything else required after this? |
Nope, it's up and running! I'd definitely file the bug with ksonnet, it should work in all cases. I don't know anything about aws-iam-authenticator but communication between that, and whatever service account ksonnet is running as, would be my guess for the issue. |
Will close this bug as it seems more like a ksonnet issue, following up there. |
* fix: let KFP profile controller use KFP version from upstream * update snapshots * disable suffix hash to workaround a problem * update snapshots * stop using commonprefix to let configmapref work * update snapshots
Trying to install Kubeflow on Amazon EKS as follows:
brew install ksonnet/tap/ks
orbrew upgrade ksonnet/tap/ks
The installation fails and here is the complete log:
The text was updated successfully, but these errors were encountered: