Skip to content

Latest commit

 

History

History
192 lines (162 loc) · 5.3 KB

yurt-app-manager.md

File metadata and controls

192 lines (162 loc) · 5.3 KB
Raw

Use yurt-app-manager to manage edge nodes and workloads

In this tutorial, we will show how the yurt-app-manager helps users manage there edge nodes and workload. Suppose you have a Kubernetes cluster in an Openyurt environment, or a native Kubernetes cluster with at least two nodes.

Install yurt-app-manager

1. install yurt-app-manager operator

Go to OpenYurt root directory:

$ cd $GOPATH/src/github.com/openyurtio/openyurt
kubectl apply -f config/yurt-app-manager/release/yurt-app-manager-v0.3.0.yaml

Wait for the yurt-app-manager operator to be created successfully

kubectl get pod -n kube-system |grep yurt-app-manager

How to Use

The Examples of NodePool and UnitedDeployment are in config/yurt-app-manager/samples/ directory

NodePool

  • 1 create an nodepool
cat <<EOF | kubectl apply -f -
apiVersion: apps.openyurt.io/v1alpha1
kind: NodePool
metadata:
  name: Pool-A
spec:
  type: Edge
  annotations:
    apps.openyurt.io/example: test-Pool-A
  labels:
    apps.openyurt.io/example: test-Pool-A
  taints:
  - key: apps.openyurt.io/example
    value: test-Pool-A
    effect: NoSchedule
EOF
  • 2 Get NodePool
$ kubectl get np Pool-A

NAME       TYPE   READYNODES   NOTREADYNODES   AGE
Pool-A     Edge                                28s
  • 3 Add Node To NodePool

Add an node into Pool-A NodePool, Set the apps.openyurt.io/desired-nodepool label on the host, and value is the name of the Pool-A NodePool

$ kubectl label node {Your_Node_Name} apps.openyurt.io/desired-nodepool=Pool-A

{Your_Node_Name} labeled
$ kubectl get np Pool-A
NAME       TYPE   READYNODES   NOTREADYNODES   AGE
Pool-A     Edge   1            0               5m19s

Once a Node adds a NodePool, it inherits the annotations, labels, and taints defined in the nodepool Spec,at the same time, the Node will add a new tag: apps.openyurt.io/nodepool. For Example:

$ kubectl get node {Your_Node_Name} -o yaml

apiVersion: v1
kind: Node
metadata:
  annotations:
    apps.openyurt.io/example: test-Pool-A
  labels:
    apps.openyurt.io/desired-nodepool: Pool-A
    apps.openyurt.io/example: test-Pool-A
    apps.openyurt.io/nodepool: Pool-A
spec:
  taints:
  - effect: NoSchedule
    key: apps.openyurt.io/example
    value: test-Pool-A
status:
***

UnitedDeployment

  • 1 create an uniteddeployment which use deployment template
cat <<EOF | kubectl apply -f -
apiVersion: apps.openyurt.io/v1alpha1
kind: UnitedDeployment
metadata:
  labels:
    controller-tools.k8s.io: "1.0"
  name: ud-test
spec:
  selector:
    matchLabels:
      app: ud-test
  workloadTemplate:
    deploymentTemplate:
      metadata:
        labels:
          app: ud-test
      spec:
        template:
          metadata:
            labels:
              app: ud-test
          spec:
            containers:
              - name: nginx
                image: nginx:1.19.1
  topology:
    pools:
    - name: edge
      nodeSelectorTerm:
        matchExpressions:
        - key: apps.openyurt.io/nodepool
          operator: In
          values:
          - Pool-A
      replicas: 3
      tolerations:
      - effect: NoSchedule
        key: apps.openyurt.io/example
        operator: Exists
  revisionHistoryLimit: 5
EOF
  • 2 Get UnitedDeployment
$ kubectl get ud
NAME      READY   WORKLOADTEMPLATE   AGE
ud-test   1       Deployment         23s

check the sub deployment created by yurt-app-manager controller

$ kubectl get deploy
NAME                 READY   UP-TO-DATE   AVAILABLE   AGE
ud-test-edge-ttthd   1/1     1            1           100s

check the pod created by UnitedeDeployment , and you will find that these pods will be created on all the hosts under the Pool-A NodePool, and all the pods created by UnitedDeployment use the same image: nginx:1.19.1

$ kubectl get pod -l app=ud-test

NAME                                  READY   STATUS    RESTARTS   AGE
ud-test-edge-ttthd-5db8f454dd-8jd4l   1/1     Running   0          7m
ud-test-edge-ttthd-5db8f454dd-ggmfb   1/1     Running   0          34s
ud-test-edge-ttthd-5db8f454dd-r6ptr   1/1     Running   0          34s
  • 3 Change UnitedDeployment workloadTemplate's image change image from nginx:1.19.1 to nginx:1.19.3, and you will find that all pods created by UnitedDeployment use the same image:nginx:1.19.3
kubectl patch ud ud-test --type='json' -p '[{"op": "replace", "path": "/spec/workloadTemplate/deploymentTemplate/spec/template/spec/containers/0/image", "value": "nginx:1.19.3"}]'
kubectl get pod -l app=ud-test
  • 4 Scale the number of pods under a node pool
$ kubectl patch ud ud-test --type='json' -p '[{"op": "replace", "path": "/spec/topology/pools/0/replicas", "value": 6}]'

You will find that the number of pods will be expanded to six

$ kubectl get pod -l app=ud-test
NAME                                  READY   STATUS    RESTARTS   AGE
ud-test-edge-ttthd-5bbb4b8664-2f5ss   1/1     Running   0          10m
ud-test-edge-ttthd-5bbb4b8664-8sjs7   1/1     Running   0          3m20s
ud-test-edge-ttthd-5bbb4b8664-99dml   1/1     Running   0          10m
ud-test-edge-ttthd-5bbb4b8664-dvb8s   1/1     Running   0          10m
ud-test-edge-ttthd-5bbb4b8664-lxhgr   1/1     Running   0          3m20s
ud-test-edge-ttthd-5bbb4b8664-zj8ls   1/1     Running   0          3m20s