Jump to content

Search the Community

Showing results for tags 'gitops'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Welcome New Members !
    • General Discussion
    • Ask a Question
    • Site News
  • DevOps & SRE
    • DevOps & SRE
    • Databases
    • Development
    • CI/CD
    • Docker, Containers & Serverless
    • Infrastructure-as-Code
    • Kubernetes
    • Linux
    • Logging, Monitoring & Observability
    • Security
  • Cloud Providers
    • AWS
    • Azure
    • GCP
    • OpenShift

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL

LinkedIn Profile URL

About Me

Development Experience

Cloud Experience

Current Role



Favourite Tools


  1. GitOps has continued in its popularity and has become the standard way to manage Kubernetes cluster configuration and applications. Red Hat continues to see the widespread adoption of the GitOps methodology across our portfolio as customers look for ways to bring increased efficiency to their operations and development teams. View the full article
  2. At some point during the OpenShift deployment phase, a question about project onboarding comes up, "How can a new customer or tenant be onboarded so they can deploy their own workload onto the cluster(s)?" While there are different ways from a process perspective (Service Now, Jira, etc.), I focus on the Kubernetes objects that must be created on each cluster. In A Guide to GitOps and Argo CD with RBAC, I described setting up GitOps RBAC rules so tenants can work with their (and only their) projects. This article demonstrates another possibility for deploying per tenant and per cluster ... View the full article
  3. A GitOps tool like Argo CD can help centralize the automation, installation, and configuration of services onto multiple Kubernetes clusters. Rather than apply changes using a Kubernetes CLI or CI/CD, a GitOps workflow detects changes in version control and applies the changes automatically in the cluster. You can use a GitOps workflow to deploy and manage changes to a Consul cluster, while orchestrating the configuration of Consul service mesh for peering, network policy, and gateways. This approach to managing your Consul cluster and configuration has two benefits. First, a GitOps tool handles the order-of-operations and automation of cluster updates before configuration updates. Second, your Consul configuration uses version control as a source of truth that GitOps enforces across multiple Kubernetes clusters. This post demonstrates a GitOps workflow for deploying a Consul cluster, configuring its service mesh, and upgrading its server with Argo CD. Argo CD annotations for sync waves and resource hooks enable orchestration of Consul cluster deployment followed by service mesh configuration with Custom Resource Definitions (CRDs). Updating a Consul cluster on Kubernetes involves opening a pull request with changes to Helm chart values or CRDs and merging it. Argo CD synchronizes the configuration to match version control and handles the order of operations when applying the changes... View the full article
  4. Recently, I published the blog Provisioning OpenShift clusters using GitOps with ACM, explaining how to create OpenShift clusters with RHACM using GitOps with ArgoCD. The OpenShift installation type was IPI and valid for most platforms: Azure, AWS, GCP, vSphere, etc., but not for baremetal. If you've ever installed an OpenShift cluster in baremetal and disconnected, you know how different it is from any other installation. View the full article
  5. In this article, I will demonstrate the use of MicroShift and GitOps in a homelab environment and explore some of my learnings from this exercise. While this article is intended to be written as a "here's what I did" rather than as step by step instructions, I thought it'd be useful to list the software versions that were used. At the time of this writing, MicroShift is only supported on hardware that supports Red Hat Enterprise Linux (RHEL) 8.7... View the full article
  6. We are excited to announce support for full cluster lifecycle automation through GitOps or Infrastructure as Code (IaC) tools like Terraform for Amazon EKS Anywhere (EKS-A). Previously, the only mechanism for customers to perform full EKS-A cluster lifecycle operations such as provisioning, updates, and deletion was by using an Amazon command-line-interface (CLI) tool “eksctl”. Now, EKS-A supports GitOps and IaC in the EKS-A management cluster so customers can automate EKS-A workload cluster lifecycle operations including cluster creation, update, and deletion. View the full article
  7. Iterative added a registry for machine learning models to its portfolio of Git-based tools for infusing artificial intelligence into applications. Iterative CEO Dmitry Petrov said the Iterative Studio Model Registry is intended to make it easier for application development teams to track which models are being used as the number of applications infused with AI […] The post Iterative Adds Registry to GitOps Portfolio for ML Models appeared first on DevOps.com. View the full article
  8. GitOps is an operational framework for continuous deployment. Typically used with Infrastructure as Code (IaC), the definitions are managed with Git workflows, providing a version history and an audit trail. Automatic reconciliation compares the desired state, stored in Git, with the actual runtime state and applies changes as required. This highly automated approach to continuous delivery increases software delivery pipeline velocity, saves DevOps engineers time and delivers consistent and repeatable deployments. Weave GitOps is a continuous delivery product to run your applications in any Kubernetes. Applications are delivered securely and reliably with the use of Policy as Code providing guardrails to ensure corporate standards continually are met. Weave GitOps takes DevOps to the next level by applying GitOps principles to cluster management. Manage your entire fleet of clusters and applications one pull request at a time. Weave GitOps is built on a core of Flux, which Weaveworks donated to the CNCF and still takes a very active role in its maintenance... View the full article
  9. By leveraging tools that are customary to a developer’s workflow, GitOps makes infrastructure definition and management inclusive for developers.View the full article
  10. Satisfying Developer Requests We have recently been in a situation where our customer wanted to just give access to the developers to manage the right projects in OpenShift. Developers at the same time, needed to create applications on OpenShift without needing to consult administrators for access to ArgoCD/OpenShift GitOps. This has increased in importance for non-production environments. If a developer team has gone through the effort of requesting budget, time, and resources to develop a new application on OpenShift, should they really wait for an administrator to change settings for them to get started? View the full article
  11. GitOps is a term that has become very popular in the last few years and is easily on its way to becoming just as overloaded with myth and mystery as DevOps. In this series of articles, we will present the principles and practices of GitOps, explaining the why and how of the automated processes that aim to deliver secure, high-quality, microservice-based applications quickly and efficiently. In part 1 of the series, we introduced the main concepts of GitOps, together with the open source automation technology Tekton and ArgoCD. These tools operate on the Red Hat OpenShift platform to deliver a cloud-native continuous integration and continuous delivery process. The first article also gave an indicative structure for Git repository and ArgoCD applications that can create a secure and audited process for the delivery to production. This article will continue the series by explaining how container images produced during the continuous integration phase can be successfully managed and used within the continuous delivery phase. View the full article
  12. Azure Kubernete Service (AKS) and Azure Arc-enabled Kubernetes for Hybrid and Multicloud Environments When it comes to enterprise platforms, Microsoft has a long history of providing solutions to the complex environment of the global and fast changing enterprise landscape. Azure Kubernetes Service (AKS), with its tight integration with Azure Active Directory (Azure AD) and Azure Policy, is a managed Kubernetes offering focused on satisfying those needs... View the full article
  13. GitOps is a term that has become very popular in the last few years and is easily on its way to becoming just as overloaded with myth and mystery as DevOps. Some definitions of GitOps describe it as a mechanism for delivering and maintaining the infrastructure on which Kubernetes applications run. Other definitions include the infrastructure focus, and augment it with the definition of a business application that has been created for the platform. In this series of articles, we will present the principles and practices of GitOps, explaining the why and how of the automated processes that aim to deliver secure, high-quality, microservice-based applications quickly and efficiently. View the full article
  14. Read More: https://faun.pub/introduction-to-gitops-part-1-cba452d4e90a Prerequisites Basic Understanding of Git & GitHub Basic Understanding of Cloud Computing Basic Understanding of Kubernetes Basic Understanding of CI/CD Deployment
  15. GitOps is an operational software development framework that enables organizations to manage IT infrastructure using Git and deliver software applications efficiently. It is an evolution of DevOps that combines Infrastructure-as-Code (IaC) and DevOps best practices for designing a model that can instantly reproduce the system’s cloud infrastructure and manage architecture based on the state of Git repositories. GitOps relies on Git as a source control system and acts as a control mechanism for developing, editing, updating, and deleting system architecture. Simply put, it is the practice of deploying changes from Git to production Kubernetes clusters in a reliable and automated way. View the full article
  16. The integration eliminates environment drift, with auto-update across infrastructure, microservices and databases San Francisco, CA, May 16, 2022 — Bunnyshell, the leading Environment-as-a-Service (EaaS) platform, today announced native integration with the infrastructure-as-code tool Terraform. The new integration provides a complete end-to-end solution for development teams to replicate their production environments at all stages of the software development […] The post Bunnyshell Launches Native Terraform Integration, Enabling True GitOps Governance appeared first on DevOps.com. View the full article
  17. ‘Drift’ is a given in a dynamic software system where code gets outdated the minute it is released. This is true of application code, and in systems where infrastructure is managed as code as well. Drift is a problem for builders and maintainers of these systems as it causes incompatibility issues, brings unpredictability, and makes systems unreliable. Reducing configuration drift is a top priority for system architects and SREs alike. In this post, we look at why drift detection is key to modern operations, and how GitOps enables it using a new breed of tooling and approaches... View the full article
  18. This post was authored by Michael Beaumont, Weaveworks Software Engineer. From the moment that the enterprise began considering cloud services, they have been talking about the hybrid cloud - one where they leverage both a public cloud and on-premise data centers. The combination of EKS in the cloud and EKS-D on-premise now makes that possible. We’ve put together a demo showing how easy it is to install Weave Kubernetes Platform and use GitOps to build a continuous deployment pipeline and promote deployments from a development cluster to production. This scenario covers a development cluster based in the cloud on AWS EKS, together with a production deployment on-premise with EKS-D. EKS-D is a Kubernetes distribution from AWS that includes the same patches and runtime as EKS uses... View the full article
  19. Using Kubernetes is a synonym for manipulating YAML. Even if the YAML community describes it as a human-readable language, it can sometimes be tricky to read it, especially in the context of Kubernetes when you are manipulating complex deployments, services, ingresses, and other resources. View the full article
  20. At a recent online virtual event with Kong, Paul Curtis (@pfcurtis_NY), Weaveworks’ Principle Solutions Architect demonstrated how you can use Weave Kubernetes Platform and GitOps to make your transition from running legacy applications on Virtual Machines onto Kubernetes much simpler... View the full article
  21. The new offering promises observability into what’s running in production – at scale, where potential issues arise and control over rollbacks and the release process Mountain View, Calif., November 16, 2020 – Today Codefresh launched a new initiative – GitOps 2.0 – which seeks to solve limitations that have existed in GitOps and promote best practices for the future. Codefresh’s support […] The post Codefresh Launches First Components of GitOps 2.0 Offering and Engages Community on Standards appeared first on DevOps.com. View the full article
  22. A core capability of any distributed system, whether it is distributed for capacity or recovery reasons, is that the initial system can be reproduced. More often than not, large organizations document changes in a Word document that get manually applied to each and every environment. While this has served as a way to propagate changes to core systems essentially for decades, it is not a reliable way to reproduce a system in today’s distributed world... View the full article
  23. With more than 8.3 trillion dollars in assets under its administration and 3.3 trillion in total discretionary assets, Fidelity Investments is one of the world’s largest asset managers. The firm offers a wide range of investment products and investment services that span retail, workplace, institutional and intermediary markets. Their long-term investment in the latest technology has the goal of simplifying and digitizing support for more than 500 applications that support their customers... View the full article
  24. Recently, Red Hat launched the Advanced Cluster Management tool, which aims to help organizations overcome the challenges of having applications deployed in multiple clusters and clouds. Red Hat is also actively collaborating with the Tekton project as the solution that will enable teams to build Kubernetes-style delivery pipelines that can fully control and own the complete life cycle of their microservices without having to rely on central teams to maintain and manage a CI server, plugins, and its configurations... View the full article
  • Member Statistics

    Total Members
    Most Online
    Newest Member
  • Create New...