argo-helm
Killed by Google
argo-helm | Killed by Google | |
---|---|---|
20 | 2,312 | |
1,598 | 2,396 | |
3.2% | - | |
9.5 | 7.0 | |
2 days ago | 8 days ago | |
Mustache | TypeScript | |
Apache License 2.0 | MIT License |
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
-
Using ArgoCD & Terraform to Manage Kubernetes Cluster
data "aws_eks_cluster_auth" "main" { name = aws_eks_cluster.main.name } resource "helm_release" "argocd" { depends_on = [aws_eks_node_group.main] name = "argocd" repository = "https://argoproj.github.io/argo-helm" chart = "argo-cd" version = "4.5.2" namespace = "argocd" create_namespace = true set { name = "server.service.type" value = "LoadBalancer" } set { name = "server.service.annotations.service\\.beta\\.kubernetes\\.io/aws-load-balancer-type" value = "nlb" } } data "kubernetes_service" "argocd_server" { metadata { name = "argocd-server" namespace = helm_release.argocd.namespace } }
-
ArgoCD: Use of Risky or Missing Cryptographic Algorithms in Redis Cache
FWIW: The Helm chart has network policy in place:
https://github.com/argoproj/argo-helm/blob/main/charts/argo-...
If you're using a CNI that supports network policy (e.g. AWS VPC CNI on EKS, Calico, etc.), I think this should more or less cover you, but I haven't personally tested it.
I think it's also probably a better practice to install "control plane" type software like Argo on a different, dedicated cluster. Argo supports this concept (and can in fact manage deployments in multiple clusters remotely). This way your main mission workloads are completely segmented from your privileged control plane software. Just as another defense-in-depth measure
-
Using ArgoCD Image Updater with ACR
resource "helm_release" "image_updater" { name = "argocd-image-updater" repository = "https://argoproj.github.io/argo-helm" chart = "argocd-image-updater" namespace = "argocd" values = [ <
-
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.
Killed by Google
- Google shuts down GPay app and P2P payments in the US
- Sending Emails to my three-year-old
-
Mathematical Optimization for Cargo Ships
With Google’s graveyard[1] growing so fast, I’m careful with new Google announcements. An API like this sounds particularly problematic to replace sometime in future.
[1]: https://killedbygoogle.com/
-
Google to shut down Google One VPN on June 20
Number 293 of killed things by Google: https://killedbygoogle.com/
- Many Searchers Want to Turn Off Google AI Overviews
-
Veo
> Google is large enough to not care about small opportunities. It ends up focusing on bigger opportunities
that result in shittier products overall. For example, just a few months ago they cut 17 features from Google Assistant because they couldn't monetize them, sorry, because these were "small opportunities": https://techcrunch.com/2024/01/11/google-is-removing-17-unde...
> all are excellent examples of Google's long term commitment to the product and constantly making things better and keeping them relevant for the market.
And here's a long list of excellent examples of Google killing products right and left because small opportunities or something: https://killedbygoogle.com/
And don't get me started on the whole Hangouts/Meet/Alo/Duo/whatever fiasco
> Sure it has shut down many small products but that is because they were unlikely to turn into bigger opportunities.
Translation: because they couldn't find ways to monetize the last cent out of them
- Bringing Project Starline out of the lab
-
Apple Introduces M4 Chip
>Google operates in China albeit via their HK domain.
The Chinese government has access to the iCloud account of every Chinese Apple user.
>They also had project DragonFly if you remember.
Which never materialized.
>The lesser of two evils is that one company doesn’t try to actively profile me (in order for their ads business to be better) with every piece of data it can find and forces me to share all possible data with them.
Apple does targeted and non targeted advertising as well. Additionally, your carrier has likely sold all of the data they have on you. Apple was also sued for selling user data to ad networks. Odd for a Privacy First company to engage in things like that.
>Google is famously known to kill apps that are good and used by customers: https://killedbygoogle.com/
Google has been around for 26 years I believe. According to that link 60 apps were killed in that timeframe. According to your statement that Google kills an app a month that would leave you 252 apps short. Furthermore, the numbers would indicate that Google has killed 2.3 apps per year or .192 apps per month.
>As for the subpar apps: there is a massive difference between the network traffic when on the Home Screen between iOS and Android.
Not sure how that has anything to do with app quality, but if network traffic is your concern there's probably a lot more an Android user can do than an iOS user tp control or eliminate the traffic.
-
Google Fit APIs get shut down in 2025, might break fitness devices
> This is proved by countless “killed by Google” incidents..
Oh, the Google's Graveyard: https://killedbygoogle.com/
-
How I migrated from Firebase to Supabase
I was already starting to feel a little cornered in the whole Google ecosystem and a bit limited with stuff like backups, vendor lock in, etc. (and you always have the obvious hanging over your head) and ultimately, I think I just find the mental model of a SQL database more intuitive compared to a NoSQL database. So I thought to myself; "the longer I leave it, the harder it'll be to make the switch".
What are some alternatives?
charts - Public helm charts
Materialize - Materialize, a CSS Framework based on Material Design
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.
babel-plugin-superjson-next - Automatically transform your Next.js Pages to use SuperJSON
argo-cd - Declarative Continuous Deployment for Kubernetes
Ryujinx-Games-List - List of games & demos tested on Ryujinx
helm-charts - OpenSourced Helm charts
tModLoader - A mod to make and play Terraria mods. Supports Terraria 1.4 (and earlier) installations
charts - OpenEBS Helm Charts and other utilities
BetterJoy - Allows the Nintendo Switch Pro Controller, Joycons and SNES controller to be used with CEMU, Citra, Dolphin, Yuzu and as generic XInput
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
kotlin - The Kotlin Programming Language.