Wang's Tech Blog

Updates from August, 2018 Toggle Comment Threads | Keyboard Shortcuts

• 

  Wang 21:56 on 2018-08-22 Permalink | Reply
  Tags: Cloud ( 26 ), Cluster ( 29 ), Docker ( 27 ), Kubernetes ( 37 ), Storage ( 3 )   

  Stateful deployment in kubernetes 

  If you deploy pod by setting “kind: Deployment“, you will lost your data when the pod restart or being deleted.

  It’s not acceptable when we want to deploy storage system like Redis, Elasticsearch, in this case we need use StatefulSet.

  For the concrete explanation please refer to the official documentation, StatefulSet use PVC(Persistent Volume Claim) as storage, and it will exist all the time no matter what happened to the pod.

  You must specify PVC in StatefulSet’s yaml file like this:

  volumeClaimTemplates:
  - metadata:
    name: redis
  spec:
    accessModes: [ "ReadWriteOnce" ]
    storageClassName: fast
    resources:
      requests:
        storage: 10Gi
  

  Please also pay attention to PVC’s name, there’s a rule for StatefulSet and PVC name mapping which IS NOT covered by documentation.

  Like this:

  Like Loading...
   

  Reply Cancel reply

  Name

  Email

  Website

  Notify me of new comments via email.

  Notify me of new posts via email.

  Δ

• 

  Wang 19:25 on 2018-08-11 Permalink | Reply
  Tags: API ( 18 ), Cloud ( 26 ), Cluster ( 29 ), Docker ( 27 ), Kubernetes ( 37 ), Performance ( 28 )   

  Auto scaling in kubernetes 

  When we deploy a API in kubernets we must define replication number for the pod, but as we know there will be high traffic during peak time and we usually can’t estimate service capacity exactly at first time, in this case we must scale our service like creating more pods to share online traffic to avoid service crash down.

  We usually scale service manually before using kubernetes, append more nodes during peak time and destroy nodes when the traffic became smooth.

  In kubernetes there’s a kind of feature called HPA(Horizontal Pod Autoscaler) which could help your scale service automatically. You could specify minimum and maximum replica number in yaml file, HPA will monitor pod’s CPU and Memory by collecting pod’s metric, if HPA found your pod’s metric is over the threshold number which you defined in yaml file, it will create more pods automatically and join the service cluster to load the traffic.

  

  Here is a simple HPA samle:

  apiVersion: autoscaling/v2beta1
  kind: HorizontalPodAutoscaler
  metadata:
    name: hpa-demo
    namespace: test-ns
    labels:
      app: hpa-demo
      component: api
  spec:
    scaleTargetRef:
      apiVersion: apps/v1
      kind: Deployment
      name: hpa-demo
    minReplicas: 3
    maxReplicas: 10
    metrics:
    - type: Resource
      resource:
        name: memory
        targetAverageUtilization: 75
    - type: Resource
      resource:
        name: cpu
        targetAverageUtilization: 75
  

  I defined there’s will be at least 3 replicas for the pod, if the CPU or Memory usage is over 75%, HPA will create at most 10 pods.

  HPA monitor pod’s metric by using metrics-server.

  Like this:

  Like Loading...