IstioCon 2021 IstioCon 2021 is the inaugural community conference for the industry's most popular service mesh. IstioCon is a community-led event, showcasing the lessons learned from running Istio in production roadmap sessions. Fun and games are also included with two social hours to take the load off and mesh with the Istio community, vendors, and maintainers! #IstioCon Agenda ● Introduction ● Target Audience London ● Have 2 cats @rytswd #IstioCon Briefly about UPSIDER ● Startup providing B2B payment service ● Uses Istio extensively in production ● Headquarter in Tokyo, Japan ● Remote team around the world

system. THE GITOPS GUIDE TO BUILDING & MANAGING INTERNAL PLATFORMS 3 weave.works ▼ Self-service developer experience (DX) In the past, the only way a developer could get access to servers, data team delivers self-service APIs to developers. This team builds and maintains the platform that is consumed by development teams. The platform they build is a collection of self-service APIs, tools, services are internal customers of the platform team. In order to properly fulfill its role as an internal service provider, the platform team must take a strategic approach to resource management. “The challenge

基础架构 以容器为中心 部署可预测性 可预测 弹性能力 弹性调度 恢复能力 自动化运维，快速恢复 蓝盾/TencentHub…… 每天可交付数十次 运维开发&应用开发 TSF,Service Mesh K8S（TKE） 云原生方法 业务最佳实践 K8S（TKE） K8S（TKE）+业务画像 K8S（TKE） ⚫ 云原生计算基金会（CNCF），2015年由谷歌牵头成立，第一个毕业的项目Kubernetes。

Open Cluster Management Other GitOps Tools PipeCD Keptn Pulumi Kubernetes Operator Summary 18 Chapter 3–Templating Everything in Git Kustomize Helm Operators delivery. It allows the teams that wrote, delivered, and supported the software to work together in service of that goal. DevOps isn’t necessarily a department, but rather a culture in your organization. scribed in a 2021 blog post [1.7], is very interesting. Back in 2017, Weaveworks was a Software-as-a-Service (SaaS) company that hosted applications on their platform using Kubernetes as the infrastructure

GitOps Removing OpenShift GitOps Operator from your cluster Last Updated: 2024-01-11 Red Hat OpenShift GitOps 1.10 Removing GitOps Removing OpenShift GitOps Operator from your cluster Legal Notice project. The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are instances added to the default namespace of the OpenShift GitOps Operator. It also discusses how to remove the OpenShift GitOps Operator from your cluster. . . . . . . . . . . . . . . . . . . . . . .

project. The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are 点上运 运行 行 GITOPS CONTROL PLANE 工作 工作负载 负载 1.1. 将 GITOPS CONTROL PLANE 工作负载移到基础架构节点 1.2. 将 GITOPS OPERATOR POD 移到基础架构节点 1.3. 其他资源 3 3 4 6 目 目录 录 1 Red Hat OpenShift GitOps 1.13 基 基础 础架 架构节 构节点上的 点上的 Container Platform 在基础架构节点上运行 GitOps control plane 工作负载。默认 情况下，这包括 Operator pod 和由 openshift-gitops 命名空间中的 Red Hat OpenShift GitOps Operator 创建的 control plane 工作负载，包括此命名空间中的默认 Argo CD 实例。 使用 GitOps control

project. The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are ？ 3 第 2 章 关于 RED HAT OPENSHIFT GITOPS Red Hat OpenShift GitOps 是一个使用 Argo CD 作为声明性 GitOps 引擎的 Operator。它启用了多集群 OpenShift 和 Kubernetes 基础架构的 GitOps 工作流。使用 Red Hat OpenShift GitOps，管理员可以在 集群和开发生命周期中一致地配置和部署基于 分析和实验等高 级部署功能。 集群范 集群范围 围的 的实 实例 例 Argo CD 配置为管理集群中的所有资源的模式，包括某些特定于集群的资源，如集群配置、集群 RBAC、Operator 资源、平台 Operator 或 secret。 control plane (GitOps control plane) 在 GitOps 上下文中，您可以为每个安装的 Argo CD 有一个 control

container orchestration capabilities like: • Automated rollouts and rollbacks of deployments • Service discovery and load balancing capabilities − As Kubernetes gives its own IP address to Pods and translates into a faster turnaround for new features and functionality for the customer. SELF-SERVICE With the existing CI/CD approach, the development team remains dependent on the operations team empowers teams to become more efficient and strategic. It enables development teams to be more self-service in nature as they would be less dependent on platform and operations teams to deploy and handle

kustomization.yaml └── services └── service-a ├── base │ ├── config │ │ ├── 300-deployment.yaml │ │ ├── 310-service.yaml │ │ └── kustomization.yaml dev-deployment.yaml ├── dev-service.yaml └── kustomization.yaml ├── base │ ├── deployment.yaml │ ├── kustomization.yaml │ └── service.yaml └── overlays ├── development / ● Sometimes you have cases where you need to deploy things in a specific order ○ Subscribe Operator before deploying instance ○ Create namespace/project before deploying application into it ○ Deploy

(Learn how to build a CI/CD pipeline.) The differentiating factor of a GitOps pipeline is the GitOps operator. This mechanism sits between the pipeline and the infrastructure platform, acting as a middleman between them. There are multiple available operators such as: Kubernetes Operator Terraform Cloud Operator Azure Service Operator Etc. GitOps workflow Now, we’ve got a Git repository and a properly configured CI/CD pipeline. The pipeline will then inform the Git Operator, which will pick up all the modifications and the desired new state. The Git operator will then compare the state of the existing infrastructure