error: the server doesn't have resource type "svc"

Question

Admins-MacBook-Pro:~ Harshin$ kubectl cluster-info Kubernetes master is running at http://localhost:8080

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. error: the server doesn't have a resource type "services"

i am following this document

https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html?refid=gs_card

while i am trying to test my configuration in step 11 of configure kubectl for amazon eks

apiVersion: v1
clusters:
- cluster:
    server: ...
    certificate-authority-data: ....
  name: kubernetes
contexts:
- context:
    cluster: kubernetes
    user: aws
  name: aws
current-context: aws
kind: Config
preferences: {}
users:
- name: aws
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      command: heptio-authenticator-aws
      args:
        - "token"
        - "-i"
        - "kunjeti"
        # - "-r"
        # - "<role-arn>"
      # env:
        # - name: AWS_PROFILE
        #   value: "<aws-profile>"

Looks like your question contains a real credentials of your cluster. I highly recommend you to delete it. — Anton Kostenko, Jul 02 '18 at 14:00
now the client is connected to http://localhost:8080, using `kubectl --kubeconfig ~/.kube/xxx cluster-info` will ensure to use the specific config file. — Eric Ho, Jul 02 '18 at 17:24
@Harshin_ You may reference from a wrong kubeconfig file. Therefore you need to specify the config file in paramater. i.e. saved above file as: `~/.kube/kubeconfig`, you need to run `kubectl --kubeconfig ~/.kube/kubeconfig cluster-info` — Eric Ho, Jul 05 '18 at 16:39
@EricHo That worked, but end up in a another error 'error: the server doesn't have a resource type "services" ' — Karthikeyan, Jul 27 '18 at 11:17

score 6 · Answer 1 · edited Nov 22 '18 at 23:51

Change "name: kubernetes" to actual name of your cluster.

Here is what I did to work it through....

1.Enabled verbose to make sure config files are read properly.

kubectl get svc --v=10

2.Modified the file as below:

apiVersion: v1
clusters:
- cluster:
    server: XXXXX
    certificate-authority-data: XXXXX
  name: abc-eks
contexts:
- context:
    cluster: abc-eks
    user: aws
  name: aws
current-context: aws
kind: Config
preferences: {}
users:
- name: aws
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      command: aws-iam-authenticator
      args:
        - "token"
        - "-i"
        - "abc-eks"
        # - "-r"
        # - "<role-arn>"
      env:
        - name: AWS_PROFILE
          value: "aws"

created a second cluster with cli, the config is almost the same. It works. My credential file only has one default. For the console cluster, the verbose log printed it's not authorized. — rickcoup, Jan 02 '19 at 22:12

score 5 · Answer 2 · edited Oct 26 '18 at 07:02

5

I have faced a similar issue, however this is not a direct solution but workaround. Use AWS cli commands to create cluster rather than console. As per documentation, the user or role which creates cluster will have master access.

aws eks create-cluster --name <cluster name> --role-arn <EKS Service Role> --resources-vpc-config subnetIds=<subnet ids>,securityGroupIds=<security group id>

Make sure that EKS Service Role has IAM access(I have given Full however AssumeRole will do I guess).

The EC2 machine Role should have eks:CreateCluster and IAM access. Worked for me :)

edited Oct 26 '18 at 07:02

Unheilig

16,196
193
68
98

answered Oct 26 '18 at 06:44

Kailas J C

139
3
8

This is for users who login to AWS account using federated login. If you have followed the AWS get started guide to create EKS from console, you should re-create using the command above. Took me a while to resolve it. – mengjiann Jan 02 '19 at 08:38

score 2 · Answer 3 · edited Nov 22 '18 at 23:53

I had this issue and found it was caused default key setting in ~/.aws/credentials. We have a few AWS accounts for different customers plus a sandbox account for our own testing and research. So our credentials file looks something like this:

[default]

aws_access_key_id = abc

aws_secret_access_key = xyz

region=us-east-1


[cpproto]

aws_access_key_id = abc

aws_secret_access_key = xyz

region=us-east-1

[sandbox]

aws_access_key_id = abc

aws_secret_access_key = xyz

region=us-east-1

I was messing around our sandbox account but the [default] section was pointing to another account. Once I put the keys for sandbox into the default section the "kubectl get svc" command worked fine.

Seems we need a way to tell aws-iam-authenticator which keys to use same as --profile in the aws cli.

This was my problem. Thanks! – mbarlocker Jan 17 '19 at 22:39 — mbarlocker, Jan 17 '19 at 22:39

score 0 · Answer 4 · answered Oct 15 '18 at 11:19

I guess you should uncomment "env" item and change your refer to ~/.aws/credentials Because your aws_iam_authenticator requires exact AWS credentials.

Refer this document: https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html

To have the AWS IAM Authenticator for Kubernetes always use a specific named AWS credential profile (instead of the default AWS credential provider chain), uncomment the env lines and substitute with the profile name to use.

error: the server doesn't have resource type "svc"

4 Answers4

Linked