In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-03-29 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)06/03 Report--
Install EKS cluster
How to install eksctl
# eksctl create cluster-f cluster.yaml apiVersion: eksctl.io/v1alpha5kind: ClusterConfig metadata: name: cluster01 region: ap-northeast-2 vpc: subnets: public: ap-northeast-2a: {id: subnet-dbbb4fb2} ap-northeast-2b: {id: subnet-2b4fa650} ap-northeast-2c: {id: subnet-99182fd3} private: ap-northeast-2a: {id: subnet-dbbb4fb2} ap-northeast-2b : {id: subnet-2b4fa650} ap-northeast-2c: {id: subnet-99182fd3} nodeGroups:-name: ng01 labels: {role: workers} instanceType: t2.xlarge minSize: 2 maxSize: 8 volumeSize: 100 volumeType: gp2 ami: auto amiFamily: Ubuntu1804 # privateNetworking: true ssh: publicKeyName: gexj # publicKeyPath: ~ / .ssh/gexj.pubRecord run result [ℹ] using region ap-northeast-2 [✔] using Existing VPC vpc-1fa75276) and subnets (private: [subnet-2b4fa650 subnet-99182fd3 subnet-dbbb4fb2] public: [subnet-dbbb4fb2 subnet-2b4fa650 subnet-99182fd3]) [!] Custom VPC/subnets will be used If resulting cluster doesn't function as expected, make sure to review the configuration of VPC/subnets [ℹ] nodegroup "ng01" will use "ami-0f37e6cfe5a2e9281" [Ubuntu1804/1.13] [ℹ] using EC2 key pair "gexj" [ℹ] using Kubernetes version 1.13 [ℹ] creating EKS cluster "cluster01" in "ap-northeast-2" region [ℹ] 1 nodegroup (ng01) was included [ℹ] will create a CloudFormation stack for cluster itself and 1 nodegroup stack (s) [ℹ] if you encounter any issues Check CloudFormation console or try 'eksctl utils describe-stacks-- region=ap-northeast-2-- name=cluster01' [ℹ] CloudWatch logging will not be enabled for cluster "cluster01" in "ap-northeast-2" [ℹ] you can enable it with' eksctl utils update-cluster-logging-region=ap-northeast-2-name=cluster01' [ℹ] 2 sequential tasks: {create cluster control plane "cluster01" Create nodegroup "ng01"} [ℹ] building cluster stack "eksctl-cluster01-cluster" [ℹ] deploying stack "eksctl-cluster01-cluster" [ℹ] building nodegroup stack "eksctl-cluster01-nodegroup-ng01" [ℹ] deploying stack "eksctl-cluster01-nodegroup-ng01" [✔] all EKS cluster resource for "cluster01" had been created [✔] saved kubeconfig as "/ root/.kube/config" [ℹ] adding role "arn:aws:iam::647035961056:role/eksctl-cluster01-nodegroup- Ng01-NodeInstanceRole-GDG5Y6EPZ0B8 "to auth ConfigMap [ℹ] nodegroup" ng01 "has 0 node (s) [ℹ] waiting for at least 2 node (s) to become ready in" ng01 "[ℹ] nodegroup" ng01 "has 2 node (s) [ℹ] node" ip-172-31-25-102.ap-northeast-2.compute.internal "is ready [ℹ] node" ip-172-31-9-210.ap-northeast-2.compute.internal "is ready [ℹ] kubectl command should work with" / root/.kube/config " Try 'kubectl get nodes' [✔] EKS cluster "cluster01" in "ap-northeast-2" region is readyAdd IAM Permissions to the roles created above {"Version": "2012-10-17", "Statement": [{"Effect": "Allow", "Action": ["route53:ChangeResourceRecordSets"], "Resource": ["arn:aws:route53:::hostedzone/*"]} {"Effect": "Allow", "Action": ["route53:ListHostedZones", "route53:ListResourceRecordSets"] "Resource": ["*"]} Set up a hosted zone## If you prefer to try-out ExternalDNS in one of the existing hosted-zones you can skip this step # aws route53 create-hosted-zone-- name "gexj.club."-- caller-reference "gexj-clube-$ (date +% s)"
{"Location": "https://10.100.0.1:443"time="2019-09-19T08:06:47Z" level=info msg=" All records are already up to dateapiVersion: v1kind: ServiceAccountmetadata: name: external-dns---apiVersion: rbac.authorization.k8s.io/v1beta1kind: ClusterRolemetadata: name: external-dnsrules:- apiGroups: [""] resources: ["services"] verbs: ["get", "watch" "list"]-apiGroups: [""] resources: ["pods"] verbs: ["get", "watch", "list"]-apiGroups: ["extensions"] resources: ["ingresses"] verbs: ["get", "watch", "list"]-apiGroups: [""] resources: ["nodes"] verbs: ["list" "watch"]-apiVersion: rbac.authorization.k8s.io/v1beta1kind: ClusterRoleBindingmetadata: name: external-dns-viewerroleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: external-dnssubjects:- kind: ServiceAccount name: external-dns namespace: default---apiVersion: extensions/v1beta1kind: Deploymentmetadata: name: external-dnsspec: strategy: type: Recreate template: metadata: labels: app: external-dnsspec: serviceAccountName: external-dns Containers:-name: external-dns image: registry.opensource.zalan.do/teapot/external-dns:latest args:-source=service-source=ingress-domain-filter=gexj.club # will make ExternalDNS see only the hosted zones matching provided domain Omit to process all available hosted zones-provider=aws-policy=upsert-only # would prevent ExternalDNS from deleting any records, omit to enable full synchronization-aws-zone-type=public # only look at public hosted zones (valid values are public Private or no value for both)-registry=txt-txt-owner-id=/hostedzone/Z3P062U2BQWNDS securityContext: fsGroup: 65534 # For ExternalDNS to be able to read Kubernetes and AWS token filesVerify ExternalDNS works (Service example) / / After roughly two minutes check that a corresponding DNS record for your service was created. # aws route53 list-resource-record-sets-output json-hosted-zone-id "/ hostedzone/Z3P062U2BQWNDS"-query "ResourceRecordSets [? Name = = 'nginx.gexj.club.'] | [? Type = =' A']" [{"Name": "nginx.gexj.club.", "Type": "A", "AliasTarget": {"HostedZoneId": "ZWKZPGTI48KDX" DNSName: "ada69bd16dab411e9b32f061aa86c2a6-1959369398.ap-northeast-2.elb.amazonaws.com." ApiVersion: v1kind: Servicemetadata: name: nginx annotations: external-dns.alpha.kubernetes.io/hostname: nginx.gexj.clubspec: type: LoadBalancer ports:-port: 80 name: http targetPort: 80 selector: app: nginx-apiVersion: extensions/v1beta1kind: Deploymentmetadata: name: nginxspec: template: metadata: labels: app: nginxspec: containers :-image: nginx name: nginx ports:-containerPort: 80 name: http
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.