headyj

Same here. This is quite annoying and dangerous as it can wipe all resources in the related argocd application as no error code is output. Any news or workaround to...

@ArtemShevelyukhin maybe I found a workaround for that problem, changing a bit my command from: ``` helm template $ARGOCD_APP_NAME -n $ARGOCD_APP_NAMESPACE ${ARGOCD_ENV_HELM_ARGS} . | argocd-vault-plugin generate - ``` to: ```...

@reasonerjt I am personally facing the same issue with the latest version of velero (v1.13.2). Seems that it is happening sporadically with different volumes (sometimes our daily backup goes well,...

@aantn I just had the same issue on v1.11.0. I tried to run the following command on both `prometheus-workload-loader` and `debug-build-anil-repo` branches and had the same error on both (with...

Yep, I do (sorry I had to anonymise most of the names :-( ): ``` [14:55:09] INFO Listing pods for namespace=namespace-1 and label_selector=app.kubernetes.io/instance=namespace-1,app.kubernetes.io/name=my-helm,name=namespace-1-pod-1 __init__.py:118 [14:55:10] DEBUG Gathering PercentileCPULoader metric for...

> Did you include all the matching log lines or only some of them? I am particularly interested in the last log line before the exception. Actually I missed only...

Actually it's a Rollout (from Argo Rollouts) but it's very close to a Deployment and I don't think it makes a difference. The content of `spec.selector` is quite standard: ```...

Yes I can confirm that it is working with Rollouts :+1:

@aantn I am not sure if is the same issue, but on my side recommendation is also missing for some sidecars with regular deployments (not using Dapr at all): ```...

The exact same result, I'm afraid :-( This is the command I executed: ``` python3.12 krr.py simple --logtostderr -c my-cluster --namespace argocd --verbose -m prometheus -p http://localhost:9090 -f json --history_duration...