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

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 configurations will be stored ideally in your version control systems (VCS) like Git, GitLab, or GitHub. BROUGHT TO YOU IN PARTNERSHIP WITH REFCARD | GITOPS FOR KUBERNETES REFCARD | SEPTEMBER 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

What's new with GitOps and OpenShift 1 Jonas Janz AppDev Solutions Architect https://github.com/pixeljonas 2 GitOps is when the infrastructure and/or application state is fully represented by tooling Day 2 operations : All changes triggered from Git Tools of the Trade https://argoproj.github.io/argo-cd https://kustomize.io/ Argo CD Kustomize Argo CD - What is It? Argo CD is a declarative svc project: product-catalog source: path: manifests/app/overlays/dev-quay repoURL: https://github.com/gnunn-gitops/product-catalog.git targetRevision: master syncPolicy: automated: prune:

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

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 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 CI/CD pipeline platform, which boils down to your

(SIGs) 贊助 •Kubernetes 1.14版開始支援 8 Sample Repoitory •https://github.com/demoyuw/k8s-summit- cd-repository.git •Git clone https://github.com/demoyuw/k8s-summit- cd-repository.git •cd k8s-summit-cd-repository •生成替換掉或增加參數的yaml •kubectl kustomize overlay/development 17 18 19 Use generate YAML and apply on kubernetes •Generate yaml and apply to k8s •kubectl kustomize overlay/development | kubectl apply -f - 20 部署出dev

standardizes the deployment and management of complex systems, improves collaboration between development and operations teams, and increases the reliability and reproducibility of deployments. GitOps them to infrastructure automation. Whereas DevOps is the practice of automating the software development lifecycle, GitOps contributes to the automation of infrastructure. This includes version control promotes modularity, independence, collaboration, versioning, and security. It allows for efficient development, testing, and deployment of both application and infrastructure components while ensuring clear

Demo: Canary Deployment @codefresh https://github.com/brandonphillips/express-microservice https://github.com/brandonphillips/gitopsapp https://github.com/brandonphillips/rollout Codefresh Enterprise drift ● Deployments & rollbacks should be painless ● Developers can and should focus on feature development @codefresh Practicing GitOps ● Templating: Helm, Kustomize, and more ● Configuration Drift: @codefresh Argo CD A declarative GitOps continuous delivery tool for Kubernetes https://argoproj.github.io/argo-cd/ MyApp k8s manifest MyApp 1. Commit 5. Call ArgoCD to sync MyApp source code 2.

drifts, and take action Enhanced Security Familiar tools and Git workflows from application development teams Standard Workflow Multi-cluster consistency 7 Source Git Repository Image Registry OpenShift Builds 15 kind: Build metadata: name: myapp-buildpack spec: source: url: https://github.com/myorg/myapp strategy: name: buildpacks-v3 builder: image: paketobuildpacks/builder:full image: quay.io/myorg/myapp:v1 kind: Build metadata: name: myapp-s2i spec: source: url: https://github.com/myorg/myapp strategy: name: source-to-image builder: image: registry.redhat.io/openjdk/openjdk-11-rhel8