This message was deleted.

Is

Cluster

aws.eks.Cluster

? (Asking because I need to know which provider you're seeing this with.)

What version are you using of the AWS CLI?

What version of kubectl are you using?

G:\DWork\osource\cloudc\devops\pulumi\java\gcp\gke>kubectl version

WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.

Client Version: <http://version.Info|version.Info>{Major:"1", Minor:"24", GitVersion:"v1.24.2", GitCommit:"f66044f4361b9f1f96f0053dd46cb7dce5e990a8", GitTreeState:"clean", BuildDate:"2022-06-15T14:22:29Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"windows/amd64"}

Kustomize Version: v4.5.4

Unable to connect to the server: dial tcp 127.0.0.1:62506: connectex: No connection could be made because the target machine actively refused it.

G:\DWork\osource\cloudc\devops\pulumi\java\gcp\gke>where kubectl

C:\Program Files\Docker\Docker\resources\bin\kubectl.exe

These are the links I'm looking at to debug your issue BTW: • https://stackoverflow.com/questions/72473455/is-there-a-way-to-solve-kubeconfig-user-entry-is-using-deprecated-api-version • https://github.com/pulumi/pulumi-eks/issues/599 I was able to find the closed GH issue by doing an org-wide search in GH. (But I also remember seeing a similar problem before, so I had extra context.) I'm asking for the details here to see if we can improve the docs so others don't hit the same issue.

by default this java code is launching 1.22, even AWS console is complaining to upgrade..which api should we see to

final var cluster = new Cluster("eks-cluster");
aContext.export("kubeconfig", cluster.kubeconfig());

to launch the latest k8s, currently latest one in aws is 1.23

Try ensuring that your kubectl version matches your cluster version.

How to launch latest k8s cluster.. that way I can take the latest of both..

I'd suggest trying making them match first and see if that resolves the issue. It looks like you're launching 1.22 and you have kubectl version 1.24. Try specifying an explicit EKS-supported version when you launch the cluster, and make sure that version matches whatever kubectl you have installed: https://www.pulumi.com/registry/packages/eks/api-docs/cluster/#version_java

Diagnostics: eksindexVpcCni (eks-cluster-vpc-cni): error: Command failed: kubectl apply -f C:\Users\RAJANA~1\AppData\Local\Temp\tmp-22212N6AzGomhBZEB.tmp Kubeconfig user entry is using deprecated API version client.authentication.k8s.io/v1alpha1. Run 'aws eks update-kubeconfig' to update. Warning: spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].key: beta.kubernetes.io/os is deprecated since v1.14; use "kubernetes.io/os" instead Warning: spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[1].key: beta.kubernetes.io/arch is deprecated since v1.14; use "kubernetes.io/arch" instead error: unable to recognize "C:\\Users\\RAJANA~1\\AppData\\Local\\Temp\\tmp-22212N6AzGomhBZEB.tmp": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1" kubernetescore/v1ConfigMap (eks-cluster-nodeAccess): error: failed to initialize discovery client: exec plugin: invalid apiVersion "client.authentication.k8s.io/v1alpha1" pulumipulumiStack (eks-dev): Kubeconfig user entry is using deprecated API version client.authentication.k8s.io/v1alpha1. Run 'aws eks update-kubeconfig' to update. Warning: spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].key: beta.kubernetes.io/os is deprecated since v1.14; use "kubernetes.io/os" instead Warning: spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[1].key: beta.kubernetes.io/arch is deprecated since v1.14; use "kubernetes.io/arch" instead error: unable to recognize "C:\\Users\\RAJANA~1\\AppData\\Local\\Temp\\tmp-22212N6AzGomhBZEB.tmp": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1" error: Running program [PID: 18808](unknown) failed with an unhandled exception: io.grpc.StatusRuntimeException: UNAVAILABLE: error reading from server: read tcp 127.0.0.153436 >127.0.0.153435: use of closed network connection at io.grpc.Status.asRuntimeException(Status.java:535) at io.grpc.stub.ClientCalls$UnaryStreamToFuture.onClose(ClientCalls.java:533) at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:553) at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:68) at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:739) at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:718) at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:833) Resources: + 18 created Duration: 10m24s

That sounds like it could be a network issue?

https://pulumi-community.slack.com/archives/C84L4E3N1/p1661526320881479?thread_ts=1661502652.446759&cid=C84L4E3N1 It says api issue..AWS console says no proper permission

Are you running Pulumi as an IAM principal with FullAdmin?

I am the root user in aws.. beyond that, I have not configured any IAM principals other than defaults that come with default root user