背景
实现了client-go gin的简略整合九-Create的namespace deployment pod的 创立操作，当初进行一下update批改的操作！
update namespace
以某 ns为例减少一个标签
对于namespace，咱们用的最多的标签是name 和labels(恩后面我还做过配额的例子，这里就简略的拿labels为例了)
[zhangpeng@zhangpeng k8s-demo1]$ kubectl get ns --show-labelsNAME STATUS AGE LABELSdefault Active 53d kubernetes.io/metadata.name=defaultkube-node-lease Active 53d kubernetes.io/metadata.name=kube-node-leasekube-public Active 53d kubernetes.io/metadata.name=kube-publickube-system Active 53d kubernetes.io/metadata.name=kube-systemzhangpeng Active 1s kubernetes.io/metadata.name=zhangpengzhangpeng1 Active 3h21m kubernetes.io/metadata.name=zhangpeng1如果去update批改namespace咱们罕用的应该是批改namespace的labels，以zhangpeng namespace为例，我想减少一个name=abcd的标签
/src/service/Namespace.go
package serviceimport ( "context" "fmt" "github.com/gin-gonic/gin" . "k8s-demo1/src/lib" v1 "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "time")type Time struct { time.Time `protobuf:"-"`}type Namespace struct { Name string `json:"name"` CreateTime time.Time `json:"CreateTime"` Status string `json:"status"` Labels map[string]string `json:"labels"` Annotations map[string]string `json:"annotations"`}func ListNamespace(g *gin.Context) { ns, err := K8sClient.CoreV1().Namespaces().List(context.Background(), metav1.ListOptions{}) if err != nil { g.Error(err) return } ret := make([]*Namespace, 0) for _, item := range ns.Items { ret = append(ret, &Namespace{ Name: item.Name, CreateTime: item.CreationTimestamp.Time, Status: string(item.Status.Phase), Labels: item.Labels, }) } g.JSON(200, ret) return}func create(ns Namespace) (*v1.Namespace, error) { ctx := context.Background() newNamespace, err := K8sClient.CoreV1().Namespaces().Create(ctx, &v1.Namespace{ ObjectMeta: metav1.ObjectMeta{ Name: ns.Name, Labels: ns.Labels, }, }, metav1.CreateOptions{}) if err != nil { fmt.Println(err) } return newNamespace, err}func updatenamespace(ns Namespace) (*v1.Namespace, error) { ctx := context.Background() newNamespace, err := K8sClient.CoreV1().Namespaces().Update(ctx, &v1.Namespace{ ObjectMeta: metav1.ObjectMeta{ Name: ns.Name, Labels: ns.Labels, }, }, metav1.UpdateOptions{}) if err != nil { fmt.Println(err) } return newNamespace, err}func CreateNameSpace(g *gin.Context) { var nameSpace Namespace if err := g.ShouldBind(&nameSpace); err != nil { g.JSON(500, err) } namespace, err := create(nameSpace) if err != nil { g.JSON(500, err) } ns := Namespace{ Name: namespace.Name, CreateTime: namespace.CreationTimestamp.Time, Status: string(namespace.Status.Phase), Labels: nil, Annotations: nil, } g.JSON(200, ns)}func UpdateNameSpace(g *gin.Context) { var nameSpace Namespace if err := g.ShouldBind(&nameSpace); err != nil { g.JSON(500, err) } namespace, err := updatenamespace(nameSpace) if err != nil { g.JSON(500, err) } ns := Namespace{ Name: namespace.Name, CreateTime: namespace.CreationTimestamp.Time, Status: string(namespace.Status.Phase), Labels: namespace.Labels, Annotations: nil, } g.JSON(200, ns)}创立updatenamespace办法 UpdateNameSpace service
main.go创立路由：
package mainimport ( "github.com/gin-gonic/gin" "k8s-demo1/src/core" "k8s-demo1/src/service" // "k8s.io/client-go/informers/core")func main() { r := gin.Default() r.GET("/", func(context *gin.Context) { context.JSON(200, "hello") }) r.GET("/namespaces", service.ListNamespace) r.POST("/namespace", service.CreateNameSpace) r.POST("/namespace/update", service.UpdateNameSpace) r.GET("/deployments", service.ListDeployment) r.GET("/service", service.ListService) r.GET("pods", service.ListallPod) r.POST("/pod", service.CreatePod) r.POST("/deployment", service.CreateDep) core.InitDeployment() r.Run()}运行main.go
Postman 测试
post http://127.0.0.1:8080/namespace/update
{"name":"zhangpeng","labels":{"name":"abcd"}}[zhangpeng@zhangpeng k8s-demo1]$ kubectl get ns --show-labels批改name标签为其余值
post http://127.0.0.1:8080/namespace/update
{"name":"zhangpeng","labels":{"name":"abcd123"}}
其余的能够玩的：扩大一下resourcequotas，能够参照这个的搞一下quota的配置，这里就不先演示了呢！
update pod?
pod是否能够update更新呢？
pod是否能够update更新呢？答案是否定的......
注：pod是一个容器的生命周期，实践上是不能够更新的，而且个别的pod 是基于基于deployment or rs等管制治理pod的，批改则意为着生命周期的完结和新的pod的产生，当然了能够基于openkruise的其余的利用实现pod的原地降级！
依着葫芦画瓢，体验一下谬误
[zhangpeng@zhangpeng k8s]$ kubectl get pods -n zhangpengNAME READY STATUS RESTARTS AGEzhangpeng 1/1 Running 0 78m[zhangpeng@zhangpeng k8s-demo1]$ kubectl get pods -o yaml -n zhangpengapiVersion: v1items:- apiVersion: v1 kind: Pod metadata: creationTimestamp: "2022-06-22T02:31:49Z" name: zhangpeng namespace: zhangpeng resourceVersion: "6076576" uid: cee39c9d-fc29-40ee-933e-d9fa76ba20e1 spec: containers: - image: nginx imagePullPolicy: Always name: zhangpeng resources: {} terminationMessagePath: /dev/termination-log terminationMessagePolicy: File volumeMounts: - mountPath: /var/run/secrets/kubernetes.io/serviceaccount name: kube-api-access-f7qvv readOnly: true dnsPolicy: ClusterFirst enableServiceLinks: true nodeName: k8s-2 preemptionPolicy: PreemptLowerPriority priority: 0 restartPolicy: Always schedulerName: default-scheduler securityContext: {} serviceAccount: default serviceAccountName: default terminationGracePeriodSeconds: 30 tolerations: - effect: NoExecute key: node.kubernetes.io/not-ready operator: Exists tolerationSeconds: 300 - effect: NoExecute key: node.kubernetes.io/unreachable operator: Exists tolerationSeconds: 300 volumes: - name: kube-api-access-f7qvv projected: defaultMode: 420 sources: - serviceAccountToken: expirationSeconds: 3607 path: token - configMap: items: - key: ca.crt path: ca.crt name: kube-root-ca.crt - downwardAPI: items: - fieldRef: apiVersion: v1 fieldPath: metadata.namespace path: namespace status: conditions: - lastProbeTime: null lastTransitionTime: "2022-06-22T02:31:49Z" status: "True" type: Initialized - lastProbeTime: null lastTransitionTime: "2022-06-22T02:32:06Z" status: "True" type: Ready - lastProbeTime: null lastTransitionTime: "2022-06-22T02:32:06Z" status: "True" type: ContainersReady - lastProbeTime: null lastTransitionTime: "2022-06-22T02:31:49Z" status: "True" type: PodScheduled containerStatuses: - containerID: docker://47d2c805f72cd023ff9b33d46f63b1b8e7600f64783685fe4c16d97f4b58b290 image: nginx:latest imageID: docker-pullable://nginx@sha256:0d17b565c37bcbd895e9d92315a05c1c3c9a29f762b011a10c54a66cd53c9b31 lastState: {} name: zhangpeng ready: true restartCount: 0 started: true state: running: startedAt: "2022-06-22T02:32:05Z" hostIP: 192.168.0.176 phase: Running podIP: 10.244.1.64 podIPs: - ip: 10.244.1.64 qosClass: BestEffort startTime: "2022-06-22T02:31:49Z"kind: Listmetadata: resourceVersion: ""/src/service/Pod.go
注：模拟deployment create写的......反正后果都是失败的，就走一遍流程看一下！前面都是要删掉的......
func (d *Pod) GetImageName() string { // 全副为应为字母数字和: pods := strings.Index(d.Images, ":") if pods > 0 { return d.Images[:pods] } return d.Images}func updatepod(pod Pod) (*corev1.Pod, error) { newpod, err := K8sClient.CoreV1().Pods(pod.Namespace).Update(context.TODO(), &corev1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: pod.Name, Namespace: pod.Namespace, Labels: pod.Labels, Annotations: pod.Annotations, }, Spec: corev1.PodSpec{ Containers: []corev1.Container{ {Name: pod.Name, Image: pod.Images, Ports: pod.GetPorts()}, }, }, }, metav1.UpdateOptions{}) if err != nil { fmt.Println(err) } return newpod, err}func UpdatePod(g *gin.Context) { var NewPod Pod if err := g.ShouldBind(&NewPod); err != nil { g.JSON(500, err) } pod, err := updatepod(NewPod) if err != nil { g.JSON(500, err) } newpod := Pod{ Namespace: pod.Namespace, Name: pod.Name, Images: pod.Spec.Containers[0].Image, CreateTime: pod.CreationTimestamp.Format("2006-01-02 15:04:05"), Annotations: pod.ObjectMeta.Annotations, } g.JSON(200, newpod)}main.go减少如下配置：
r.POST("/pod/update", service.UpdatePod)运行main.go postman测试：
恩 大略就是这个样子 就为了演示一下，更深刻了解一下pod生命周期，当然了也能够去钻研一下那些原地降级的办法openkruise还是很不错的！
update deployment
初始deployment为下
[zhangpeng@zhangpeng k8s]$ kubectl get pods -n zhangpengNAME READY STATUS RESTARTS AGEzhangpeng-5dffd5664f-nvfsm 1/1 Running 0 27s[zhangpeng@zhangpeng k8s]$ kubectl get deployment zhangpeng -n zhangpengNAME READY UP-TO-DATE AVAILABLE AGEzhangpeng 1/1 1 1 40s[zhangpeng@zhangpeng k8s]$ kubectl get deployment zhangpeng -n zhangpeng -o yamlapiVersion: apps/v1kind: Deploymentmetadata: annotations: deployment.kubernetes.io/revision: "1" creationTimestamp: "2022-06-22T06:44:06Z" generation: 1 name: zhangpeng namespace: zhangpeng resourceVersion: "6096527" uid: d42d5851-2e63-439b-b2a5-976b5fe246bbspec: progressDeadlineSeconds: 600 replicas: 1 revisionHistoryLimit: 10 selector: matchLabels: app: zhangpeng strategy: rollingUpdate: maxSurge: 25% maxUnavailable: 25% type: RollingUpdate template: metadata: creationTimestamp: null labels: app: zhangpeng name: zhangpeng spec: containers: - image: nginx imagePullPolicy: Always name: nginx ports: - containerPort: 80 name: web protocol: TCP resources: {} terminationMessagePath: /dev/termination-log terminationMessagePolicy: File dnsPolicy: ClusterFirst restartPolicy: Always schedulerName: default-scheduler securityContext: {} terminationGracePeriodSeconds: 30status: availableReplicas: 1 conditions: - lastTransitionTime: "2022-06-22T06:44:24Z" lastUpdateTime: "2022-06-22T06:44:24Z" message: Deployment has minimum availability. reason: MinimumReplicasAvailable status: "True" type: Available - lastTransitionTime: "2022-06-22T06:44:06Z" lastUpdateTime: "2022-06-22T06:44:24Z" message: ReplicaSet "zhangpeng-5dffd5664f" has successfully progressed. reason: NewReplicaSetAvailable status: "True" type: Progressing observedGeneration: 1 readyReplicas: 1 replicas: 1 updatedReplicas: 1关键词就是：
{"name":"zhangpeng","namespace":"zhangpeng","replicas":1,"ports":"tcp,80,web","images":"nginx"}编写程序文件
/src/service/Deployment.go
func Updatedep(dep Deployment) (*v1.Deployment, error) { deployment := &v1.Deployment{ ObjectMeta: metav1.ObjectMeta{ Name: dep.Name, Namespace: dep.Namespace, Labels: dep.GetLabels(), }, Spec: v1.DeploymentSpec{ Replicas: &dep.Replicas, Selector: &metav1.LabelSelector{ MatchLabels: dep.GetSelectors(), }, Template: corev1.PodTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ Name: dep.Name, Labels: dep.GetSelectors(), }, Spec: corev1.PodSpec{ Containers: []corev1.Container{ { Name: dep.GetImageName(), Image: dep.Images, Ports: dep.GetPorts(), }, }, }, }, }, } ctx := context.Background() newdep, err := lib.K8sClient.AppsV1().Deployments(dep.Namespace).Update(ctx, deployment, metav1.UpdateOptions{}) if err != nil { fmt.Println(err) } return newdep, nil}func UpdateDep(g *gin.Context) { var newDep Deployment if err := g.ShouldBind(&newDep); err != nil { g.JSON(500, err) } newdep, err := Updatedep(newDep) if err != nil { g.JSON(500, err) } newDep1 := Deployment{ Namespace: newdep.Namespace, Name: newdep.Name, Pods: GetPodsByDep(*newdep), CreateTime: newdep.CreationTimestamp.Format("2006-01-02 15:03:04"), } g.JSON(200, newDep1)}留神：根本就是拿后面的deployment create的办法改的......
减少路由运行main.go
main.go减少路由并运行main.go
r.POST("/deployment/update", service.UpdateDep)Postman测试
批改正本为2
http://127.0.0.1:8080/deployment/update
{"name":"zhangpeng","namespace":"zhangpeng","replicas":2,"ports":"tcp,80,web","images":"nginx"}批改镜像tag
开始想的是批改nginx为nginx:1.18后果失败了......
预计是images数据格式的问题，先疏忽吧......退而求其次批改镜像为apache镜像（留神镜像是httpd）
http://127.0.0.1:8080/deployment/update
{"name":"zhangpeng","namespace":"zhangpeng","replicas":2,"ports":"tcp,80,web","images":"httpd"}登陆服务器验证：
zhangpeng@zhangpeng k8s]$ kubectl get pods -n zhangpengNAME READY STATUS RESTARTS AGEzhangpeng-5546976d9-mkslb 1/1 Running 0 73szhangpeng-5546976d9-tcsb5 0/1 ContainerCreating 0 14szhangpeng-5dffd5664f-nvfsm 1/1 Running 0 18m[zhangpeng@zhangpeng k8s]$ kubectl get pods -n zhangpengNAME READY STATUS RESTARTS AGEzhangpeng-5546976d9-mkslb 1/1 Running 0 100szhangpeng-5546976d9-tcsb5 1/1 Running 0 41s[zhangpeng@zhangpeng k8s]$ kubectl get deployment -n zhangpeng -o yaml |grep image - image: httpd imagePullPolicy: Always总结：
1.Pod生命周期
2.update与create比就批改了update metav1.UpdateOptions{}
3.镜像的tag标签的问题前面看一下怎么解决