Aaron Prindle

Thanks for the submission @filipenf! Currently you have updated: `docs/content/en/docs/pipeline-stages/deployers/helm.md` We have recently forked our docs into a `docs` and a `docs-v2` folder. Can you also update the docs-v2/content/en/docs/pipeline-stages/deployers/helm.md file...

@filipenf just the new bits thanks! I believe the other differences are inherent to Skaffold v1 vs v2 (so they should be different)

@filipenf ah, I see now. Yes, if you wouldn't mind adding that section as well here that would be great. Thanks for the extra analysis here!

@gsquared94 can you add any information here regarding if this is intended behaviour from https://github.com/GoogleContainerTools/skaffold/pull/6828 and what possible short-term/long-term fixes there might for this issue?

Hi @SakoMe, sorry for the delay here. In attempting to repro this, I am not having the same issue you mentioned above. It seems that what is happening is that...

What version of the kvm driver are you using?

Closing, fixed now with the doc @ericzzzzzzz created

@ericzzzzzzz this is related to the Cloud Code v1 -> v2 migration effort. Assigning you for now as it is related to your prior investigation

Closing, the flag pattern used is common across many k8s/yaml specs. Re-open if perhaps this warrants more inspection

Just validated that this functionality indeed works @ HEAD using the repro above: Repro Dockerfile + file tree: ``` aprindle@aprindle-ssd ~/kaniko-ctx-dir tree . ├── Dockerfile └── files └── include_me 2...