argoproj / argo-helm Goto Github PK

View Code? Open in Web Editor NEW

1.6K 38.0 1.8K 43.23 MB

ArgoProj Helm Charts

Home Page: https://argoproj.github.io/argo-helm/

License: Apache License 2.0

Shell 6.04% Mustache 93.96%

helm-charts argoproj

argo-helm's Introduction

Argoproj - Get stuff done with Kubernetes

What is Argoproj?

Argoproj is a collection of tools for getting work done with Kubernetes.

Argo Workflows - Container-native Workflow Engine
Argo CD - Declarative GitOps Continuous Delivery
Argo Events - Event-based Dependency Manager
Argo Rollouts - Progressive Delivery with support for Canary and Blue Green deployment strategies

Also argoproj-labs is a separate GitHub org that we setup for community contributions related to the Argoproj ecosystem. Repos in argoproj-labs are administered by the owners of each project. Please reach out to us on the Argo slack channel if you have a project that you would like to add to the org to make it easier to others in the Argo community to find, use, and contribute back.

Community Blogs and Presentations

Project specific community blogs and presentations are at

Adopters

Each Argo sub-project maintains its own list of adopters. Those lists are available in the respective project repositories:

Contributing

To learn about how to contribute to Argoproj, see our contributing documentation. Argo contributors must follow the CNCF Code of Conduct.

For help contributing, visit the #argo-contributors channel in CNCF Slack.

To learn about Argoproj governance, see our community governance document.

Project Resources

Argo Community Meeting Calendar
- ICS file
Argo GitHub: https://github.com/argoproj
Argo website: https://argoproj.github.io
Argo Slack: https://argoproj.github.io/community/join-slack

argo-helm's People

Contributors

Stargazers

Watchers

Forkers

dschmidtdev louis-murray sagansystems vshimoda dln akranga divolgin ishitatsuyuki vosmith solebrity krueladin seungweonpark jmcarp alexeldeib alexmt paulvanstaden vaibhavpage dtaniwaki nstott raanand-home coreplane slobo1c mura-s wuxi-nextcode yurrriq e-mon hickey jfouchard cw-ozaki anhdat sherwoodwt naseemkullah pbrit acaisoft donaldrauscher l15k4 tompowell-dd mattmelgard paguos paperspace razvan-wework ninech trawler gincoinc omerkahani yann-soubeyrand keleustes carsonoid leoxiongideahq gpaul saintaxl chocopowwwa quantopian jdeprin sjclement spothero cdickens-hbc jbehling antoinedao fairwindsops tomhellier alantang888 nouseforaname ctc-oss username1366 abhishekjiitr masondaven jeroenlanckmans 3loc razaj92 ingvarch cryptobioz muzzylogic pcantea davidkarlsen cna-bot alinbalutoiu igaskin daytong ch-stark mikeling lawliet89 tylerauerbeck rparsonsbb mcanevet camptocamp pabrahamsson ealiass falloutdurham geol86 chrissng carlosjgp rkt2spc mjs2600 bergur88 cabrinha tgauweiler opensean rarguellof jsolbrig

argo-helm's Issues

Support initContainers for custom tooling in the repo-server

One of the documented ways to install custom tooling for the repo-server is via the use of volume mounts coupled with initContainers for actually downloading the binaries.

https://argoproj.github.io/argo-cd/operator-manual/custom_tools/

Can we add support for either adding initContainers for the repo server?

argocd chart does not include ClusterRole and ClusterRoleBinding for argocd-server.

Describe the bug
Chart does not include the ClusterRole/argocd-server or ClusterRoleBinding/argocd-server as is found in https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml

To Reproduce
Steps to reproduce the behavior:

Install from chart
Deploy any application to the default cluster to a new namespace
Click on pod and you can not see manifest or logs

Expected behavior
If the ClusterRole and ClusterRoleBinding are present, manifest and logs will be readable.

Additional context
This is a quick fix I will try to PR later this weekend.

Link broken for argo-events README.md

https://github.com/argoproj/argo-helm/blob/master/charts/argo-events/README.md

While following through the document, link is broken: https://blade-git.blackrock.com/cloud-native/roles

Would you fix?

Add a README which explains what argo-helm is?

Argo service account admin binding

In the main project's readme, it says you need to create a rolebinding to the admin clusterrole in order for the pods to be able to work as part of a DAG. It seems like there are some roles and bindings setup by the helm chart, but this binding was not created. Should we create this binding as part of the base chart, or possibly add some info to the README here about it? Happy to contribute this simple change just not sure if it's something I'm missing or an actual improvement to be made.

The command I ran to create the binding was:
kubectl create rolebinding default-admin --clusterrole=admin --serviceaccount=argo:default --namespace argo

I am using a custom namespace called "argo" just for argo.

Workflow CRD is not in the chart

Is this a feature request of a bug
Bug (maybe feature request)

What happened
I installed argo using the chart. Workflows would not run because CRD was missing.

What should happen
CRD resource should be created when installing chart

Add argo helm repo to hub.helm.sh

As per https://github.com/helm/hub/blob/master/Repositories.md ...I think it would be a good idea so that more users can discover the argo charts.

workflow-controller fails to obtain v1alpha1.WorkflowTemplate resource

Describe the bug
Deploying argo 0.6.1 using this chart boots up workflow controller that immediately fails.

To Reproduce
Steps to reproduce the behavior:

deploy argo with default values
kubectl logs -f pod/workflow-controller-5994bd4bbd-jx7zk

Expected behavior
workflow controller should boot up properly but instead following happens :

time="2019-10-25T13:56:54Z" level=info msg="workflow controller configuration from argo-staging-workflow-controller-configmap:\ncontainerRuntimeExecutor: docker\nartifactRepository:\n"
time="2019-10-25T13:56:54Z" level=info msg="Persistence configuration disabled"
time="2019-10-25T13:56:54Z" level=info msg="Starting workflow TTL controller (resync 20m0s)"
time="2019-10-25T13:56:54Z" level=info msg="Workflow Controller (version: v2.4.2) starting"
time="2019-10-25T13:56:54Z" level=info msg="Workers: workflow: 8, pod: 8"
time="2019-10-25T13:56:54Z" level=info msg="Watch Workflow controller config map updates"
time="2019-10-25T13:56:54Z" level=info msg="Detected ConfigMap update. Updating the controller config."
time="2019-10-25T13:56:54Z" level=info msg="workflow controller configuration from argo-staging-workflow-controller-configmap:\ncontainerRuntimeExecutor: docker\nartifactRepository:\n"
time="2019-10-25T13:56:54Z" level=info msg="Persistence configuration disabled"
E1025 13:56:54.844483       1 reflector.go:126] github.com/argoproj/argo/workflow/controller/controller.go:157: Failed to list *v1alpha1.WorkflowTemplate: the server could not find the requested resource (get workflowtemplates.argoproj.io)

Add badge support

Is your feature request related to a problem? Please describe.
Editing the argocd-cm post deployment and adding the additional data field:
statusbadge.enabled: "true"

allows us to access badge status via
https://argourl/api/badge?name=foobar

It would be neat if we could do this via a values flag instead of post deployment.

Describe the solution you'd like
We could add a boolean value that adds statusbadge.enabled to the underlying cm.

Update ArgoCD chart to support 1.2.0

Is your feature request related to a problem? Please describe.
New version of ArgoCD is released! Additionally, the new version of ArgoCD requires a new annotation on ConfigMap resources.

Describe the solution you'd like
Bump version, do some testing and cut a new release.

Additional context
Argo CD config maps must be annotated with app.kubernetes.io/part-of: argocd label.

Chart version in Helm repository is not up to date

Describe the bug

The chart version in the Helm repository is 0.5.4 and not 0.6.x as expected.
Possibly similar to: #86
Is there a CI job or a pipeline that can be triggered automatically for each new chart version?

To Reproduce
Steps to reproduce the behavior:

❯ helm repo list  
NAME    URL
argo    https://argoproj.github.io/argo-helm
❯ helm repo update
❯ helm fetch argo/argo-cd 
❯ ls   
argo-cd-0.5.4.tgz

Expected behavior
I exptect the downloaded version to be 0.6.x.

invalid field "namspace"

Generating templates results in configurations that kubectl won't apply:

$ helm repo add argo https://argoproj.github.io/argo-helm
"argo" has been added to your repositories
$ helm fetch argo/argo --untar --untardir ./charts/argo
$ helm template ... --output-dir=manifests ./charts/argo/
wrote manifests/argo/templates/workflow-controller-config-map.yaml
wrote manifests/argo/templates/ui-sa.yaml
[...]
$ kubectl apply --recursive --filename ./manifests/argo/
[...]
error: error validating "manifests/argo/templates/ui-sa.yaml": error validating data: ValidationError(ServiceAccount.metadata): unknown field "namspace" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta; if you choose to ignore these errors, turn validation off with --validate=false

due to what looks like a typo in e.g. https://github.com/argoproj/argo-helm/blob/master/charts/argo/templates/ui-sa.yaml#L5 among others.

Syntax error when deploying argo-cd helm chart

When deployment argo-cd the following error shows up:

Helm template failed. Error: parse error in "argo-cd/templates/argocd-server-service.yaml: template: argo-cd/templates/argocd-server-service.yaml:13: unexpected {{end}} : exit status 1

Deploying to custom namespace no longer works with v1.0.0 of argo-helm chart

Describe the bug
Installing the v1.0.0 argo-cd helm chart causes the argocd-server, argocd-dex-server, and argocd-application-controller to start crash looping because it cannot find the argocd-cm configuration map.

I think this is because this line of code in util/settings/settings.go expects that the app.kubernetes.io/part-of is set to argocd, I propose we need to update the helm chart to not change the part-of section of any of the manifests.

    app.kubernetes.io/part-of: argocd-ref

To Reproduce
Configure the argocd chart to install to a namespace other than argocd, and configure the .Values.nameOverride to be argocd-ref.

Expected behavior
The argocd-dex-server, argocd-server, and argocd-application-controller all start up successfully.

Defning a a custom health check not possible

Is your feature request related to a problem? Please describe.
According to the documentation you should be able to add resource.customizations to argocd-cm to define a custom resource health checks. The helm chart does not allow this.

Describe the solution you'd like
Add the option in config in values.yaml to add resource customizations. This will be rendered in argocd-cm like the other options do.

Describe alternatives you've considered
Patching argocd-cm from kubectl, not an option imo.

Invalid json in `_sensor-crd.tpl`

Try to clone and install argo-events chart getting:

k logs -f argo-events-apply-sensor-crd-ztz86
error: error parsing STDIN: json: line 0: invalid character '}' looking for beginning of object key string

and indeed _sensor-crd.tpl contains body

{
  "apiVersion": "apiextensions.k8s.io/v1beta1",
  "kind": "CustomResourceDefinition",
  "metadata": {
    "name": "sensors.argoproj.io"
  },
  "spec": {
    "group": "argoproj.io",
    "names": {
      "kind": "Sensor",
      "listKind": "SensorList",
      "plural": "sensors",
      "singular": "sensor",
    },
    "scope": "Namespaced",
    "version": "v1alpha1"
  }
}

that produces parse error: Expected another key-value pair at line 14, column 5

Repo-server for Argo-CD 1.2 and newer is incomplete

The repo server now -has- to have volume mounts for the ssh known hosts and tls certs: https://github.com/argoproj/argo-cd/blob/master/manifests/install.yaml#L2832

The current charts do not include these mounts by default.

Allow Setting of Image Pull Policy

Problem: I ran into a situation in which we would like to leverage the Argo helm chart in an air gapped environment. The machine we will be deploying to do not have external connections and are unable to pull images. Instead the images are pre-loaded on the the nodes.

Solution:
See: Enable imagePullPoicy consistently across all helm charts.

Upgrade ArgoCD from v0.12.3 to v1.1.2 failed

Describe the bug
Upgrade ArgoCD from v0.12.3 to v1.1.2 failed

To Reproduce
Steps to reproduce the behavior:

replace image tag v0.12.3 to v1.1.2 in helm/argocd/values.yaml

diff --git a/helm/argocd/values.yaml b/helm/argocd/values.yaml
index 4487af3..385b33c 100644
--- a/helm/argocd/values.yaml
+++ b/helm/argocd/values.yaml
@@ -1,17 +1,17 @@
 applicationController:
   image:
     repository: argoproj/argocd
-    tag: v0.12.3
+    tag: v1.1.2
     pullPolicy: Always

 server:
   image:
     repository: argoproj/argocd
-    tag: v0.12.3
+    tag: v1.1.2
     pullPolicy: Always
   uiInitImage:
     repository: argoproj/argocd-ui
-    tag: v0.12.3
+    tag: v1.1.2
     pullPolicy: Always
   extraArgs:
     - --insecure
@@ -19,7 +19,7 @@ server:
 repoServer:
   image:
     repository: argoproj/argocd
-    tag: v0.12.3
+    tag: v1.1.2
     pullPolicy: Always

 dexServer:
@@ -29,7 +29,7 @@ dexServer:
     pullPolicy: Always
   initImage:
     repository: argoproj/argocd
-    tag: v0.12.3
+    tag: v1.1.2
     pullPolicy: Always

helm repo update

Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "argo" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.

helm upgrade --install -f helm/argocd/values.yaml argocd --namespace=argocd argo/argo-cd

UPGRADE FAILED
Error: YAML parse error on argo-cd/templates/argocd-secret.yaml: error converting YAML to JSON: yaml: line 13: could not find expected ':'
Error: UPGRADE FAILED: YAML parse error on argo-cd/templates/argocd-secret.yaml: error converting YAML to JSON: yaml: line 13: could not find expected ':'

Expected behavior
I have upgraded argo-cd successfull in lab environment in 2019-09-09, but failed today

Screenshots

Additional context
I found that line with syntax error, (commit 2days ago)
https://github.com/argoproj/argo-helm/blob/master/charts/argo-cd/templates/argocd-secret.yaml#L14

Publish v4.2.0 of Argo

@alexmt @alexec Gentlemen, could you please hit scripts/publish.sh?

Thank you.

Argo-CD v0.12.0 needs Redis?

I've been using the Helm Chart for v0.11.2 version of Argo-CD, and attempted to update all image tags to v0.12.0 but getting an error on the application controller;

2019/03/25 04:22:44 cache: Get key="app|managed-resources|<appname>|0.12.0" failed: dial tcp: lookup argocd-redis on 172.20.0.10:53: no such host

Do we have a new requirement which should be added to a requirements.yaml?

Helm charts are pending release

Describe the bug
The helm charts are pending release. Argo chart v 0.5.0 was merged to master 15 days ago. Is there a CI pipeline releasing these charts?

To Reproduce
Steps to reproduce the behavior:

Add Argo-helm charts repo. helm repo add argo https://argoproj.github.io/argo-helm
Run helm update
Install Argo chart. Features like containerRuntimeExecutor were merged to master a month ago is not available.

Expected behavior
Charts must be released on schedule to mirror chart versions in master.

Instillation fails with "Error: no available release name found"

I am following the instillation guide here: link
But when I run helm install argo/argo-events I get the error:
Error: no available release name found

Ingress for argocd not working with new helm chart

Describe the bug
When enabling ingress it maps to port "server" and ingress-controller in our case traefik, doesn't resolve anymore link to service. Ports on service are named "http" and "https". We use http intracluster as we are using a secure CNI network. We would expect ingress to point to "http" port.
Changing ingress from port "server" to port "http" fixes the bug.

Expected behavior
The ingress generated by the chart should enable connectivity to the UI without having to be fixed manually.

Can not get admin psw via kubectl

Can not get psw via kubectl in:

https://github.com/argoproj/argo-helm/blob/master/charts/argo-cd/templates/NOTES.txt

kubectl get pods -n argocd -l app.kubernetes.io/name={{ include "argo-cd.name" . }}-server -o name | cut -d'/' -f 2

error: name cannot be provided when a selector is specified

USE:
kubectl get pod -n argocd -l app.kubernetes.io/name=argo-cd-server -o jsonpath="{.items[0].metadata.name}"

kubectl get pod -n argocd -l app.kubernetes.io/name=argo-cd-server -o name | cut -d'/' -f 2

Service argocd-metrics targetting wrong pods

Service argocd-metrics has a labelSelector for argocd-server not argocd-application-controller.

When looking at the argocd-metrics manifest for argo-cd you can see it selects pods with label selector app.kubernetes.io/name: argocd-application-controller.

In the argo-cd helm chart it has a label selector effectively app.kubernetes.io/name: argocd-server.

argocd-application-controller is exposing the metrics.

Workflows CRD should be installed as a `post-install` rather than `pre-install` step

This is probably a niece use-case that most won't run into, but before the changes to install CRD along with the rest of that chart were merged, we were installing/upgrading using our own chart, with the CRD one of the resources installed.

When switching over to the new official 0.1.1 chart, ~~helm ran the pre-install hook, "creating" the already existing CRD, then proceeded to delete as part of the cleanup.~~ the pre-install hook did not run because it was an upgrade.

Running this as a post-upgrade hook would seemingly have solved the problem. The CRD should be applied as part of a post-install and post-upgrade hook so that it is correctly updated should anything change.

Installation fails with "CRD already exists" error

This is on version 0.3.1

helm install fails with the following error:
Error: release argo failed: customresourcedefinitions.apiextensions.k8s.io "workflows.argoproj.io" already exists

I have verified that the CRD is not present with kubectl get crd prior to running helm install.

Add role aggregations to argo-events

Is your feature request related to a problem? Please describe.
Argo has role aggregations for the workflow CRD to be added to view/edit/admin. The argo-events project does not have this.

Describe the solution you'd like
Add role aggregations to argo-events similar to https://github.com/argoproj/argo-helm/blob/master/charts/argo/templates/workflow-aggregate-roles.yaml

[charts/argo-cd] Enable override of tls.crt and tls.key

The tls.crt and tls.key appear to be autogenerating in the argocd-secret secret. It would be great if we could override this from the values.yaml.

Argo chart uses hardcoded names for service accounts

Argo chart uses hardcoded 'argo' and 'argo-ui' as a service account names. Names are specified in values.yaml file.

This is useful to let user configure service account name, but by default chart should include Release.Name into service account name. Otherwise second helm install fails due to name conflict.

Running Argo UI on non-root path

I'm trying to run Argo UI on cluster (as a dependency), but not on subdomain, but on relative path (like dev.cluster.io/argoui), but it looks like helm charts weren't designed to be used like that.
Reason no. one, ui-ingress.yaml:

{{- range .Values.ui.ingress.hosts }}
- host: {{ . }}
  http:
    paths:
      - backend:
          serviceName: {{ $serviceName }}
          servicePort: {{ $servicePort }}
{{- end -}}

no place for path paramter.

I managed to make it happen partially by disabling default ingress and adding custom one to application's chart, and argo-ui pod does respond on desired url, but tries to fetch js file from root path (<script type="text/javascript" src="main.8cdedde4853950928afa.js"></script></body>), likely because BASE_HREF points on /

And that's because it's value is set in ui-development.yaml, but it's hardcoded

Wouldn't it be nice to:

allow to set parameter path in http.paths map
make BASE_HREF variable
?

Simpler CRD creation

Hi,

Just need an explanation why a job is used to created the CRD in Argo chart instead of using a simple crd.yaml file with all the declarations.

Thanks

BTW: there is a duplicate definition of workflow-crd-json, in _helpers.tpl and in _workflow-crd.tpl

[argo] Add securityContext to ui and controller

Would be nice to remove as much privileges, force readonly FS, run as non root and so on.

argo-cd chart argocd-rbac-cm defaults cause issues depending on git setup

Describe the bug
This line https://github.com/argoproj/argo-helm/blob/master/charts/argo-cd/values.yaml#L336 is applied by default. Depending on the users Git setup it may not be applicable and could cause issues with permissions in the default setup. The base values in the chart should target the general user.

To Reproduce
Steps to reproduce the behavior:

deploy chart with default settings
describe argocd-rbac-cm has example settings.

Expected behavior
If the user does not specify a policy it should be left blank.

Expose Type in Server Ingress

To set up ArgoCD Server behind a Load Balancer, the service must be type LoadBalancer. The service template (argocd-server-service.yaml) doesn't include a way to set the type based on a values file.

I'd like to be able to set the type using a values file. The only workarounds I've found for this have been to either fork the repo, modify the one template file and reference the forked repo, or to call kubectl patch to set the type after creation as suggested here: https://argoproj.github.io/argo-cd/getting_started/#service-type-load-balancer.

Here's an example of what the fix might look like:

# argocd-server-service.yaml

apiVersion: v1
kind: Service
metadata:
  ...
spec:
  type: {{ .Values.server.serviceType }}
  ports:
     ...
  selector:
    app.kubernetes.io/name: {{ include "argo-cd.name" . }}-server

Use stable argo chart

Argo CD helm chart is currently using the v0.12.3 tag. Can we update the helm chart to bring it to the stable one ?

most recent version of helm chart is not on https://argoproj.github.io/argo-helm

most recent chart up is from june

Allow parameterization of credentials

Is this a feature request or a bug?
Feature request

What happened
The only way to remove or change artifact repository credentials is by updating the configmap once the chart is installed

What you expect to happen
I would like to be able to override the credentials values or remove credentials altogether (argoproj/argo-workflows#797 allows for configurations without credentials)

Add keyPrefix option in artifactRepository.s3

Per this documentation, you can specify a keyPrefix for your artifacts. Requesting we simply add some logic for this in workflow-controller-config-map.yaml. Thanks!

Migrate charts publishing workflow to argo v2

Directory .argo contains workflow which publishes charts to gh-pages branch. We need to migrate workflow to argo v2

Argo CD not accessible from HTTPS

Describe the bug
I install Argo CD using Helm. When I try access this not are targeting to argocd-server:

curl -k https://argocd.example.com/                                                                                                                                           
default backend - 404

To Reproduce

helm repo add argo https://argoproj.github.io/argo-helm
helm repo update

kubectl create namespace argo-cd

helm install argo/argo-cd \
  -n argo-cd \
  --namespace argo-cd \
  --set ingress.enabled=true \
  --set ingress.hosts={argocd.example.com}

Additional context

I believe that port 443 is not properly configured.

kubectl get ingress -A                                                                                                                                                        
NAMESPACE       NAME            HOSTS                 ADDRESS        PORTS     AGE
argo-cd         argocd-server   argocd.example.com    10.108.54.49   80        6m29s
cattle-system   rancher         rancher.example.com   10.108.54.49   80, 443   3h24m
kube-monitor    grafana         grafana.example.com   10.108.54.49   80        3h

Helm install has broken for us.

We use helm to build/tear down our environment all the time.

Recently the helm install on master has broken.

I've attached some lines that the controller is dumping...

0117 17:29:55.274599 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:29:56.272602 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:29:56.276121 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:29:57.274360 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:29:57.277970 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:29:58.276206 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:29:58.280216 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:29:59.278189 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:29:59.281652 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:00.287614 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:00.289346 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:01.289243 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:01.291151 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:02.291323 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:02.292586 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:03.292541 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:03.293369 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:04.294185 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:04.295126 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:05.295975 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:05.297012 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:06.298821 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:06.298821 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:07.300292 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:07.301428 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:08.302092 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:08.303059 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:09.303328 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:09.304809 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:10.310519 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:10.310520 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:11.311866 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:11.312970 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:12.313753 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:12.314856 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:13.315269 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:13.316745 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:14.317286 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:14.318570 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:15.319779 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:15.320160 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:16.321307 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:16.323028 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:17.324022 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:17.324592 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:18.326799 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:18.326865 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:19.329399 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:19.330405 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:20.336846 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:20.337320 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:21.339614 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:21.339617 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:22.343184 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:22.343204 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:23.345069 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:23.349065 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:24.346785 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:24.351326 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:25.350349 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:25.354277 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:26.352533 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:26.357584 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:27.353981 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:27.360194 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:28.357446 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:28.362621 1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:29.358871 1 reflector.go:205] github.com/argoproj/argo/workflow/ttlcontroller/ttlcontroller.go:75: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

E0117 17:30:29.364760       1 reflector.go:205] github.com/argoproj/argo/workflow/controller/controller.go:143: Failed to list *unstructured.Unstructured: the server could not find the requested resource (get workflows.argoproj.io)

[argo] Add value to set resources (memory+cpu)

Both for UI and workflow-controller.

When argocd manages argocd argocd-secret is wiped when no webhooks config is provided

Describe the bug
When we set up argocd to manage itself through an application with helm it quickly stops working altogether as it wipes out admin.password, admin.passwordMtime and server.secretKey (along with all other keys).

This is because when no webhooks configuration is provided in values.yaml this template is rendered as this:

apiVersion: v1
kind: Secret
metadata:
  name: argocd-secret
  labels: 
    ...
type: Opaque
data:

Meaning, here data is null can't be diffed with existing secret by Kubernetes and completely replaces data. Changing it to simply an empty object (data: {}) works fine.

For some reason this didn't use to be a problem in version 0.2.2 (Argo-CD 0.12).

A possible workaround is to put fake webhook secret so that data isn't null.

Expected behavior
Argocd should take over itself fine.

Additional context
Add any other context about the problem here.

Add Argo-Events Helm chart

we should add a Helm chart for the argo-events project

[charts/argo-cd] Adding namespacing

Is your feature request related to a problem? Please describe.
It is frustrating that helm deployments of Argo can't target a different namespace.

Describe the solution you'd like
Can we add namespace to the definition of each component?
E.g.

apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: argocd-application-controller
  namespace: {{ .Release.Namespace }}

Helm Versions

Is your feature request related to a problem? Please describe.
Things break for our development team when helm chart version increases.

Describe the solution you'd like
Create multiple versions of the chart that one can choose to install.

Describe alternatives you've considered
Upgrading every time the helm chart version increases.

Additional context
We have a fairly decent sized development team and everyone has their own special snowflake environment. Some use docker for desktop, some use micro k8s. Whenever there is an upgrade to Argo, it's hit or miss whether the workflow engine will work for everyone on the team. It'd be nice to downgrade and not lose velocity if the latest doesn't work. Then upgrade when we get a chance.

argo events chart uses hard-coded values?

Any reason why these Helm charts have so many hard-coded values? The Argo events one seems to really want to install itself under the "argo-events" namespace, which doesn't work for me:

https://github.com/argoproj/argo-helm/blob/master/charts/argo-events/templates/argo-events-cluster-roles.yaml#L12

You guys are aware of values.yaml and how yon can write {{.Values.namespace}} and such, right?

oidc.config not supported

In the SSO configuration documentation for argo-cd it mentions that you can use a Bundled Dex OIDC provider or Existing OIDC provider.

The description is as follows:

Existing OIDC provider - use this if you already have an OIDC provider which you are using (e.g. Okta, OneLogin, Auth0, Microsoft), where you manage your users, groups, and memberships.

This provider is not supported in the argo-cd helm chart.

Additionally argocd-cm.yaml documentation mentions that an url config value is required when using SSO. https://github.com/argoproj/argo-cd/blob/master/docs/argocd-cm.yaml#L7

argoproj / argo-helm Goto Github PK

argo-helm's Introduction

Argoproj - Get stuff done with Kubernetes

What is Argoproj?

Community Blogs and Presentations

Adopters

Contributing

Project Resources

argo-helm's People

Contributors

Stargazers

Watchers

Forkers

argo-helm's Issues

Recommend Projects

Recommend Topics

Recommend Org