kubernetes-Namespace入门实战
文章目录
一、 Namespace
Namespace是kubernetes系统中的一种非常重要资源，它的主要作用是用来实现多套环境的资源隔离或者多租户的资源隔离。
默认情况下，kubernetes集群中的所有的Pod都是可以相互访问的。但是在实际中，可能不想让两个Pod之间进行互相的访问，那此时就可以将两个Pod划分到不同的namespace下。kubernetes通过将集群内部的资源分配到不同的Namespace中，可以形成逻辑上的"组"，以方便不同的组的资源进行隔离使用和管理。
可以通过kubernetes的授权机制，将不同的namespace交给不同租户进行管理，这样就实现了多租户的资源隔离。此时还能结合kubernetes的资源配额机制，限定不同租户能占用的资源，例如CPU使用量、内存使用量等等，来实现租户可用资源的管理
kubernetes在集群启动之后，会默认创建几个namespace
查看
[root@master ~]# kubectl get ns
NAME STATUS AGE
default Active 10d
kube-flannel Active 10d
kube-node-lease Active 10d
kube-public Active 10d
kube-system Active 10d
[root@master ~]# kubectl get ns default
NAME STATUS AGE
default Active 10d
[root@master ~]# kubectl get ns default -o yaml
apiVersion: v1
kind: Namespace
metadata:
creationTimestamp: "2022-11-18T02:27:23Z"
labels:
kubernetes.io/metadata.name: default
name: default
resourceVersion: "191"
uid: b03bb5e7-e532-46eb-98b9-351ec6fec5b6
spec:
finalizers:
- kubernetes
status:
phase: Active
[root@master ~]# kubectl describe ns default
Name: default
Labels: kubernetes.io/metadata.name=default
Annotations: <none>
Status: Active
# ResourceQuota 针对namespace做的资源限制# LimitRange针对namespace中的每个组件做的资源限制
No resource quota.
No LimitRange resource.
创建
[root@master ~]# kubectl create ns rww
namespace/rww created
删除
# 删除namespace
[root@master ~]# kubectl delete ns rww
namespace "rww" deleted
二、 Pod
Pod是kubernetes集群进行管理的最小单元，程序要运行必须部署在容器中，而容器必须存在于Pod中。
Pod可以认为是容器的封装，一个Pod中可以存在一个或者多个容器。
kubernetes在集群启动之后，集群中的各个组件也都是以Pod方式运行的。可以通过下面命令查看
[root@master ~]# kubectl get pod -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-c676cc86f-2wz9j 1/1 Running 2 (20m ago) 10d
coredns-c676cc86f-82j79 1/1 Running 2 (20m ago) 10d
etcd-master 1/1 Running 2 (20m ago) 10d
kube-apiserver-master 1/1 Running 2 (20m ago) 10d
kube-controller-manager-master 1/1 Running 3 (20m ago) 10d
kube-proxy-4rzff 1/1 Running 2 (20m ago) 10d
kube-proxy-b79p4 1/1 Running 2 (20m ago) 10d
kube-proxy-pdlj2 1/1 Running 2 (20m ago) 10d
kube-scheduler-master 1/1 Running 3 (20m ago) 10d
创建并运行
kubernetes没有提供单独运行Pod的命令，都是通过Pod控制器来实现的
# 命令格式： kubectl run (pod控制器名称) [参数]
# --image 指定Pod的镜像
# --port 指定端口
# --namespace 指定namespace
[root@master ~]# kubectl run nginx --image=nginx:latest --port=80 --namespace rww
pod/nginx created
查看pod信息
[root@master ~]# kubectl get pods -n rww
NAME READY STATUS RESTARTS AGE
nginx 1/1 Running 0 91s
[root@master ~]# kubectl describe pod nginx -n rww
Name: nginx
Namespace: rww
Priority: 0
Service Account: default
Node: node2/192.168.17.135
Start Time: Mon, 28 Nov 2022 22:42:34 +0800
Labels: run=nginx
Annotations: <none>
Status: Running
IP: 10.122.7.5
IPs:
IP: 10.122.7.5
Containers:
nginx:
Container ID: containerd://59ae4576b88774e2d5eb9d902e59f04bd5c9782e4a8d542b0068ee0d5dfe9a7a
Image: nginx:latest
Image ID: docker.io/library/nginx@sha256:e209ac2f37c70c1e0e9873a5f7231e91dcd83fdf1178d8ed36c2ec09974210ba
Port: 80/TCP
Host Port: 0/TCP
State: Running
Started: Mon, 28 Nov 2022 22:42:37 +0800
Ready: True
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-lk7k4 (ro)
Conditions:
Type Status
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
kube-api-access-lk7k4:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 99s default-scheduler Successfully assigned rww/nginx to node2
Normal Pulling 98s kubelet Pulling image "nginx:latest"
Normal Pulled 95s kubelet Successfully pulled image "nginx:latest" in 2.665589638s
Normal Created 95s kubelet Created container nginx
Normal Started 95s kubelet Started container nginx
访问Pod
[root@master ~]# kubectl get pods -n rww -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
nginx 1/1 Running 0 3m4s 10.122.7.5 node2 <none> <none>
[root@master ~]# curl http://10.122.7.5
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>
<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>
<p><em>Thank you for using nginx.</em></p>
</body>
删除指定Pod
[root@master ~]# kubectl delete pod nginx -n rww
pod "nginx" deleted
# 如果create，显示删除Pod成功，但是再查询，发现又新产生了一个 ；
[root@master ~]# kubectl get pods -n rww
NAME READY STATUS RESTARTS AGE
nginx 0/1 ContainerCreating 0 4m19s
# 这是因为当前Pod是由Pod控制器创建的，控制器会监控Pod状况，一旦发现Pod死亡，会立即重建# 此时要想删除Pod，必须删除Pod控制器
# 先来查询一下当前namespace下的Pod控制器
[root@master ~]# kubectl get deploy -n rww
No resources found in rww namespace.
[root@master ~]# kubectl create deployment nginx --image=nginx:1.17.1 -n rww
deployment.apps/nginx created
[root@master ~]# kubectl get deploy -n rww
NAME READY UP-TO-DATE AVAILABLE AGE
nginx 0/1 1 0 49s
# 接下来，删除此PodPod控制器
[root@master ~]# kubectl delete deploy nginx -n rww
deployment.apps "nginx" deleted
配置操作
创建一个pod-nginx.yaml
[root@master ~]# vim www-nginx.yaml
apiVersion: v1
kind: Pod
metadata:
name: nginx
namespace: gbj
spec:
containers:
- image: nginx:latest
name: pod
ports:
- name: nginx-port
containerPort: 80
protocol: TCP
[root@master ~]# kubectl create -f www-nginx.yaml
pod/nginx created
创建：kubectl create -f pod-nginx.yaml
删除：kubectl delete -f pod-nginx.yaml
三、 Label
Label是kubernetes系统中的一个重要概念。它的作用就是在资源上添加标识，用来对它们进行区分和选择。
Label的特点：
一个Label会以key/value键值对的形式附加到各种对象上，如Node、Pod、Service等等
一个资源对象可以定义任意数量的Label ，同一个Label也可以被添加到任意数量的资源对象上去
Label通常在资源对象定义时确定，当然也可以在对象创建后动态添加或者删除
可以通过Label实现资源的多维度分组，以便灵活、方便地进行资源分配、调度、配置、部署等管理工作。
一些常用的Label 示例如下：
版本标签：“version”:“release”, “version”:“stable”…
环境标签：“environment”:“dev”，“environment”:“test”，“environment”:“pro”
架构标签：“tier”:“frontend”，“tier”:“backend”
标签定义完毕之后，还要考虑到标签的选择，这就要使用到Label Selector，即：
Label用于给某个资源对象定义标识
Label Selector用于查询和筛选拥有某些标签的资源对象
当前有两种Label Selector：
基于等式的Label Selector
name = slave: 选择所有包含Label中key="name"且value="slave"的对象
env != production: 选择所有包括Label中的key="env"且value不等于"production"的对象
基于集合的Label Selector
name in (master, slave): 选择所有包含Label中的key="name"且value="master"或"slave"的对象
name not in (frontend): 选择所有包含Label中的key=“name"且value不等于"frontend"的对象
标签的选择条件可以使用多个，此时将多个Label Selector进行组合，使用逗号”,"进行分隔即可
命令方式
# 为pod资源打标
[root@master ~]# kubectl label pod nginx version=1.0 -n gbj
pod/nginx labeled
# 为pod资源更新标签
[root@master ~]# kubectl label pod nginx version=2.0 -n gbj --overwrite
pod/nginx labeled
# 查看标签
[root@master ~]# kubectl get pod nginx -n gbj --show-labels
NAME READY STATUS RESTARTS AGE LABELS
nginx 1/1 Running 0 21m version=2.0
# 筛选标签
[root@master ~]# kubectl get pod -n gbj -l version=2.0 --show-labels
NAME READY STATUS RESTARTS AGE LABELS
nginx 1/1 Running 0 22m version=2.0
#删除标签
[root@master ~]# kubectl label pod nginx version- -n gbj
pod/nginx unlabeled
配置方式
[root@master ~]# vim pod-nginx.yaml
apiVersion: v1
kind: Pod
metadata:
name: nginx
namespace: gbj
labels:
version: "3.0"
env: "test"
spec:
containers:
- image: nginx:latest
name: pod
ports:
- name: nginx-port
containerPort: 80
protocol: TCP
~
然后执行对应的更新命令：kubectl apply -f pod-nginx.yaml
[root@master ~]# kubectl apply -f pod-nginx.yaml
Warning: resource pods/nginx is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create --save-config or kubectl apply. The missing annotation will be patched automatically.
pod/nginx configured
四、 Deployment
在kubernetes中，Pod是最小的控制单元，但是kubernetes很少直接控制Pod，一般都是通过Pod控制器来完成的。Pod控制器用于pod的管理，确保pod资源符合预期的状态，当pod的资源出现故障时，会尝试进行重启或重建pod。
在kubernetes中Pod控制器的种类有很多，本章节只介绍一种：Deployment
命令操作
[root@master ~]# kubectl create deploy nginx --image=nginx:latest --port=80 --replicas=3 -n ren
deployment.apps/nginx created
# 查看创建的Pod
[root@master ~]# kubectl get pods -n ren
NAME READY STATUS RESTARTS AGE
nginx-j8o9c47f5-8jk8c 1/1 Running 0 37s
nginx-j8o9c47f5-fp697 1/1 Running 0 37s
nginx-j8o9c47f5-rhjvb 1/1 Running 0 37s
# 查看deployment的信息
[root@master ~]# kubectl get deploy -n ren
NAME READY UP-TO-DATE AVAILABLE AGE
nginx 3/3 3 3 70s
# UP-TO-DATE：成功升级的副本数量
# AVAILABLE：可用副本的数量
[root@master ~]# kubectl get deploy -n ren -o wide
NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR
nginx 3/3 3 3 107s nginx nginx:latest app=nginx
# 查看deployment的详细信息
[root@master ~]# kubectl describe deploy nginx -n ren
Name: nginx
Namespace: guan
CreationTimestamp: Mon, 28 Nov 2022 15:26:13 +0800
Labels: app=nginx
Annotations: deployment.kubernetes.io/revision: 1
Selector: app=nginx
Replicas: 3 desired | 3 updated | 3 total | 3 available | 0 unavailable
StrategyType: RollingUpdate
MinReadySeconds: 0
RollingUpdateStrategy: 25% max unavailable, 25% max surge
Pod Template:
Labels: app=nginx
Containers:
nginx:
Image: nginx:latest
Port: 80/TCP
Host Port: 0/TCP
Environment: <none>
Mounts: <none>
Volumes: <none>
Conditions:
Type Status Reason
---- ------ ------
Available True MinimumReplicasAvailable
Progressing True NewReplicaSetAvailable
OldReplicaSets: <none>
NewReplicaSet: nginx-j8o9c47f5 (3/3 replicas created)
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal ScalingReplicaSet 2m18s deployment-controller Scaled up replica set nginx-cd55c47f5 to 3
# 删除
[root@master ~]# kubectl delete deploy nginx -n gbj
deployment.apps "nginx" deleted
配置操作
创建一个deploy-nginx.yaml
[root@master ~]# vim deploy-nginx.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx
namespace: guan
spec:
replicas: 3
selector:
matchLabels:
run: nginx
template:
metadata:
labels:
run: nginx
spec:
containers:
- image: nginx:latest
name: nginx
ports:
- containerPort: 80
protocol: TCP
[root@master ~]# kubectl delete -f deploy-nginx.yaml
deployment.apps "nginx" deleted
创建：kubectl create -f deploy-nginx.yaml
删除：kubectl delete -f deploy-nginx.yaml
扫一扫
1777
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
