#IstioCon Getting Started and Beyond: Istio Multicluster with GitOps Ryota Sawada / @rytswd / CTO at UPSIDER, Inc. #IstioCon Welcome to the IstioCon 2021 IstioCon 2021 is the inaugural community conference showcasing the lessons learned from running Istio in production, hands-on experiences from the Istio community, and featuring maintainers from across the Istio ecosystem. The conference offers a mix of mesh with the Istio community, vendors, and maintainers! #IstioCon Agenda ● Introduction ● Target Audience ● Topics covered / NOT covered ● About Istio Multicluster ● Brief brush up on Istio resources

building DX teams to work with platform teams to improve overall organisational productivity and development velocity.” James Governor, — Source Redmonk.com Executive summary Adopting the platform approach they would go about building and maintaining the platform. Further, how they would build a new development culture around the platform that makes software delivery seamless. In this paper, we look at are essentially application development teams that build features and release code into production. Platform teams, on the other hand, exist to support application development teams and make resources

drift ● Deployments & rollbacks should be painless ● Developers can and should focus on feature development @codefresh Practicing GitOps ● Templating: Helm, Kustomize, and more ● Configuration Drift: CI/CD Platform 6. Get latest from repo Config Sync GitOps Demo! @codefresh ● Service Meshes: Istio, Linkerd (SMI), and more @codefresh Argo Rollout Advanced deployment CRD for Blue Green and Canary

) 准备——工作 流 面向角色 环境描述 环境名称样例 场景介绍 开发工程师 用于日常开发、联调 dev 如果 Java 栈实现灰度能力，可以通过新建环境随时拉 起开发自测子环境 如果采用 Istio + Skywalking 技术栈，通过 Zadig 开启自测模式随时拉起子环境 测试工程师 用于测试手工验证 sit 自主升级环境，选择一个或多个 PR/MR 进行功能需求 的并行验证。 执行工作流更新生产环境 步骤包含：灰度 20% -> 审批 -> 灰度 60% -> 审批 -> 新版本全量发布 Sprint 发布 需求开发 测试验证 产品规划 变更发布 生产环境发布—— Istio 发布， 执行工作流更新生产环境 步骤包含：部署新版本 20% 流量导入新版本 -> 审批 -> 100% 流量导入新版本 Sprint 发布 需求开发 测试验证 产品规划 Sprint

管理员(运维)准备——工作流 面向角色 环境描述 环境名称样例 场景介绍 开发工程师 用于日常开发、联调 dev 如果 Java 栈实现灰度能力，可以通过新建环境随时拉起 开发自测子环境 如果采用 Istio + Skywalking 技术栈，通过 Zadig 开启 自测模式随时拉起子环境 测试工程师 用于测试手工验证 sit 自主升级环境，选择一个或多个 PR/MR 进行功能需求 的并行验证。 执行工作流更新生产环境 步骤包含：灰度 20% -> 审批 -> 灰度 60% -> 审批 -> 新版本全量发布 Sprint 发布 需求开发 测试验证 产品规划 变更发布 生产环境发布——Istio 发布， 执行工作流更新生产环境 步骤包含：部署新版本 20% 流量导入新版本 -> 审批 -> 100% 流量导入新版本 Sprint 发布 需求开发 测试验证 产品规划 Sprint

Chapter 4–Git Workflows Separate Your Repositories Separate Development in Directories, Not Branches Trunk-Based Development Policies and Security Summary 25 Chapter 5–Repository based. Around 2007, many developers and site administrators began to identify gaps in application development processes. Although the DevOps movement officially started around 2007, I believe its true birth ways, the Agile Manifesto is the grandfather of DevOps. Agile development practices were a big step toward improving the application development process for the end user and for internal or external customers

way we develop and manage applications, resulting in faster, more consistent, more collaborative development cycles. It has evolved further by incorporating microservices-based architectures and even databases management solutions such as Terraform. The goal of GitOps is to simplify and streamline the development process. This leads to building reproducible infrastructure with proper state management, which first thing to consider is the Git repository. As GitOps is platform-agnostic, users can utilize any local or cloud-based Git repository such as: GitHub BitBucket Azure Repos GitLab Etc. Then comes the

to survive. Every company is a technology company now. Yet, like all approaches to software development, there is more than one way to implement DevOps. As the DevOps Research and Assessment group (DORA) application code. This built-in observability allows for fast iteration and experimentation, and allows development teams to make crucial decisions before they deploy new features. Features or other updates like they know, using pull requests to accelerate deployment and operations tasks. The benefits for development teams include increased velocity and improved system reliability. Increased velocity with GitOps

Resources 11 14 21 23 31 36 eBook 3 GitOps in Practice A “you build it, you own it” development process requires tools that developers know and understand. GitOps is our name for how we use control and alerts you when there is a divergence. The ultimate goal of GitOps is to speed up development so that your team can make changes and updates safely and securely to complex applications running deployment. This allows your team to ship 30-100x more changes per day, and increases overall development output 2-3 times. 1. Increased Productivity 2. Enhanced Developer Experience Key Benefits of

kept alongside application code in Git. Keeping your entire system in Git means that your development team uses familiar Git-based workflows and pull requests to deploy both application and infrastructure in Git allow developers to use familiar workflows, reducing the time it takes to spin up new development, test environments, or deploy new features to a cluster. Teams can ship more changes per day approach, the development team remains dependent on the operations team to deploy new changes in production. GitOps empowers teams to become more efficient and strategic. It enables development teams to