Taras Bondarchuk

@helenabutowatcisco many thanks for the instructions! Worked for me even with external cluster in another account, just had to create argocd-manager role in external account, add it to `aws-auth` and...

Looks like IRSA roles work even with 1.6.2 images. Found out while experimenting and switching between latest and 1.6.2. I suspect that after adding SA annotation with role name pods...

using hooks works perfectly for deployment but there is no hook for `render` so if I run `devspace render` while secrets are not decrypted yet - it shows warning and...

I've just tested and it doesn't seem to be possible to overwrite DEVSPACE_NAMESPACE with vars, top-level or in profile. I suppose all Predefined Variables are not editable so it should't...

Trying to think about usecase for profile activation based on custom var defined in top level `vars`: source env doesn't make sense as we can can already activate directly from...

might be related, but not sure: after bootstraping new cluster from existing repo, chart was first stuck in `install retries exhausted ` and then become `Helm uninstall failed: uninstall: Release...

Reproduced with incorrect values for helm chart, so helm template was failing locally but HR status was `Helm uninstall failed: uninstall: Release not loaded` I suspect its because of my...

I suspect it might be caused by two reconciliation happening at the same time: one set by HelmRelease's interval, second triggered by source update. I've seen the same issue but...

I've noticed that `helm list` does not show release in question in that situation but pods are actually running. Also, I've tried to remove last helm secret for release and...

@HaveFun83 Thanks, now I've learned something new about helm:) Guess my previous comment should say: "helm release in question is not in `deployed` or `failed` state"