Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Why not use Rancher?

Why not use Rancher?

53850955f15249a1a9dc49df6113e400?s=128

LINE Developers
PRO

May 25, 2019
Tweet

Transcript

  1. ޷RANCHER ෆ༻䆩ʁ HAZEL 1

  2. • FE -> BE • K8S ROOKIE • CI/CD PROCESS

    IMPROVING SELF-INTRO 2
  3. OUTLINE • WHAT is Rancher • WHY we use rancher

    • HOW does rancher improve our CI/CD • WHO should use rancher • WHEN you may be bitXhed by Rancher 3
  4. WHAT IS RANCHER 4

  5. 5

  6. ARCHITECTURE 6

  7. KUBERNETES PROVIDER 7

  8. HOW DOES RANCHER WORK 8

  9. WHY WE USE RANCHER 9

  10. WHY WE USE RANCHER • Easy to setup • Easy

    to add hosts • Clusters • Catalogs Support 10
  11. EASY TO SETUP Ref: https://rancher.com/docs/rancher/v2.x/en/quick-start-guide/deployment/quickstart-manual-setup/ 11

  12. EASY TO ADD HOSTS Ref: https://rancher.com/docs/rancher/v2.x/en/cluster-provisioning/ 12

  13. CLUSTERS 13

  14. CATALOGS SUPPORT 14

  15. HOW DOES RANCHER IMPROVE OUR CI/CD 15

  16. BACK-END 16

  17. • Put ssh keys, restart script on every hosts •

    Restart all processes on every deployments • Load balancer management • 40 servers on prod stage BACK-END 17
  18. • Docker Swarm on 3 servers • Drone FRONT-END 18

  19. DRONE 19

  20. NOW 20

  21. WHO SHOULD USE RANCHER 21

  22. WHO SHOULD USE RANCHER • SRE • Data Scientist •

    FE developers • BE developers 22
  23. SRE • Prometheus • Grafana • EFK 23

  24. DATA SCIENTISTS • Kubeflow 24

  25. WHEN YOU MAY BE BITCXED BY RANCHER 25

  26. WHEN YOU MAY BE BITCXED BY RANCHER • L4 Load

    Balancer Issues • Application Issues - Argo CI • kubectl 26
  27. L4 LOAD BALANCER ISSUE • Since Rancher2.X, no L4 ingress

    • Nginx • Traefik 27
  28. APPLICATION ISSUE • What you see: • The actual log

    is: 28
  29. ARGO CD APPLICATION ISSUE 29

  30. 30