argo-helm
cdk8s
Our great sponsors
argo-helm | cdk8s | |
---|---|---|
17 | 48 | |
1,547 | 4,129 | |
4.8% | 2.6% | |
9.5 | 9.7 | |
2 days ago | 1 day ago | |
Mustache | JavaScript | |
Apache License 2.0 | 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.
argo-helm
-
Introducing ArgoCD: A GitOps Approach to Continuous Deployment
kubectl create namespace argocd helm repo add argo https://argoproj.github.io/argo-helm helm repo update helm install argocd argo/argo-cd --namespace argocd
-
2- Your first ARGO-CD
We will use Helm to install Argo CD with the community-maintained chart from argoproj/argo-helm because The Argo project doesn't provide an official Helm chart. We will render thier helm chart for argocd locally on our side, manipulate it and overrides its default values, and also we can helm lint the chart and templating to see if there is some errors or not, We gonna use the chart version 5.50.0 which matches appVersion: v2.8.6 you can find all details for the chart and also we gonna override some values @ default-values.yaml
-
Having an issue connecting to git repo configured through helm using ssh private key
resource "helm_release" "argocd" { name = "${var.environment}-argocd" namespace = "${var.environment}-argocd" create_namespace = true repository = "https://argoproj.github.io/argo-helm" version = "${var.helm_version}" chart = "argo-cd" set { name = "server.service.type" value = "LoadBalancer" } set { name = "server.service.loadBalancerIP" value = "${var.loadBalancerIP}" } values = [ <<-YAML --- global: image: tag: "${var.image_tag}" configs: repositories: gitops-homelab: url: [email protected]:myprivaterepo/gitops-homelab.git name: private-repo type: git sshPrivateKey: file("${path.module}/sa_keys/private/${var.environment}_id_rsa") server: extraArgs: - --insecure YAML ] } output "file_location" { value = file("${path.module}/sa_keys/private/${var.environment}_id_rsa") }
-
Issue with helm_release on terraform destroy
"argo-cd" = { repository = "https://argoproj.github.io/argo-helm", chart = "argo-cd", namespace = "argocd" values_file = templatefile("./values/argocd.yml", { ingress_scheme = "internal" #internet-facing or internal elb_name = aws_lb.this["${local.name}-int-a"].name })
-
How to Install ArgoCD using Helm through Terraform
repository = "https://argoproj.github.io/argo-helm" chart = "argo-cd" namespace = "argo" version = "5.34.5"
- How to determine ordering in a bunch of helm sub charts?
-
Dump Kustomize with 20 lines of TypeScript
I think your example with the ArgoCD Helm chart says it all. It can get incredibly complicated, and I had tremendous trouble getting it working, it broke all the time, getting the indentation right was a nightmare ... very unpleasant experience. I mean look at that chart, the authors have to constantly specify the indentation level everywhere.
-
Can I use a values.yaml file with my argocd application?
plugin: name: argocd-vault-helm env: - name: release_name value: argocd - name: chart_name value: argo-cd - name: chart_repo value: https://argoproj.github.io/argo-helm - name: chart_version value: 5.17.1 - name: chart_values value: -f applicationset.yaml -f configs.yaml -f controller.yaml -f dex.yaml -f redis.yaml -f reposerver.yaml -f server.yaml -f notifications.yaml - name: args value: --include-crds
-
Templating the Matrix
Another folder I want to discuss shortly is the Terraform folder. This project was installed by terraform basically but it can deployed easily with simple helm installation of ArgoCD . In the next attachment we can see the relevant values neccesary to apply our ArgoCD system : values-override.tpl
-
Injecting secrets from Vault into Helm charts with ArgoCD
Finally, we have to install ArgoCD from the official Helm Chart but with extra configuration that provides modifications required to install Vault plugin via sidecar container.
cdk8s
-
K8s Service Meshes: The Bill Comes Due
Any, it doesn’t matter which as long as you don’t have to count spaces in yaml by hand.
If you really want a concrete recommendation try https://cdk8s.io/.
- Why the fuck are we templating YAML? (2019)
- Cdk8s: Kubernetes native apps and abstractions using object-oriented programming
-
10 Ways for Kubernetes Declarative Configuration Management
CDK8s - CDK8s is used to define Kubernetes resources and applications. CDK8s uses the high-level abstraction concept called constructs to represent various Kubernetes resources such as deployments, services, and configurations. Developers can write code in programming languages like TypeScript, Python, and Java, and CDK8s will translate this code into standard Kubernetes YAML manifests that can be directly applied to a Kubernetes cluster.
-
I built a React renderer for Kubernetes configurations
Have you looked into https://cdk8s.io/? I've been using it for a while now, and I must admit TypeSript does help a lot. Not really sold on your React syntax yet, but well done nevertheless
-
How are most EKS clusters deployed?
I, personally, prefer to wrap it in CDKTF/CDK8S in golang and manage with Crossplane Composition Functions, but your mileage may vary. I'm finding way too bugs in CDK's... but it calms me a bit, that Amazon folks actually looking into it.
-
Editing Badly formatted yaml file
Have you looked into cdk8s? That will let you get away from dealing with yaml and let you use code instead. Helm included.
-
kpt, cue, ... Your experiences?
My favorite is cdk8s + typescript.
- Cloud Development Kit for Kubernetes
-
Dump Kustomize with 20 lines of TypeScript
What about https://cdk8s.io/?
What are some alternatives?
charts - Public helm charts
helmfile - Deploy Kubernetes Helm Charts
cp-helm-charts - The Confluent Platform Helm charts enable you to deploy Confluent Platform services on Kubernetes for development, test, and proof of concept environments.
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
argo-cd - Declarative Continuous Deployment for Kubernetes
terraform-cdk - Define infrastructure resources using programming constructs and provision them using HashiCorp Terraform
helm-charts - OpenSourced Helm charts
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
charts - OpenEBS Helm Charts and other utilities
jsonnet - Jsonnet - The data templating language
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
kubernetes-the-hard-way - Bootstrap Kubernetes the hard way. No scripts.