Skip to content
This repository has been archived by the owner on Apr 27, 2020. It is now read-only.

EKS cluster name being ignored #87

Open
christopher-wong opened this issue Apr 8, 2020 · 0 comments
Open

EKS cluster name being ignored #87

christopher-wong opened this issue Apr 8, 2020 · 0 comments

Comments

@christopher-wong
Copy link

When specifying EKS, the resource seems to ignore the configuration.

 - name: eks-deploy
    type: kubernetes
    source:
      use_aws_iam_authenticator: true
      aws_eks_cluster_name: <MY-CLUSTER-NAME>
      aws_access_key_id: ((aws-access-key-id-dev))
      aws_secret_access_key: ((aws-secret-access-key-dev))
+ kubectl config set-cluster cluster --server=
20:43:15
Cluster "cluster" set.
20:43:15
+ kubectl config set-context kubernetes-resource --cluster=cluster --user auth
20:43:15
Context "kubernetes-resource" created.
20:43:15
+ kubectl config use-context kubernetes-resource
20:43:15
Switched to context "kubernetes-resource".
20:43:15
+ kubectl version
20:43:15
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4", GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"clean", BuildDate:"2020-03-12T21:03:42Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
20:43:15
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant