1 개요[ | ]
- kops edit instancegroup
- kops edit instancegroups
- kops edit ig
Console
Copy
$ kops get ig
NAME ROLE MACHINETYPE MIN MAX ZONES
master-ap-northeast-2c Master t3.small 1 1 ap-northeast-2c
nodes Node t3.medium 2 2 ap-northeast-2c
Console
Copy
$ kops edit ig nodes
yaml
Copy
apiVersion: kops/v1alpha2
kind: InstanceGroup
metadata:
creationTimestamp: 2019-03-25T06:13:33Z
labels:
kops.k8s.io/cluster: k8s.example.com
name: nodes
spec:
image: kope.io/k8s-1.12-debian-stretch-amd64-hvm-ebs-2019-08-16
machineType: t3.medium
maxSize: 3
minSize: 3
nodeLabels:
kops.k8s.io/instancegroup: nodes
role: Node
subnets:
- ap-northeast-2c
Console
Copy
$ kops get ig
NAME ROLE MACHINETYPE MIN MAX ZONES
master-ap-northeast-2c Master t3.small 1 1 ap-northeast-2c
nodes Node t3.medium 3 3 ap-northeast-2c
Console
Copy
$ kops update cluster
I1007 11:45:57.336470 4930 executor.go:103] Tasks: 0 done / 83 total; 42 can run
I1007 11:45:58.380074 4930 executor.go:103] Tasks: 42 done / 83 total; 23 can run
I1007 11:45:59.005711 4930 executor.go:103] Tasks: 65 done / 83 total; 16 can run
I1007 11:45:59.273060 4930 executor.go:103] Tasks: 81 done / 83 total; 2 can run
I1007 11:45:59.339632 4930 executor.go:103] Tasks: 83 done / 83 total; 0 can run
Will modify resources:
AutoscalingGroup/nodes.k8s.example.com
MaxSize 2 -> 3
MinSize 2 -> 3
Must specify --yes to apply changes
Console
Copy
$ kops update cluster --yes
I1007 11:47:45.995254 4949 executor.go:103] Tasks: 0 done / 83 total; 42 can run
I1007 11:47:46.773387 4949 executor.go:103] Tasks: 42 done / 83 total; 23 can run
I1007 11:47:47.463784 4949 executor.go:103] Tasks: 65 done / 83 total; 16 can run
I1007 11:47:47.736052 4949 executor.go:103] Tasks: 81 done / 83 total; 2 can run
I1007 11:47:47.945388 4949 executor.go:103] Tasks: 83 done / 83 total; 0 can run
I1007 11:47:47.945630 4949 dns.go:153] Pre-creating DNS records
I1007 11:47:48.800378 4949 update_cluster.go:291] Exporting kubecfg for cluster
kops has set your kubectl context to k8s.example.com
Cluster changes have been applied to the cloud.
Changes may require instances to restart: kops rolling-update cluster
Console
Copy
$ kops validate cluster
Validating cluster k8s.example.com
INSTANCE GROUPS
NAME ROLE MACHINETYPE MIN MAX SUBNETS
master-ap-northeast-2c Master t3.small 1 1 ap-northeast-2c
nodes Node t3.medium 3 3 ap-northeast-2c
NODE STATUS
NAME ROLE READY
ip-172-35-79-157.ap-northeast-2.compute.internal master True
ip-172-35-92-13.ap-northeast-2.compute.internal node True
ip-172-35-92-213.ap-northeast-2.compute.internal node True
VALIDATION ERRORS
KIND NAME MESSAGE
Machine i-068024a79135c8e02 machine "i-068024a79135c8e02" has not yet joined cluster
Validation Failed
Console
Copy
$ kops validate cluster
Validating cluster k8s.example.com
INSTANCE GROUPS
NAME ROLE MACHINETYPE MIN MAX SUBNETS
master-ap-northeast-2c Master t3.small 1 1 ap-northeast-2c
nodes Node t3.medium 3 3 ap-northeast-2c
NODE STATUS
NAME ROLE READY
ip-172-35-79-157.ap-northeast-2.compute.internal master True
ip-172-35-92-13.ap-northeast-2.compute.internal node True
ip-172-35-92-213.ap-northeast-2.compute.internal node True
ip-172-35-68-13.ap-northeast-2.compute.internal node True
Your cluster k8s.example.com is ready
Console
Copy
$ kubectl get node
NAME STATUS ROLES AGE VERSION
ip-172-35-79-157.ap-northeast-2.compute.internal Ready master 20d v1.12.10
ip-172-35-92-13.ap-northeast-2.compute.internal Ready node 20d v1.12.10
ip-172-35-92-213.ap-northeast-2.compute.internal Ready node 3d18h v1.12.10
ip-172-35-68-13.ap-northeast-2.compute.internal Ready node 8m36s v1.12.10
2 같이 보기[ | ]
3 참고[ | ]
편집자 Jmnote
로그인하시면 댓글을 쓸 수 있습니다.