Ok, please help me to get create of eks cluster without any issues.
Can you confirm that we can create cluster in Azure also?
Hello @sreemanthena,
I created a post on how to create a managed k8s cluster on AKS, please follow:
Another simple post on how to create your first application on your AKS cluster:
All are in the KodeKloud Playground!
Hope this help,
Trung.
Hi @trung-kodekloud ,
By creating the cluster using the console, I’m not able to create the node-group as I get the error bellow.
I’ve followed the information in the link below to create a role for the ec2 call services
I’m trying to follow instructions on the video: [ Kubernetes for the Absolute Beginners – Hands-on Tutorial | KodeKloud ], after create the cluster, create the nodes.
The error:
User: arn:aws:iam::964762276523:user/odl_user_823013 is not authorized to perform: eks:CreateNodegroup on resource: arn:aws:eks:us-east-1:964762276523:cluster/ziriguidum with an explicit deny
link:
Amazon EKS node IAM role - Amazon EKS.
Thank you.
Raul.
Hi @raul.souza
It is currently not possible to create clusters with eksctl in the KodeKloud playgrounds.
As per the video, you must create your own personal AWS account to follow the instructions there.
If you are serious about cloud and devops, then having your own cloud accounts is pretty much a requirement. Cloud accounts cost virtually nothing to maintain, as long as you don’t create things which you forget to delete later.
thanks for the feedback.
I was trying to use my own aws account which also didn’t work; a deletion of service failed and incurred some extra charging. For this reason I opted for playground.
Is there any potential ETA regarding the fix for this issue?
Thank You.
Raul.
Hi,
I also go the error when create th eks
eksctl create cluster --name eksClusterRole --region us-east-1 --fargate
2025-01-27 08:43:32 [
] eksctl version 0.202.0
2025-01-27 08:43:32 [] using region us-east-1
2025-01-27 08:43:32 [] setting availability zones to [us-east-1d us-east-1c]
2025-01-27 08:43:32 [] subnets for us-east-1d - public:192.168.0.0/19 private:192.168.64.0/19
2025-01-27 08:43:32 [] subnets for us-east-1c - public:192.168.32.0/19 private:192.168.96.0/19
2025-01-27 08:43:32 [] using Kubernetes version 1.30
2025-01-27 08:43:32 [] creating EKS cluster “eksClusterRole” in “us-east-1” region with Fargate profile
2025-01-27 08:43:32 [] if you encounter any issues, check CloudFormation console or try ‘eksctl utils describe-stacks --region=us-east-1 --cluster=eksClusterRole’
2025-01-27 08:43:32 [] Kubernetes API endpoint access will use default of {publicAccess=true, privateAccess=false} for cluster “eksClusterRole” in “us-east-1”
2025-01-27 08:43:32 [] CloudWatch logging will not be enabled for cluster “eksClusterRole” in “us-east-1”
2025-01-27 08:43:32 [] you can enable it with ‘eksctl utils update-cluster-logging --enable-types={SPECIFY-YOUR-LOG-TYPES-HERE (e.g. all)} --region=us-east-1 --cluster=eksClusterRole’
2025-01-27 08:43:32 [] default addons vpc-cni, kube-proxy, coredns, metrics-server were not specified, will install them as EKS addons
2025-01-27 08:43:32 []
2 sequential tasks: { create cluster control plane “eksClusterRole”,
3 sequential sub-tasks: {
1 task: { create addons },
wait for control plane to become ready,
create fargate profiles,
}
}
2025-01-27 08:43:32 [] building cluster stack “eksctl-eksClusterRole-cluster”
2025-01-27 08:43:32 [] deploying stack “eksctl-eksClusterRole-cluster”
2025-01-27 08:44:02 [] waiting for CloudFormation stack “eksctl-eksClusterRole-cluster”
2025-01-27 08:44:02 [
] unexpected status “ROLLBACK_IN_PROGRESS” while waiting for CloudFormation stack “eksctl-eksClusterRole-cluster”
2025-01-27 08:44:02 [] unexpected status “ROLLBACK_IN_PROGRESS” while waiting for CloudFormation stack “eksctl-eksClusterRole-cluster”
2025-01-27 08:44:02 [] fetching stack events in attempt to troubleshoot the root cause of the failure
2025-01-27 08:44:02 [!] AWS::EC2::InternetGateway/InternetGateway: DELETE_IN_PROGRESS
2025-01-27 08:44:02 [!] AWS::IAM::Role/ServiceRole: DELETE_IN_PROGRESS
2025-01-27 08:44:02 [!] AWS::EC2::SecurityGroup/ControlPlaneSecurityGroup: DELETE_IN_PROGRESS
2025-01-27 08:44:02 [!] AWS::EC2::VPCGatewayAttachment/VPCGatewayAttachment: DELETE_IN_PROGRESS
2025-01-27 08:44:02 [!] AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPublicUSEAST1D: DELETE_IN_PROGRESS
2025-01-27 08:44:02 [!] AWS::IAM::Role/FargatePodExecutionRole: DELETE_IN_PROGRESS
2025-01-27 08:44:02 [!] AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPublicUSEAST1C: DELETE_IN_PROGRESS
2025-01-27 08:44:02 [!] AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPrivateUSEAST1D: DELETE_IN_PROGRESS
2025-01-27 08:44:02 [!] AWS::EC2::NatGateway/NATGateway: DELETE_IN_PROGRESS
2025-01-27 08:44:02 [!] AWS::EC2::SecurityGroup/ClusterSharedNodeSecurityGroup: DELETE_IN_PROGRESS
2025-01-27 08:44:02 [!] AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPrivateUSEAST1C: DELETE_IN_PROGRESS
2025-01-27 08:44:02 [] AWS::EC2::NatGateway/NATGateway: CREATE_FAILED – “Resource creation cancelled”
2025-01-27 08:44:02 [] AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPublicUSEAST1D: CREATE_FAILED – “Resource creation cancelled”
2025-01-27 08:44:02 [] AWS::EC2::SubnetRouteTableAssociation/RouteTableAssociationPublicUSEAST1C: CREATE_FAILED – “Resource creation cancelled”
2025-01-27 08:44:02 [] AWS::EC2::SecurityGroup/ControlPlaneSecurityGroup: CREATE_FAILED – “Resource creation cancelled”
2025-01-27 08:44:02 [] AWS::EC2::SecurityGroup/ClusterSharedNodeSecurityGroup: CREATE_FAILED – “Resource creation cancelled”
2025-01-27 08:44:02 [] AWS::EC2::RouteTable/PrivateRouteTableUSEAST1D: CREATE_FAILED – “Resource creation cancelled”
2025-01-27 08:44:02 [] AWS::EC2::RouteTable/PublicRouteTable: CREATE_FAILED – “Resource creation cancelled”
2025-01-27 08:44:02 [] AWS::EC2::RouteTable/PrivateRouteTableUSEAST1C: CREATE_FAILED – “Resource creation cancelled”
2025-01-27 08:44:02 [] AWS::EKS::Cluster/ControlPlane: CREATE_FAILED – “Resource handler returned message: "User: arn:aws:iam::339712982725:user/kk_labs_user_304800 is not authorized to perform: iam:PassRole on resource: arn:aws:iam::339712982725:role/eksctl-eksClusterRole-cluster-ServiceRole-sHHvJRUzypnP (Service: Eks, Status Code: 403, Request ID: 7ce11094-c1b5-4633-b91f-1a9266e23cf9)" (RequestToken: ff2607fe-11e5-cdf7-f068-a74e2ae974ae, HandlerErrorCode: AccessDenied)”
2025-01-27 08:44:02 [!] 1 error(s) occurred and cluster hasn’t been created properly, you may wish to check CloudFormation console
2025-01-27 08:44:02 [] to cleanup resources, run ‘eksctl delete cluster --region=us-east-1 --name=eksClusterRole’
2025-01-27 08:44:02 [] ResourceNotReady: failed waiting for successful resource state
Error: failed to create cluster “eksClusterRole”