Custom script as a deployer

[ojhughes]

Expected behavior

Ability to provide a custom script as a deployer, using the same pattern that allows a custom build script to be used as a builder. This will enable other Kubernetes deployment tools to be leveraged within a Skaffold workflow, such as Kapp or Spinnaker pipeline triggers

Actual behavior

Currently, it is only possible to use kubectl, helm or kustomize as a deployer implementation

[NAlexPear]

This is important for us as well, since we're using sops for secret decryption across environments. So even though we're happy using kubectl to apply changes to our clusters, the inability to hook into that deploy pipeline means that we can't currently use skaffold

[erandagan]

More use cases:

• Using other configuration & templating solutions like kapitan or plain Jinja2.
• Mixing helm and kustomize in all sorts of ways
• As @NAlexPear mentioned, handling secrets using a variety of mechanisms. This is a real pain point that makes it difficult to integrate Skaffold into most of our projects even if we're already using one of the supported deployers. We're currently using the great sealed-secrets as a workaround, but would much rather use our standard KMS solution instead.
• Support client-side helm templates #1514

[tbarrella]

It seems like this could also reduce the need for #1441

[ojhughes]

This is my current workflow
skaffold render | kapp deploy -a $(yq r skaffold.yaml metadata.name) -y -f -

In my case I also let kapp take care of deletion of the deployment so would also be nice to provide an override for skaffold delete

[tstromberg]

Adding discuss label to see if this is actually feasible or not, given Skaffolds current architecture.