From a skunk-works project to running the entire enterprise While developers see and realize the benefits of Kubernetes, how it improves efficiencies, saves time, and enables focus on the unique business requirements of each project; InfoSec, infrastructure, and software operations teams still face challenges when managing a new set of tools and technologies, and integrating them into an existing enterprise infrastructure. In this meetup, Chris, CTO at Tigera, and Oleg, CTO at Kublr, discussed the evolution of your Kubernetes cluster - from a skunk-works project to running the entire enterprise.

1. The Evolution of Your Kubernetes Cluster
From a Skunk-Works Project to Running the Entire Enterprise
Oleg Chunikhin | CTO, Kublr

2. Introductions
Oleg Chunikhin
CTO, Kublr
• 20 years in software architecture & development
• Working w/ Kubernetes since its release in 2015
• Software architect behind Kublr—an enterprise
ready container management platform
• Twitter @olgch

3. History
• Custom software development company
• Dozens of projects per year
• Varying target environments: clouds, on-prem,
hybrid
• Recurring need for unified application delivery
and ops platform w/ monitoring, logs, security,
multiple env, ...
@olgch; @kublr

4. Docker and Kubernetes to the Rescue
• Docker is great, but local
• Kubernetes is great... when it is up and running
• Who sets up and operates K8S clusters?
• Who takes care of operational aspects at scale?
• How do you provide governance and ensure
compliance?
@olgch; @kublr

5. Enterprise Kubernetes Needs
Developers SRE/Ops/DevOps/SecOps
• Self-service
• Compatible
• Conformant
• Configurable
• Open & Flexible
• Governance
• Org multi-tenancy
• Single pane of glass
• Operations
• Monitoring
• Log collection
• Image management
• Identity management
• Security
• Reliability
• Performance
• Portability
@olgch; @kublr

6. Kubernetes Management Platform Wanted
• Portability – clouds, on-prem, hybrid, air-gapped, different OS’
• Centralized multi-cluster operations saves resources – many
environments (dev, prod, QA, ...), teams, applications
• Self-service and governance for Kubernetes operations
• Reliability – cluster self-healing, self-reliance
• Limited management profile – cloud and K8S API
• Architecture – flexible, open, pluggable, compatible
• Sturdy – secure, scalable, modular, HA, DR etc.
@olgch; @kublr

7. @olgch; @kublr
Automation
Ingress
Custom
Clusters
Infrastructure
Logging Monitoring
Observability
API
Usage
Reporting
RBAC IAM
Air Gap TLS
Certificate
Rotation
Audit
Storage Networking Container
Registry
CI / CD App Mgmt
Infrastructure
Container Runtime Kubernetes
OPERATIONS SECURITY &
GOVERNANCE

8. Central Control Plane: Operations
K8S Clusters
Cloud(s)
Data
center
API UI
Log collection
Operations
Monitoring
Authn and authz, SSO, federation
Audit Image Repo
Infrastructure management
Backup & DR
Dev
K8S API
Cloud API
Prod
PoC
Dev
@olgch; @kublr

9. Central Control Plane: Operations
@olgch; @kublr

10. Talking Points
Self-service and Governance
• Resource quotas and limits
Deployment and Day 2 Ops
• Infrastructure, portability
• Storage/data, image mgmt, CI/CD
Visibility/Observability
• Asset visibility and ownership
• Log collection/monitoring/tracing
• Network & flow logging (IP
ephemerality)
Security and AAA
• IaM
• RBAC and Network Policy
• Container scanning, signing, governance
• Underlying OS and updates
• Underlying platform security (e.g.
SElinux)
Legacy & Enterprise integration
• RBAC, IaM
• Legacy network enforcement integration
@olgch; @kublr

11. Q&A
@olgch; @kublr

12. Oleg Chunikhin
Chief Technology Officer
oleg@kublr.com
@olgch
Kublr | kublr.com
@kublr
Signup for our newsletter
at kublr.com
@olgch; @kublr