James Mills

I see

If I update my workflow to have `charts_dir: .` I get the following behaviour: ``` Run helm/[email protected] with: charts_dir: . env: CR_TOKEN: *** netdata-helmchart Looking up latest tag... Discovering changed...

I _think_ the problem is with this action's workflow `cr.sh` script itself: https://github.com/helm/chart-releaser-action/blob/97237943efb7a48269d47a642ec5fdff675aa55f/cr.sh#L186-L188 I can _probably_ fix this if you would accept a PR to be a bit more flexible...

I made some modifications in [this fork](https://github.com/prologic/chart-releaser-action) and now things are getting even weirder: ``` Discovering changed charts since '1fe4c3b8e1f1385caf11c17e422c832c711078d3'... WARNING: .github/Chart.yaml is missing, assuming that '.github' is not a...

> I can make PR for this, but since it is directly specified in the helm docs that the charts structure must be charts//Chart.yaml, I was wondering if we can...

Since #1030 will soon be available does it make sense to tackle this next? Having services that may need special access to devices makes scheduling a lot easier

I ran into an issue similar to the one described in this issue; but with a different root cause and solution. ## Symptoms I saw a service deployed with `docker...

> How we use it to exploit Did you even read the [README](/README.md) ?! 😂

I _may_ be barking up the wrong tree here, but I'm struggling myself to get Cloudinit to operate correctly on an Ubuntu 20.04 Guest in VCD. I also set guest...

Thanks! I'll have a look in the morning 👌