externalImportEnabled with Amazon EKS cluster does not work

[youwalther65]

Probably I do have a wrong understanding, how I can import exsiting resources from a running Amazon EKS cluster into the simulator, but this is what I 've done:

1. Run make build to create Go binaries
2. Created a config.yaml pointing to my Amazon EKS cluster

$ cat config.yaml | grep -v "^#"


apiVersion: kube-scheduler-simulator-config/v1alpha1
kind: SimulatorConfiguration

port: 1212

etcdURL: "http://127.0.0.1:2379"

corsAllowedOriginList:
  - "http://localhost:3000"

kubeConfig: "/Users/waltju/.kube/config"

kubeApiServerUrl: "https://<redacted>.gr7.eu-west-1.eks.amazonaws.com"

kubeSchedulerConfigPath: ""

externalImportEnabled: true

resourceSyncEnabled: false

3. Started simulator

$ ./simulator/bin/simulator 
I0411 10:34:09.715563   60423 simulator.go:81] waiting for kube-system namespace to be ready: Get "https://1151B40A90049914622A345DEB497090.gr7.eu-west-1.eks.amazonaws.com/api/v1/namespaces/kube-system": tls: failed to verify certificate: x509: “kube-apiserver” certificate is not trusted
I0411 10:34:14.643937   60423 simulator.go:81] waiting for kube-system namespace to be ready: Get "https://1151B40A90049914622A345DEB497090.gr7.eu-west-1.eks.amazonaws.com/api/v1/namespaces/kube-system": tls: failed to verify certificate: x509: “kube-apiserver” certificate is not trusted
...

What am I doing wrong? Is this possible at all? Thx.

[sanposhiho]

See https://github.com/kubernetes-sigs/kube-scheduler-simulator/blob/master/simulator/docs/import-cluster-resources.md.
kubeApiServerUrl doesn't have to point to your EKS.

[youwalther65]

I found it here. So this is the URL of the kube-apiserver which is used for simulation, not for import. Is this the right understanding?

[sanposhiho]

Yes, you're right. So, for importing, the simulator only uses kubeConfig to access your cluster.
https://github.com/kubernetes-sigs/kube-scheduler-simulator/blob/master/simulator/config/config.go#L92

[sanposhiho]

Run make build to create Go binaries

Another point, it's probably easier to use the simulator with docker, edit /simulator/config.yaml and then run:

make docker_up

(make docker_up mounts /simulator/config.yaml for the simulator configuration)