argocd-example-apps
updatecli
argocd-example-apps | updatecli | |
---|---|---|
18 | 9 | |
1,378 | 484 | |
2.4% | 4.3% | |
2.0 | 9.6 | |
4 days ago | 6 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
updatecli
-
Top 10 CLI Tools for DevOps Teams
Updatecli is a useful tool for fine-tuning update strategies in DevOps. As you've probably experienced, manual updates often result in outdated specs because figuring out what can be updated is tricky.
-
ArgoCD // Helm Chart // Dev/Staging // Your Best-Practise
A second innovation is the use of updatecli to observe the available application helm releases and update the environment helm charts automatically to promote application versions:
-
Looking for an automated way to add ENVs in the deployment file in the helm chart whenever a new ENV comes from the developer's end
Maybe you could have a look to Updatecli https://github.com/updatecli/updatecli
-
Automatic update when newer image is available
I built https://github.com/updatecli/updatecli for those situations where it's not possible to guess the next tag version. It's a declarative dependency management tool, You define in a manifest how your Yaml should be update, then run updatecli from your CI to automatically open a PullRequest on your repository when a new container tag is available.
- What do you use to update image tags?
- GitHub - updatecli/updatecli: Updatecli is an automation engine
-
Show HN: What if Dependabot and Ansible had a child?
Like in this package https://github.com/updatecli/updatecli/tree/main/pkg/plugins...
And the matching between a package and a resource kind is done here
What are some alternatives?
microservices-demo - Sample cloud-first application with 10 microservices showcasing Kubernetes, Istio, and gRPC.
argocd-image-updater - Automatic container image update for Argo CD
gitflow - Git extensions to provide high-level repository operations for Vincent Driessen's branching model.
renovate - Universal dependency automation tool.
argocd-autopilot - Argo-CD Autopilot
dependabot-core - 🤖 Dependabot's core logic for creating update PR's.
gitops-environment-promotion - Example for promoting a release between different GitOps environments
helm-charts - Epinio Helm chart
argo-cd - Declarative Continuous Deployment for Kubernetes
kubernetes-management - Jenkins Infrastructure Kubernetes Management
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
globalping-cli - A simple CLI tool to run networking commands remotely from hundreds of globally distributed servers