Closed dennyabrain closed 5 months ago
I am posting some stats of the current VPC and EC2 dashboard for the ap-south-1 region. This is for my future clean up reference as we bring resources up and down.
successfully brought an managed kubernetes cluster on our aws. Keeping the eks commands handy for later
eksctl create cluster \
--name sandbox \
--version 1.29 \
--region ap-south-1 \
--nodegroup-name generalpurpose \
--node-type t2.micro \
--nodes 2 \
--vpc-public-subnets=subnet-ID1-MAKED,subnet-ID1-MAKED
eksctl delete cluster --region=ap-south-1 --name=sandbox
Untested but you should be able to create new node groups to the cluster using this command
eksctl create nodegroup --cluster=<clusterName> --region=<region> --name=<newNodeGroupName> --managed=false
eksctl manifest file :
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
name: sandbox
region: ap-south-1
version: "1.29"
vpc:
subnets:
public:
ap-south-1a:
id: "subnet-MASKED"
ap-south-1b:
id: "subnet-MASKED"
nodeGroups:
- name: generalpurpose
instanceType: t2.micro
desiredCapacity: 1
- name: c7gxlarge
instanceType: c7g.xlarge
desiredCapacity: 1
labels:
node-class: "c7gxlarge"
ssh:
publicKeyPath: ~/.ssh/id_rsa.pub
- name: c7g4xlarge
instanceType: c7g.4xlarge
desiredCapacity: 1
labels:
node-class: "c7g4xlarge"
ssh:
publicKeyPath: ~/.ssh/id_rsa.pub
k8 manifest file for deployment
apiVersion: apps/v1
kind: Deployment
metadata:
name: feluda-operator-vidvec
labels:
app.kubernetes.io/name: feluda-operator-vidvec
spec:
replicas: 1
selector:
matchLabels:
app.kubernetes.io/name: feluda-operator-vidvec
template:
metadata:
labels:
app.kubernetes.io/name: feluda-operator-vidvec
spec:
nodeSelector:
node-class: "c7gxlarge"
containers:
- name: feluda-operator-vidvec
image: tattletech/feluda-operator-vidvec:b4c4eca
imagePullPolicy: Always
command: ["tails","-f","/dev/null"]
resources:
requests:
cpu: "1000m"
memory: "4000Mi"
limits:
cpu: "4000m"
memory: "8000Mi"
Overview