helm-charts VS charts

I have no clue of what is wrong. The applicationset yaml looks like (somewhat cut-down): apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet metadata: name: myjenkins namespace: argocd spec: generators: - list: elements: - namespace: "development" ingressHostName: "myjenkins-dev.scs.domain" limitsMemory: "12Gi" template: metadata: name: myjenkins spec: destination: namespace: '{{namespace}}' server: https://kubernetes.default.svc project: default syncPolicy: {} sources: - chart: jenkins repoURL: https://github.com/jenkinsci/helm-charts/tree/main/charts targetRevision: 4.3.9 helm: releaseName: myjenkins parameters: - name: extraLabels value: slice1 - name: controller.resources.limits.cpu value: '8' - name: controller.resources.limits.memory value: '{{limitsMemory}}' valueFiles: - $values/deployments/jenkins/global/common.values - $values/deployments/jenkins/global/shared-libs.values - $values/deployments/jenkins/global/job-dsl-seed.values - $values/deployments/jenkins/global/ssh-credentials.values - $values/deployments/jenkins/global/kubernetes-cloud.values - repoURL: 'ssh://[email protected]:29418/kubernetes' targetRevision: master ref: values

Here is what I'm deploying.. I have a very small GKE cluster up and running right now with terraform. I'm on a budget, so I'm trying to containerize as many of the services we need for development as possible. I am using this Jenkins helm chart for deployment: https://github.com/jenkinsci/helm-charts/blob/main/charts/jenkins/README.md

I've updated my post with the error logs and some descriptions. The "Additional Agents" thing is part of the Helm chart. The Adding Pod Templates Using additionalAgents section of the Helm Chart's README gives an example of how to declare them. I initially tried using a direct copy of the example in the README (adapted to use with the Ansible module) but that displayed roughly the same behaviour

https://github.com/jenkinsci/helm-charts/tree/main/charts/jenkins Using offical chart

I'm using this prometheus helm chart.

I did this using the incubator/raw chart ( https://github.com/helm/charts/tree/master/incubator/raw ), by creating a k8s Job.

I've installed Prometheus operator 0.34 (which works as expected) on cluster A (main prom)Now I want to use the federation option,I mean collect metrics from other Prometheus which is located on other K8S cluster B

So I am using the helm chart stable/traefik to deploy a reverse proxy to my cluster. I need to customise it beyond what is possible with the variables I can set for the template.

It may be that we just migrated to Bitnami's chart when the old "stable" chart was deprecated

Edit: I'm using Postgresql Stable Chart version 5.3.10

I'm using the official stable/prometheus-operator chart do deploy Prometheus with helm.

I am using using https://github.com/helm/charts/tree/master/stable/airflow helm chart and building v1.10.8 puckle/docker-airflow image with kubernetes installed on it and using that image in the helm chart,But I keep getting