argocd-example-apps
argo-rollouts
argocd-example-apps | argo-rollouts | |
---|---|---|
18 | 9 | |
1,378 | 2,499 | |
2.9% | 2.7% | |
2.0 | 9.5 | |
7 days ago | 2 days ago | |
Jsonnet | Go | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
argocd-example-apps
- ArgoCD // Helm Chart // Dev/Staging // Your Best-Practise
-
What is better Github or Devops? We of the kubernetes Dutch podcast interviewed April Edwards. Normally the podcast is in dutch but this episode is in englisch.
I have not yet had the opportunity to test flux extensively. Regarding Argo examples, the Argo team themself maintain such a repo: https://github.com/argoproj/argocd-example-apps
- Did I miss something here, regarding network policies and helm templates? (Slightly ranty)
-
Am I missing something? (argo cd and helm in AWS)
Second, when dealing with OCI helm charts, look up the umbrella chart model https://github.com/argoproj/argocd-example-apps/blob/master/helm-dependency/README.md. This basically lets you create a helm chat that doesn’t do anything but call your next helm chart as a dependency. I use this with OCI stores helm charts all over the place. Also, in the next ArgoCD release, you should be able to get multiple sources for a sync, but we’ll see when that comes out
-
Argo CD and Helm: Deploy Applications the GitOps Way!
argocd app create helm-guestbook --repo https://github.com/argoproj/argocd-example-apps.git --path helm-guestbook --dest-server https://kubernetes.default.svc --dest-namespace default
-
Getting Started With GitOps For Developers!
Let’s Fork a sample repo, for example, like this one found here: https://github.com/argoproj/argocd-example-apps
-
deploy to different namespace from argocd
apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: guestbook namespace: argocd spec: project: default source: repoURL: https://github.com/argoproj/argocd-example-apps.git targetRevision: HEAD path: guestbook destination: server: https://kubernetes.default.svc namespace: guestbook
-
ArgoCD installation
For example if I point to https://github.com/argoproj/argocd-example-apps, from the UI, I can see a new repository but no applications
-
GitOps installation
extraObjects: - apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: my-app namespace: argocd spec: project: default source: repoURL: 'https://github.com/argoproj/argocd-example-apps' path: guestbook targetRevision: HEAD destination: server: 'https://kubernetes.default.svc' namespace: test syncPolicy: automated: {} syncOptions: - CreateNamespace=true EOF
-
Fixing potential security issues in your Infrastructure as Code at the source with Sysdig
❯ cd ~/git ❯ gh repo fork https://github.com/argoproj/argocd-example-apps.git --clone ✓ Created fork e-minguez/argocd-example-apps Cloning into 'argocd-example-apps'... ... From github.com:argoproj/argocd-example-apps * [new branch] master -> upstream/master ✓ Cloned fork
argo-rollouts
-
Gateway API is now in Beta; new project formed for service mesh APIs
And support is on it's way for Argo Rollouts 🎉 https://github.com/argoproj/argo-rollouts/pull/2004
-
Progressive Delivery with Argo Rollouts : Blue-Green Deployment
curl -LO https://github.com/argoproj/argo-rollouts/releases/latest/download/kubectl-argo-rollouts-linux-amd64 chmod +x ./kubectl-argo-rollouts-linux-amd64 sudo mv ./kubectl-argo-rollouts-linux-amd64 /usr/local/bin/kubectl-argo-rollouts kubectl argo rollouts version
-
Progressive Delivery with Argo Rollouts: Canary Deployment
kubectl create namespace argo-rollouts kubectl apply -n argo-rollouts -f https://github.com/argoproj/argo-rollouts/releases/latest/download/install.yaml
-
how do you auto deploy to kubernetes with auto rollbacks?
You can see in why argo section here what are the limitations of rolling updates and how rollouts solves it: https://github.com/argoproj/argo-rollouts
-
Best Practices for Argo CD
Argo Rollouts
-
Canary deployments
Check the public users list https://github.com/argoproj/argo-rollouts/blob/master/USERS.md
-
argo-rollouts VS flagger - a user suggested alternative
2 projects | 25 Jan 2022
- argoproj/argo-rollouts: Progressive Delivery for Kubernetes
-
Automation assistants: GitOps tools in comparison
Supplementary GitOps operators can also be used for deployment strategies, such as canary releases, A/B tests, and blue/green deployments, which have now been grouped under the term “progressive delivery”. The resources of most GitOps operators are not sufficient for this. One solution is Flagger. The tool that was launched by Weaveworks is now being developed as part of the Flux project. The Argo project also has an operator for this use case: Argo Rollouts. Both offer CRs for implementing progressive delivery strategies in interaction with various ingress controllers and service meshes.
What are some alternatives?
microservices-demo - Sample cloud-first application with 10 microservices showcasing Kubernetes, Istio, and gRPC.
flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments)
gitflow - Git extensions to provide high-level repository operations for Vincent Driessen's branching model.
Flux - Successor: https://github.com/fluxcd/flux2
argocd-autopilot - Argo-CD Autopilot
fleet - Deploy workloads from Git to large fleets of Kubernetes clusters
gitops-environment-promotion - Example for promoting a release between different GitOps environments
terraform-k8s - Terraform Cloud Operator for Kubernetes
argo-cd - Declarative Continuous Deployment for Kubernetes
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets