Hidde Beydals

First of all, thank you for your detailed feature request! :sunflower: I have talked this through with @stefansedich who is going to pick it up. We agreed on a max...

@stuartpb the releases have a `.yaml` file attached to them with the bare minimum that is required to deploy the release: https://github.com/fluxcd/helm-controller/releases. Documentation around "standalone" installations will follow in the...

@rafaelgaspar see: - https://github.com/fluxcd/helm-operator/pull/514#issuecomment-688166731 - https://github.com/fluxcd/helm-operator/pull/514#issuecomment-743122502

The issue description is no longer accurate for the current behaviour of the Git synchronization and the release process. The files check still needs to be in place as otherwise...

Cluster-state mutations are out-of-scope for the Helm Operator at the moment. As described in the feature list: > Detection and recovery from **Helm storage mutations** (e.g. a manual Helm release...

I would expect the 4 steps you have documented to work as long as the converted releases are written to the `secret` storage. We actually want to make it possible...

@derrickburns will keep that in mind while utilizing it, thanks. --- @stefanprodan any ideas on what the most straight forward approach would be for users to tell the operator that...

Can you try running the Helm Operator with the following environmental flag enabled: `GODEBUG=madvdontneed=1`? I am wondering if we are bitten by the new GC behaviour of Golang since >=1.12.

@geNAZt are you by any chance active on either the CNCF or Weaveworks Slack community? Would like to provide some insights (and have a chat about it). I am `@hidde`...

https://slack.cncf.io for an invite, you can find me in `#flux` (and `#flux-dev`).