A set of flexible and comprehensive operation principles to cover all stages of a modern application life cycle.
Almost any Customer wants the Setup to be compatible with existing infrastructure. It assumes a Bare Metal, Private or Public Cloud. In special cases even offline setup, for example, Airports, Fintech sector or Telecom operators. The main requirements are: Scalability, High Availability, Security Compliance, Professional Service.
So, we should cover all three tiers: Infrastructure, Control Plane and Application Plane. Market leaders are Drone, Argo and Knative. And our story we called Cloud Flex Framework.
2. About Me
10+ years in Telecom industry: network
engineer, technical manager, operation
team and unit lead, CTO.
IP transit operators, Internet Providers and
Mobile Network Operators:
Beeline, Kyivstar, MTS , Velcom, Mobicom,
Azerfon, Azercell, lifecell
msrn.me
2 Startups: manager positions and system
architect/software engineer role.
5 years as Co-Founder cloud b2b/b2c web
application project: VoIP Roaming Solution.
Today: software engineer in Cloud Media
project for Globallogic
denys
vasyliev
3
linkedin.com/in/denis-vasyliev
9. ● 8: The numbers of characters between the “K”
and the “S” in Kubernetes, leading to the
developer shorthand, K8s.
● 388,100: The number of comments on the
Kubernetes repository on GitHub during the past
year
● 680: The number of reviews the Kubernetes
repository has received on GitHub
● 6525: Kubernetes’ “Krihelimeter” - fourth
overall among GitHub repositories.
● 28,519: The number of stars the Kubernetes
repository has received to date.
● 60%: The percentage of respondents reporting
broad container usage in production
● $2.7 billion: The expected overall market for
containers in 2020
● 3: Kubernetes’ age, in years; version 1.0 was
released on July 21, 2015.
● 47%: users currently deploying container
orchestration on top of OpenStack using
Kubernetes
Kubernetes by numbers
10
https://goo.gl/STPM5u
https://goo.gl/WcSHRj
11. ● Official top-level CNCF project
● Think of it like apt/yum/homebrew for Kubernetes
● Charts are packages of Kubernetes resources
● Two parts: a client (helm) and a server (tiller)
● Tiller runs inside of your Kubernetes cluster
● Tiller manages releases (installations) of your charts
● Helm Runs on laptop, CI/CD, or wherever you want
● Charts are packages that contain at least two things:
○ A description of the package (Chart.yaml)
○ Templates, which contain manifest files
Declarative Deployment
12
https://www.helm.sh
12. API Gateway
● Kubernetes-native API Gateway
● Self-service configuration
● First class gRPC and HTTP/2 support
● CORS, timeouts, weighted round robin
● Istio integration
● Authentication
● Robust TLS support
● Open Source project
https://www.getambassador.io
https://www.envoyproxy.io
13. Service Mesh
● Traffic Management. Control the flow of traffic and API
calls between services
● Service Identity and Security. Provide the ability to
protect service traffic as it flows
● Policy Enforcement. Policy between services
● Telemetry. Gain understanding of the dependencies
between services and the nature and flow of traffic
between them
https://istio.io
17. ● Natural Language Processing
● Domain Knowledge Base
● AI Powered Algorithms
● Machine Learning Analyze
● Platform & Devices Support
○ Google Assistance
○ Slack & Fb Messenger
○ AWS Alexa & Cortana
● Infrastructure Management
● Deployments & Services
● Monitoring and Alerting
● Environment Rollouts
VoxControl
alpha
19
18. 20
● Configuration of applications and their
deployment environments should be
declarative and version controlled.
● Application deployment and lifecycle
management should be simple, automated, and
auditable.
● Application deployments should be fast,
reliable, and idempotent.
● Any deviation from the version controlled
configuration should be immediately detected
and remediated.
● Rollbacks should be as simple as deploying a
different configuration.
https://blog.argoproj.io
Argo
19. 21
● Deploying a container
● Orchestrating source-to-URL workflows on
Kubernetes
● Routing and managing traffic with
blue/green deployment
● Automatic scaling and sizing workloads
based on demand
● Binding running services to eventing
ecosystems
● Build - Source-to-container build orchestration
● Eventing - Management and delivery of events
● Serving - Request-driven compute scale to zero
https://cloud.google.com/knative
Knative