KubeCon + CloudNativeCon India 2024

Managing hybrid environments with public and private clouds poses significant challenges, especially with disparate interfaces and legacy applications. Our development and QE teams faced difficulties navigating multiple environments—testing private cloud code on private Docker clouds and public cloud code on public resources. Legacy apps, often running on bare metal or metal instances, added complexity. To tackle this, we used Kubernetes and CNCF projects like KubeVirt, CrossPlane, and Longhorn to build a unified hybrid hyper-converged cloud platform. This session will explore how we integrated these technologies to streamline operations. You'll learn about the initial challenges, how KubeVirt enabled virtualization, CrossPlane’s role in multi-cloud management, Longhorn’s storage solutions, and the unification of these components into a cohesive platform.

At Intuit, we have ~2000 production services that serve North-South and East-West Traffic using API Gateway and Service Mesh. These services span across ~350 k8s clusters and are managed by 10,000+ engineers. This talk walks you through multiple design iterations conducted by the Traffic team at Intuit in building the platforms that serve 1.5 Million+ TPS. Topics that are covered include lessons learnt while 1. Designing a cost effective, low latency, highly scalable, multi tenant API Gateway and Service Mesh platforms. 2.Using a non blocking model to externalise Authorization using an OPA based sidecar. 3.Distributing traffic configurations that are self serviced by 10,000+ engineers to the Traffic runtime platforms. 4. Designing Rate Limiting solutions with Low latency and low error

In Intuit, We have API Gateway and Service Mesh platforms that are responsible for handling ~30 billion requests every day and providing ingress to ~2000 services. With this talk, we’ll see - * How Admiral manages failover configurations by creating required custom resources like globalTrafficPolicy (GTP) across 300+ clusters and provides feedback on the activity. * Manage Observability for all failover activity and provide better insights to Developers. * How Intuit achieved simplified centralized failover UI experience leveraging Kubernetes and Istio features. * Operational challenges associated with managing the failover configurations. * High Availability and DR for services across 7000+ namespaces and enabling more than 900 teams to have seamless and unified experience to manage failover endpoints.

Rolling out a new service, adding databases clusters, are always challenging. The recommended way is to start with diverting small % of traffic to the new service and increase rollout % if things look well. If things don’t go well, the rollout % should be reduced. This is generally done through feature flags and manually monitoring the service with an observability tool. Feature flags enable remote update of rollout % without doing new deployments. OpenFeature is a new CNCF project which is trying to standardise feature flagging. It also has built-in hooks for OpenTelemetry so that feature flag values are available by default in tracing & metrics data captured by OpenTelemetry. In this talk, I will share how you can leverage open standards like OpenFeature (for feature flagging) and OpenTelemetry ( for observability) to better manage rollouts. You can enable automatic increase or decrease of rollout % by tying observability with feature flagging.

How do we build a self-service platform that allows developers to interact with a legacy application through Kubernetes? In most other parts of the organisation, developers seek to operate on Kubernetes using the now-familiar concepts of GitOps and cloud-native ways for deploying their applications. When Kubernetes is a one-stop for deployment, the cognitive loads for platform and infrastructure can be minimized, and gives better focus to implementing business needs. In this talk, Bankdata.dk will share their experience building a Kubernetes API-driven self-service platform for operating three of their most critical legacy systems on Kubernetes, through ArgoCD and GitOps. The platform builds on the Java operator framework, and wraps operations on a portal server also running in Kubernetes. Bankdata.dk delivers all IT to 9 danish banks, including the 2nd and 3rd largest.

At PepsiCo, we are committed to enhancing efficiency and developer experience by continuously reviewing our processes and systems. As part of streamlining our deployment workflows, we transitioned to the GitOps methodology and adopted ArgoCD, a powerful GitOps tool with a feature-rich web UI that facilitates intuitive management of deployments, rollbacks, and application health. By leveraging ArgoCD's App of Apps pattern, we could define a bootstrapper Application, enabling the automation of application deployment. This approach allowed us to achieve self-service Continuous Delivery, empowering teams to independently manage their deployments while maintaining centralized control and visibility. Join us, as we share some of the challenges, including managing dependencies, configuring environments and ensuring consistency across deployments. Additionally, we will highlight the strategies and best practices, including the implementation of App of Apps pattern and the integration of Helm.

Expedia Group's journey to implement GitOps with ArgoCD is a story of innovation, scalability, and overcoming challenges. Our GitOps journey involved migrating from KubeFed to ArgoCD, focusing on extensive scalability testing across hundreds of virtual clusters, set up using open source tool, vcluster. We proactively identified potential challenges and prepared comprehensive test cases tailored to different application flavors. We created three types of applications for testing, with sizes varying between 15-30 resources, including CRDs and jobs, small applications containing 15 resources and large applications containing 30 resources. We experimented with multiple test scenarios, using permutation and combination of applications tested on 300 vclusters, scaling approximately 1,000 applications to 30,000+ across these clusters. We concluded this initiative with determining optimal settings for various tunable parameters in the ArgoCD controllers.