Introduction to Rancher and using it to create Kubernetes as a service

1. © 2018 Nokia1
K8s as a service with
Rancher
Michał Wcisło
12-02-2019

2. © 2018 Nokia2
Goals
• What is Rancher ?
• How Rancher can be used for k8s deployment ?
• How Rancher leverages kubernetes functionality ?

3. © 2018 Nokia3
Few words about me
• 8 years in Nokia
• Worked in telco reasearch (VoIP, MIMO), QA, Technical Support and Development
• Currently developing Nokia AVA platform as part of Analytics Engine

4. © 2018 Nokia4
Nokia Poland
• Sites in Warsaw, Wrocław, Kraków and
Bydgoszcz
• Smart City, 5G evaluation
• code::dive, test dive, Nokia Garage
• ~4500 employees in Wrocław
• Wrocław: BTS SW, OSS, MANO, AE

5. © 2018 Nokia55 © Nokia 2017
Why Nokia needs Analytics Engine?
• 1865 started as a pulp (paper) mill
….
• 1979-1984 established first fully automated cellular phone system (1G) with comercially available phones
• 1991 first 2G call with Nokia 1011
• 2000 ;)
• 1998 – … 3GPP, LTE, 5G

6. © 2018 Nokia6
Nokia Analytics Engine ecosystem

7. © 2018 Nokia7
Kubernetes as a service
• Separate cluster per each project
• Better granularity
• Separate openstack account
• Separate CEPH account
• …
• Security
• Cluster failure mitigation

8. © 2018 Nokia8
K8s as a service - assumptions
Access
Ingress
Network
cluster networking (flannel, calico, etc.)
Network security
Deployment
K8s deployment
Orchestrator deployment (multiple clusters)
Apps
Deployment/Helm
Scaling
Service discovery
Catalog
Security
Users/RBAC
LDAP integration
Namespaces – workspace separation
Monitoring
FM orchestrator
FM on k8s
Logs orchestrator
Volumes/storage
Backup/restore
Backup/restore of orchestrator

9. © 2018 Nokia9
How to deploy k8s?
Gardener
Kubermatic by
kubeadm

10. © 2018 Nokia10
Why Rancher?
• More than k8s deployment tool
• More than vanilla k8s
• Cheaper - open source
• Big community, great materials, regular online meetups - https://rancher.com/

11. © 2018 Nokia11
What is Rancher?
Access
Ingress
Network
cluster networking (flannel, calico, etc.)
Network security
Deployment
K8s deployment
Orchestrator deployment (multiple clusters)
Apps
Deployment/Helm
Scaling
Service discovery
Catalog
Security
Users/RBAC
LDAP integration
Namespaces – workspace separation
Monitoring
FM orchestrator
FM on k8s
Logs orchestrator
Volumes/storage
Backup/restore
Backup/restore of orchestrator

12. © 2018 Nokia12
Rancher working as a proxy – big picture
Core kubernetes
Customer
kubernetes
Node 1 (192.168.X.X)
Node 2 (192.168.X.X)
Node 3 (192.168.X.X)
Customer
kubernetes
Node 1 (192.168.X.X)
Node 2 (192.168.X.X)
Node 3 (192.168.X.X)
Customer
kubernetes
Node 1 (192.168.X.X)
Node 2 (192.168.X.X)
Node 3 (192.168.X.X)Ingress
(10.X.X.X)
LBaaS

13. © 2018 Nokia13
DEMO
• Cluster discovery, local cluster, REST API
• Manual deployment, Rundeck
• Basic operations on local cluster (kubectl, kubeconfig copy, nodes, scale nodes)
• Members and permissions, RBACs, integration with keycloak
• Project/namespaces, quota, how to create different workspaces for different groups of
users (dev, users, etc)
• Rancher CLI, Catalogue, how apps are viewed in Rancher
• Alerts, Notifiers, Logging (EFK)

14. © 2018 Nokia14
Things to consider using rancher
• Single point of failure (possibly addressed in 2.2)
• No federation
• Not fully reflecting cloud providers features (i.e. openstack affinity rules)
• Cost of support