master branch. Figure 18. A simple commit history You’ve decided that you’re going to work on issue #53 in whatever issue- tracking system your company uses. To create a new branch and switch to it at command with the - b switch: $ git checkout -b iss53 Switched to a new branch "iss53" This is shorthand for: $ git branch iss53 $ git checkout iss53 Figure 19. Creating a new branch pointer You work moves the iss53 branch forward, because you have it checked out (that is, your HEAD is pointing to it): $ vim index.html $ git commit -a -m 'Create new footer [issue 53]' Figure 20. The iss53 branch has

master branch. Figure 18. A simple commit history You’ve decided that you’re going to work on issue #53 in whatever issue-tracking system your company uses. To create a new branch and switch to it at the command with the -b switch: $ git checkout -b iss53 Switched to a new branch "iss53" This is shorthand for: $ git branch iss53 $ git checkout iss53 Figure 19. Creating a new branch pointer You work moves the iss53 branch forward, because you have it checked out (that is, your HEAD is pointing to it): $ vim index.html $ git commit -a -m 'Create new footer [issue 53]' Figure 20. The iss53 branch has

现在，你已经决定要解决你的公司使用的问题追踪系统中的 #53 问题。 想要 新建一个分支并同时切换到那个分支上，你可以运行一个带有 -b 参数的 git checkout 命令： $ git checkout -b iss53 Switched to a new branch "iss53" 它是下面两条命令的简写： $ git branch iss53 $ git checkout iss53 图表 19. 创建一个新分支指针 创建一个新分支指针 你继续在 #53 问题上工作，并且做了一些提交。 在此过程中，iss53 分支在 不断的向前推进，因为你已经检出到该分支 （也就是说，你的 HEAD 指针指向 了 iss53 分支） $ vim index.html $ git commit -a -m 'added a new footer [issue 53]' 图表 20. iss53 分支随着工作的进展向前推进 现在你接到那个电话，有个紧急问题等待你来解决。 有了 Git 的帮助，你不必 把这个紧急问题和 iss53 的修改混在一起， 你也不需要花大力气来还原关于 53# 问题的修改，然后再添加关于这个紧急问题的修改，最后将这个修改提交 到线上分支。 你所要做的仅仅是切换回 master 分支。 但是，在你这么做之前，要留意你的工作目录和暂存区里那些还没有被提交的 修改， 它可能会和你即将检出的分支产生冲突从而阻止

block like this: kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors health kubernetes cluster.local in-addr.arpa ip6.arpa { pods 2019-07-23T06:05:35Z 0 2 0 m5.large ami- 0923e4b35a30a5f53 eksctl scale nodegroup --cluster test-cluster -n ng-25560078 -N 2 [ℹ] scaling nodegroup stack "e io/docs/tasks/tools/install-kubectl] aws account with permissions: * AmazonEC2FullAccess * AmazonRoute53FullAccess * AmazonS3FullAccess * IAMFullAccess * AmazonVPCFullAccess Installing kops Linux MacOS

block like this: kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors health kubernetes cluster.local in-addr.arpa ip6.arpa { pods io/docs/tasks/tools/install-kubectl/] aws account with permissions: * AmazonEC2FullAccess * AmazonRoute53FullAccess * AmazonS3FullAccess * IAMFullAccess * AmazonVPCFullAccess Installing kops Linux MacOS ss --group-name kops aws iam attach-group-policy --policy-arn arn:aws:iam::aws:policy/AmazonRoute53FullAccess --group-name kops aws iam attach-group-policy --policy-arn arn:aws:iam::aws:policy/AmazonS3FullAccess

like this: kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors health kubernetes cluster.local in-addr.arpa ip6.arpa { like this: kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors health kubernetes cluster.local in-addr.arpa ip6.arpa { io/docs/tasks/tools/install-kubectl] aws account with permissions: * AmazonEC2FullAccess * AmazonRoute53FullAccess * AmazonS3FullAccess * IAMFullAccess * AmazonVPCFullAccess Installing kops Linux MacOS

block like this: kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors health kubernetes cluster.local in-addr.arpa ip6.arpa { pods 2019-07-23T06:05:35Z 0 2 0 m5.large ami- 0923e4b35a30a5f53 eksctl scale nodegroup --cluster eni-cluster -n ng-25560078 -N 2 [ℹ] scaling nodegroup stack "ek io/docs/tasks/tools/install-kubectl] aws account with permissions: * AmazonEC2FullAccess * AmazonRoute53FullAccess * AmazonS3FullAccess * IAMFullAccess * AmazonVPCFullAccess Installing kops Linux MacOS

Kubernetes 1.16+ kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors health kubernetes cluster.local in-addr.arpa ip6.arpa { pods Kubernetes < 1.16 kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors health kubernetes cluster.local in-addr.arpa ip6.arpa { pods io/docs/tasks/tools/install-kubectl/] aws account with permissions: * AmazonEC2FullAccess * AmazonRoute53FullAccess * AmazonS3FullAccess * IAMFullAccess * AmazonVPCFullAccess Installing kops Linux curl

io/docs/tasks/tools/install-kubectl/] aws account with permissions: * AmazonEC2FullAccess * AmazonRoute53FullAccess * AmazonS3FullAccess * IAMFullAccess * AmazonVPCFullAccess Installing kops Linux curl --group-name kops $ aws iam attach-group-policy --policy-arn arn:aws:iam::aws:policy/AmazonRoute53FullAccess --group-name kops $ aws iam attach-group-policy --policy-arn arn:aws:iam::aws:policy/AmazonS3FullAccess 80/TCP 107s service/kubernetes ClusterIP 10.96.0.1 443/TCP 3m53s Each pod will be represented in Cilium as an Endpoint. We can invoke the cilium tool inside the Cilium

io/docs/tasks/tools/install-kubectl/] aws account with permissions: * AmazonEC2FullAccess * AmazonRoute53FullAccess * AmazonS3FullAccess * IAMFullAccess * AmazonVPCFullAccess Installing kops Linux curl --group-name kops $ aws iam attach-group-policy --policy-arn arn:aws:iam::aws:policy/AmazonRoute53FullAccess --group-name kops $ aws iam attach-group-policy --policy-arn arn:aws:iam::aws:policy/AmazonS3FullAccess 80/TCP 107s service/kubernetes ClusterIP 10.96.0.1 443/TCP 3m53s Each pod will be represented in Cilium as an Endpoint. We can invoke the cilium tool inside the Cilium