Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Ondat <> Komodor Webinar

Komodor
April 24, 2022

Ondat <> Komodor Webinar

Kubernetes is eating the world...at least the world of modern software engineering. Besides their applications, most businesses consider their data as the holy grail. It is key to the value they deliver. As they progress through application modernization, Kubernetes is the natural foundation to support their effort. But where should the data go? Is Kubernetes safe enough to take care of it? How to prepare for DB-related incidents in an ever-changing environment?

Learn the key tenets of data storage with troubleshooting in mind, and how to avoid the common pitfalls when migrating databases to Kubernetes, without compromising on availability, security, performance, and visibility.

Komodor

April 24, 2022
Tweet

More Decks by Komodor

Other Decks in Technology

Transcript

  1. 5 Tips to Successfully Migrate your Database to Kubernetes Guy

    Menahem, Solution Engineer @Komodor Nic Vermandé, Principal Developer Advocate @Ondat
  2. Agenda Your Speakers: What to expect today: • A bit

    of history & predictions • Kubernetes Patterns for stateful apps • Special considerations for databases • Demos Guy Menahem, Solution Engineer Komodor Nic Vermandé, Principal Dev Advocate Ondat
  3. Cloud Databases on the Rise MQ Cloud Database Management Systems:

    • By 2022, 75% of all databases will be deployed or migrated to a cloud platform, with only 5% ever considered for repatriation to on-premises. • By 2023, cloud preference for data management will reduce the vendor landscape while the growth in multicloud increases the complexity for data governance and integration. • By 2023, cloud DBMS revenue will account for 50% of the total DBMS market revenue. BTW We’re a 2021 Gartner Cool Vendor!
  4. K8s Troubleshooting Today Understand who changed what Check the CI

    pipeline Check pods status Check the CI pipeline Check current alert Explore relevant exceptions Review alert’s metrics Check account activity Review the latest code changes
  5. K8s Troubleshooting Today Too often, it devolves into A process

    of elimination, Driven by more guesswork Than insight.
  6. Collect cross systems events Provide a complete overview of all

    services and their relations in a single place For each service, we build a comprehensive timeline: deploys, config changes, alerts and more How Does Komodor Work?
  7. Troubleshoot Statefulsets With Pod Logs Komodor’s Pod Logs & Events

    feature offers quick access to all of the pod-level data you`ll need for troubleshooting, including: • Overview of all pods running the service • Pod details, similar to what you would get with kubectl describe • Live view of all events • Pod containers’ logs
  8. Tip 1 - K8s Patterns for your Platform - Use

    Kubernetes StatefulSets to deploy your Database - Use a Database Operator to tune your Database deployment configuration
  9. Tip 1 - K8s Patterns for your App - In

    your application, make sure to leverage the right mechanisms to make it platform-aware: - Downward API - Environment Variables - Volumes Container A Env_A1 Env_A2 Container B K8S API call /etc/annotations /etc/labels Volume A Pod API Server Pod Configuration + Runtime Information Inject Query Mount Source: Ibryam B., and Huß R., 2019, Kubernetes Patterns, O’Reilly Media Inc., Sebastopol
  10. Tip 2: Compare Costs - EBS or other cloud persistent

    disks are expensive as performance requirements increase - PaaS solutions add another proprietary abstraction layer and leads to vendor lock-in
  11. Tip 3: Shift Left with GitOps Principles • What is

    Shift Left? • What is GitOps? • Why do you need to adopt these paradigms? "Bring application components and infrastructure dependencies early in the DevOps process and SDLC to detect and fix issues before deploying the artifact"
  12. Tip 3: Shift Left with GitOps Principles • Save on

    operational costs and time-to-deploy • Agility, nimbler to move • Reliable, Higher Quality Software • Anything “as-a-Service” • Improve Security and Compliance • Policy-as-Code Why do you need to adopt these paradigms?
  13. • Add visibility (Performance, I/O, Backups, etc.) • Make sure

    you got the right troubleshooting tools • Test, automate and practice! • Build your DB expertise Tip 4: Build Your Stack For Doomsday
  14. • Operator - Capabilities, Community/Enterprise, Upgrades • Failovers - How?

    Downtime? • Day 2 Operations • K8s Friendly Tip 5: Choose your DB Wisely
  15. Key Takeaways • Kubernetes primitives and ecosystem are ready to

    Stateful Apps • Enterprises can take advantage of Kubernetes to run their critical databases, saving on multiple dimensions • But there are still challenges: - Data service layer - Monitoring and microservices correlation
  16. Q&A