Operations practices have historically lagged behind development. Agile and Extreme Programming have become common practice for development teams. In the last decade, the DevOps and SRE movements have brought these concepts to operations, borrowing heavily from Lean principles such as Kanban and Value Stream Mapping. So, how does all of this play out if we’re using Kubernetes?
In this class, Paul Czarkowski, Principal Technologist at Pivotal, will explain how Kubernetes enables a new cloud-native way of operating software. Attend to learn:
● what cloud-native operations are;
● how to build a cloud-native CI/CD stack; and
● how to deploy and upgrade an application from source to production on Kubernetes.
Presenter:
Paul Czarkowski, Principal Technologist, Pivotal Software
23. Infra
Services
App
Platform
Platform
Team
Application
Team
Build common services
for App Teams
Take business
requirements and turn
them into features
IaaS
Virtual Infrastructure
Physical Infrastructure
Abstract infrastructure
complexity with easy
consumption
DBaaSELK
App2App1 App3
Middleware
ML
Creds/CertsMessaging
???
Container Services
Container Hosts | Kubernetes
Infrastructure
Team
32. Storage NetworkingCompute
Dev / Apps
App User
IT / Ops
> kubectl
Kubernetes Dashboard
Load Balancing / Routing
Container Image
Registry
App Monitoring
App Logging
OS Updates
OS Images
K8S Updates
K8S Images
Log & Monitor
Recover & Restart
Backup & Restore
External
Data Services
Cluster
Provisioning
Provision & Scale
Command Line
/ API
Management
GUI
Monitoring GUI
...but Kubernetes alone is not enough for enterprises
33. Storage NetworkingCompute
Pivotal Container Service (PKS) provides what’s missing
Dev / Apps
App User
IT / Ops
> kubectl
Kubernetes Dashboard
Load Balancing / Routing
Container Image
Registry
OS Updates
OS Images
K8S Updates
K8S Images
Log & Monitor
Recover & Restart
Backup & Restore
External
Data Services
Cluster
Provisioning
Provision & Scale
App Logging
PKS Control Plane
> pks
Operations Manager
vRealize Operations*
*integration
GCP Service Broker
34. Storage NetworkingCompute
Dev / Apps
App User
IT / Ops
> kubectl
Kubernetes Dashboard
Load Balancing / Routing
Container Image
Registry
K8S Updates Log & Monitor Backup & Restore
External
Data Services
Cluster
Provisioning
App Logging
PKS Control Plane
GCP Service Broker
> pks
Operations Manager
vRealize Operations*
*integration
on any Cloud
35. What PKS adds to Kubernetes
PKS
value-added
features
Built into
Kubernetes
Multi-container pods
Stateful Sets of pods
Persistent disks
Single tenant ingress
Pod scaling and high availability
Rolling upgrades to pods
Cluster provisioning and scaling
Embedded, hardened Operating System
Monitoring and recovery of cluster VMs and processes
Rolling upgrades to cluster infrastructure
Secure multi-tenant ingress
Secure container registry
36. PKS Vision
To provide enterprise customers with the ability to
safely and efficiently deliver container services
on their preferred infrastructure so that they can
excel in their market with a cloud native platform
37. PKS does for your Kubernetes
what
Kubernetes does for your apps
38. BOSH
Reliable and consistent operational experience for any cloud.
BOSH
Harbor
NSX-T
Kubernetes
K8s Cluster
K8s Cluster
K8s Cluster
PKS Control Plane
Use the PKS CLI and API to
create, operate, and scale your
clusters.
VMware GCP Azure Openstack AWS
PKSControlPlane
Built with open-source
Kubernetes
Constant compatibility with the
latest stable release of Google
Kubernetes Engine—no
proprietary extensions.
Harbor
An enterprise-class container registry.
Includes vulnerability scanning, identity
management, and more.
NSX-T
Network management, security, and
load balancing out-of-the-box with
VMware NSX-T. Multi-cloud,
multi-hypervisor.
Enterprise-Grade Kubernetes
59. One Big Cluster or Many Smaller Clusters
One [or two] Big Cluster[s]
● All teams co-located on cluster, “namespaces”
separate them.
● Higher chance of noisy neighbor, other
multi-tenancy issues.
● Better utilization of resources (less servers,
higher bin-packing)
● Cluster Upgrades affect everyone.
● Large Blast radius during cluster issues /
outages.
● Monolithic approach to infrastructure
Many Smaller Clusters
● Each “team” or “business unit” gets its own
cluster.
● Dedicated resources to each cluster reduces
noisy neighbor etc.
● Resources can be customized at the cluster for
the specific use cases.
● Cluster Upgrades only affect one team, easier
to coordinate.
● Cluster issues/outages restricted to one team.
● Microservices approach to Infrastructure
60. One Big Cluster or Many Smaller Clusters
One [or two] Big Cluster[s]
● Pivotal Container Service - Essentials
● Kops
● Some Kubernetes distro from another vendor
● Kubespray
● DIY chef/puppet/ansible
Many Smaller Clusters
● Pivotal Container Service - Enterprise
● Pivotal Container Service - Cloud
● Google Container Engine
● Elastic Container Service
● Azure Container Service
75. We’ve spent 10 years figuring
out how to do agile operations
76.
77. Helm Chart
Repo Kube Env
#1 Repo
Kube Env
#2 Repo
A
P
P
A
P
P
A
P
P
A
P
P
Gitl
ab
Con
cou
rse
Spi
nna
ker
A
P
P
A
P
P
A
P
P
A
P
P
Gitl
ab
Con
cou
rse
Spi
nna
ker
Platform Operations