argocd-example-apps
argo-events
Our great sponsors
argocd-example-apps | argo-events | |
---|---|---|
18 | 8 | |
1,371 | 2,230 | |
3.5% | 1.8% | |
2.2 | 9.4 | |
about 23 hours ago | 10 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-events
-
Progressive Delivery with Argo Rollouts : Blue-Green Deployment
Argo Events - Event-based Dependency Manager
- Looking for Git repos branches monitoring/tracking project
- Any interesting project with potential to become new kubewatch?
-
Best Practices for Argo CD
Argo Events
- Release v1.5.6 - argoproj/argo-events
-
Go-generated protobufs with map[string]interface{}
I'm trying to extend argo events to support the quorum queues of RabbitMQ: argoproj/argo-events - Issue 1479 - Allow AMQP arguments in AMQPQueueDeclare instead of always passing nil (Enables Quorum Queues and other functionality)
- Argo CD
-
Argo Events. slack as a event source. Does it work for you?
slack event source was created from from this yaml https://github.com/argoproj/argo-events/blob/master/examples/event-sources/slack.yaml
What are some alternatives?
microservices-demo - Sample cloud-first application with 10 microservices showcasing Kubernetes, Istio, and gRPC.
sources-for-knative - VMware-related event sources for Knative.
gitflow - Git extensions to provide high-level repository operations for Vincent Driessen's branching model.
argo-cd - Declarative Continuous Deployment for Kubernetes
argocd-autopilot - Argo-CD Autopilot
argo - Workflow Engine for Kubernetes
gitops-environment-promotion - Example for promoting a release between different GitOps environments
cadence - Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.
kubewatch - Watch k8s events and trigger Handlers
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
configs - Config files used to define parameters specific to compute environments at different Institutions