instance-type | common mapping of various cloud instance types | Map library

AWS CLI provides command describe-instance-types to list all offered EC2 instance types. It also allows to filter them by different attributes. Is it possible to do something similar with Google Cloud CLI?

I want to list all offered machine types with their attributes. Additionally, I would like to filter them by their attributes (memory size, cpus, etc).

we followed this guide to use GPU enabled nodes in our existing cluster but when we try to schedule pods we're getting 2 Insufficient nvidia.com/gpu error

Details:

We are trying to use GPU in our existing cluster and for that we're able to successfully create a NodePool with a single node having GPU enabled.

Then as a next step according to the guide above we've to create a daemonset and we're also able to run the DS successfully.

But now when we are trying to schedule the Pod using the following resource section the pod becomes un-schedulable with this error 2 insufficient nvidia.com/gpu

Used ami-0fd3c3c68a2a8066f from ap-south-1 region http://cloud-images.ubuntu.com/locator/ec2/, but unable to use t2.micro instance type against this.

Cluster Specification:

This is my Jenkins EC2 configuration:

• URL: $JENKINS_URL/configureClouds/
• Add new cloud: Amazon EC2
• Name: Amazon EC2 eu-central-1
• Amazon EC2 Credentials: AKIA...
• Region: eu-central-1
• EC2 Key Pair's Private Key: ubuntu
• Test connection: success
• Advanced...
• Instance Cap: 3
• No delay provisioning: checked
• Add AMI
• Description: Linux node
• AMI ID: ami-0293...
• Check AMI: 05052029...
• Instance Type: T3aMedium
• EBS Optimized: checked
• Monitoring: checked
• T2 Unlimited: checked
• Security group names: sg-0c2d... (opens SSH port 22)
• Remote FS root: ./jenkins
• Remote user: ubuntu
• AMI Type: unix
• Labels: aws ubuntu linux
• Usage: Use this node as much as possible
• Idle termination time: 30
• Advanced...
• Number of executors: 2
• Stop/Disconnect on Idle Timeout: checked
• Minimum number of instances: 1
• Minimum number of spare instances: 0
• Instance cap: 10
• Block device mapping: /dev/sda1=snap-0eadbe3f...:200:true:gp2, /dev/sdb=ephemeral0, /dev/sdc=ephemeral1
• Associate Public IP: checked
• Connection Strategy: Public DNS
• Host Key Verification Strategy: off
• Maximum Total Uses: 10
• Environment variables: checked (not listing all environment variables)
• Tool locations: checked (not listing all tool locations)

With this configuration, I would expect that at least 1 EC2 instance would be started, but no instance is started.

In the nodes page in Jenkins when I hit the provision via button, I get an error:

Oops! A problem occurred while processing the request. Logging ID=8ead3651-3809-4a47-984c-e0e494c705bb

In /log/all I have:

I just kicked off a g4dn.8xlarge instance on AWS. According to their website, this instance should have 128GB memory, as shown in the screenshot below:

However, I notice my model keeps running out of memory. When I investigated, I see this:

I've been trying since yesterday to get this CloudFormation template working... the goal is to launch an EC2 instance into a public subnet that I can access through HTTP. Everything looks like it has been created correctly to me, but the instance won't connect in the browser. Things I've checked:

• EC2 instance deployed in correct subnet
• Subnet has a route table pointing to an IGW
• EC2 instance has a public IP
• Security group allows inbound access over ports 80, 443 and 22 from all sources
• Creating without userdata
• verified user data works correctly in a manual EC2

Any suggestions for other things to check?

Here's my template:

I am having a problem where I am trying to restrict a deployment to work on avoid a specific node pool and nodeAffinity and nodeAntiAffinity don't seem to be working.

• We are running DOKS (Digital Ocean Managed Kubernetes) v1.19.3
• We have two node pools: infra and clients, with nodes on both labelled as such
• In this case, we would like to avoid deploying to the nodes labelled "infra"

For whatever reason, it seems like no matter what configuration I use, Kubernetes seems to schedule randomly across both node pools.

See configuration below, and the results of scheduling

deployment.yaml snippet

I was trying out my cluster in EKS with managed node group. I am able to attach CSI to the cluster and able to create storageClass and persistentVolumeClaim, but when ever I try to deploy a deployment. The pods seems to be not associating with the specified nodes.

the pod file