What's Rancher v2.1.0 EN

2018.10.18 Rancher Meetup Tokyo #15

Transcript

1. Rancher Meetup Tokyo #15 2018.10.18 © 2018 cyberblack28 WHAT’S RANCHER V2.1.0 ?
2. Profile Twitter:cyberblack28 Hatena Blog:https://cyberblack28.hatenablog.com/ Job Educational Solution Architect Developer Advocate/Technical Evangelist Infrastructure Engineer Frontend Engineer
    Hobby1: Music,Live,FES !! Hobby2: Take a picture !! https://www.flickr.com/photos/cyberblack ISBN-10: 4798155373 ISBN-13: 978-4798155371 I wrote the Chapter 6 Rancher 2.0 part. Release on March 15, 2018 #rancherjp #kujiraya #deepcn
3. AP Communications Co., Ltd
4. Agenda 1. What’s Rancher v2.1.0 2. Windows support revival 3. Information
5. WHAT’S RANCHER V2.1.0
6. What’s Rancher v2.1.0 ? Rancher v2.1.0 introduces new improvements to Kubernetes cluster operations and app management, as well as a migration path for users moving from Rancher’s Cattle orchestrator introduced in 1.x to Rancher Kubernetes. Summary • Latest - v2.1.0 - rancher/rancher:latest • Stable - v2.0.8 - rancher/rancher:stable Version
7. What’s Rancher v2.1.0 ? Webinar October Online Meetup: Migrating from Rancher 1.6 to 2.1 In our October Rancher Meetup, we’ll discuss how to transition various aspects of Rancher 1.6 applications to Rancher 2.0. We’ll look at key terminology differences and parallels, how to implement important elements, and transition from Cattle Compose to YAML specs. Date: Tuesday, October 23rd, 2018 Time: 1:00 PM (US Eastern Time) https://info.rancher.com/2018-10-23-how-to-migrate-from-rancher1- to-rancher2
8. What’s Rancher v2.1.0 ? • Support for project quotas [#13277] - Cluster and project owners can now set quotas on Kubernetes resources at the cluster and project level. • Rancher HA improvements - Administrators can now configure an HA setup with more than one Rancher server. This provides better redundancy and horizontal scalability. • Support for draining nodes [#14265] - Cluster owners can now drain nodes in order to perform maintenance or other disruptive tasks on them. • CI/CD pipeline UX improvements [#14282] - Users will find the CI/CD pipeline more intuitive, easier to use, and with more features. • Support for GitLab in CI pipelines [#12608] - Users can now configure Rancher Pipelines to integrate with GitLab. Details
9. What’s Rancher v2.1.0 ? • Support for Keycloak as an authentication provider [#14730] - Administrators can now configure Keycloak as an authentication provider. • Support for EKS Platform Version 2 [#15487] - Version 2 is now used for all newly created EKS clusters. • Support for editing Helm values.yaml in Rancher catalogs [#13064] [#14844] - User can now achieve a higher degree of customization with Rancher catalog items by directly editing their Helm values.yaml file in the Rancher UI or by uploading a custom values.yaml file. • Created a tool to clean up Rancher installations on Kubernetes Clusters [#13505] - The system-tools utility removes all Rancher installation components installed on a Kubernetes cluster. Details
10. What’s Rancher v2.1.0 ? • EXPERIMENTAL support for Windows Kubernetes clusters - Administrators can now create EXPERIMENTAL Windows Kubernetes clusters. • EXPERIMENTAL support for Kubernetes 1.12 [#15872] - Users can now create EXPERIMENTAL Kubernetes 1.12 clusters. Details
11. WINDOWS SUPPORT REVIVAL
12. Windows support revival rancher-server master Agent Server Control Plane etcd Worker node01 Agent Worker node02 Agent Worker
13. Windows support revival 1. Building Rancher Server 1.Prepare Instance Item Setting Value Name rancher-server Region asia-northeast1
    Tokyo Zone asia-northeast1-b Machine type vCPUx1 Boot disk Ubuntu 16.04 LTS Size(GB) 80GB Firewall Allow HTTP traffic, Allow HTTPS traffic We will use GCP (Google Cloud Platform). The firewall rule assumes full permission. 2.Install Docker $ curl https://releases.rancher.com/install-docker/17.03.2.sh | sh 3.Install Rancher v2.1.0 Server $ sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher
14. Windows support revival 4.Launch the browser and access RancherUI https://EXTERNAL-IP/ Create password for admin user Register Rancher Server URL Login complete 5.First time login setting
15. Windows support revival 2.Construction of Master and Node 1.Prepare Instance We will use GCP (Google Cloud Platform). The firewall rule assumes full permission. Item Setting Value Name master Region asia-northeast1
    Tokyo Zone asia-northeast1-b Machine type vCPUx1 Boot disk Ubuntu 16.04 LTS Size(GB) 80GB Firewall Allow HTTP traffic, Allow HTTPS traffic Item Setting Value Name node01 Region asia-northeast1
    Tokyo Zone asia-northeast1-b Machine type vCPUx1 Boot disk Ubuntu 16.04 LTS Size(GB) 80GB Firewall Allow HTTP traffic, Allow HTTPS traffic
16. Windows support revival 2.Confirm completion of Instance creation 3.Install Docker on master, node 01 $ curl https://releases.rancher.com/install-docker/17.03.2.sh | sh Item Setting Value Name node02 Region asia-northeast1
    Tokyo Zone asia-northeast1-b Machine type vCPUx1 Boot disk Windows Server version 1803 Datacenter Core for Containers Size(GB) 80GB Firewall Allow HTTP traffic, Allow HTTPS traffic
17. Windows support revival 3. Construction of Kubernetes cluster 1.Press "Add Cluster" button
18. Windows support revival 2.Select "Custom", enter an arbitrary name in "Cluster Name", click "Cluster Options" and press the "Next" button 1 2 3
19. Windows support revival 3."Windows Support (Experimental)" is pressed "Enabled" ,"Next" button 4 5
20. Windows support revival 4.Check "Linux" of "Node Operating System", check "etcd" and "Control Plane" of "Node Role", press "Copy to Clipboard" button, execute that command at the master console, Press the button 3 1 2 4 Execute command at master's console
21. Windows support revival 5.After creating the cluster, click the red frame part and select "Edit" 1 2
22. Windows support revival 6.Press the "Copy to Clipboard" button, execute that command at the console of node 01 and press the "Save" button 1 2 Command execution on the console of node 01
23. Windows support revival 7.Confirm that Node has been added
24. Windows support revival 8.Select "Global" from the upper menu 9.Click the red frame part and select "Edit"
25. Windows support revival 10.Select "Windows" in "Node Operating System" and press "Copy to Clipboard" button 1 2
26. Windows support revival 11.For Windows, install Remote Desktop, Chrome's "Chrome RDP for Google Cloud Platform" on Mac. 12. Resetting the RDP password of the node 02 at the GCP side Copy the password to the editor and so on. 3 4 1 2
27. Windows support revival 13.Press "RDP" button 14.Press "RDP" button, after starting Chrome RDP for GCP, enter the password and press "OK" button 1 2
28. Windows support revival 15.Execute the command copied in step 11
29. Windows support revival 16.Press "Save" button
30. Windows support revival 17. Confirm that the number of "Nodes" is 3
31. Windows support revival 18.Select upper menu "Nodes", click "node 02" 1 2
32. Windows support revival 19.Confirm that Windows node is added in "System Information"
33. Windows support revival 20.Select "Cluster" from the upper menu and press the "Launch kubectl" button 1 2
34. Windows support revival 21.Confirm Node status $ kubectl get nodes
35. Windows support revival • Windows node is only Worker node at present. • Network is only Flannel at present. Consideration https://rancher.com/docs//rancher/v2.x/en/cluster-provisioning/rke- clusters/windows-clusters/ Configuring Custom Clusters for Windows (Experimental) Official Docs
36. INFORMATION
37. JAPAN CONTAINER DAYS V18.12 2018.12.04-05 @ sola city Conference Center rancherjp30 deepcn30
38. JAPAN CONTAINER DAYS Training Register 2018.12.03 (Mon) @impress seminar room https://eventregist.com/e/containerdays1812training
39. ! !