Basic support for using kubectl and helm together

[ajbouh]

This is the minimal change needed to do deploys with both kubectl and helm.

If only one configuration is present, it falls back to existing logic. If both configurations are present, a new deployer is returned that runs both helm and kubectl in sequence.

It is naive in a number of ways:

• It does not determine which artifacts are used by which deployer, so a change in any artifact redeploys both kubectl and helm
• A failure in one deployer means it does not attempt to deploy the other
• No test coverage

Addresses #528

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[dlorenc]

@ajbouh Would you be able to sign the CLA?

[ajbouh]

Done

[dgageot]

@ajbouh Can you please rebase your code? Thanks a lot!

[dlorenc]

@ajbouh can you check that you signed the CLA with the right email address? The bot is still saying it's not signed.

[ajbouh]

Hmm, I have multiple email addresses in GitHub, but only signed with the address that's referenced by the commit. Do you think that could be the issue?

…

On Tue, Jun 19, 2018, 09:27 dlorenc ***@***.***> wrote: @ajbouh <https://github.com/ajbouh> can you check that you signed the CLA with the right email address? The bot is still saying it's not signed. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#586 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAcnRC79Y1mbn90pqrK4pHiPddhlwt-ks5t-SaKgaJpZM4ULL13> .

[dgageot]

@ajbouh yes, that can be the issue. Can you also rebase your code, please? Thanks!

[balopat]

@ajbouh ping, do you still have issues with the CLA/rebasing?

[googlebot]

CLAs look good, thanks!

[ajbouh]

@balopat rebased. Also, looks like the cla bot doesn't recheck until you repush

[codecov-io]

Codecov Report

Merging #586 into master will decrease coverage by 0.42%.
The diff coverage is 13.63%.

@@            Coverage Diff             @@
##           master     #586      +/-   ##
==========================================
- Coverage   40.61%   40.19%   -0.43%     
==========================================
  Files          68       68              
  Lines        2969     3005      +36     
==========================================
+ Hits         1206     1208       +2     
- Misses       1639     1671      +32     
- Partials      124      126       +2

Impacted Files	Coverage Δ
pkg/skaffold/deploy/deploy.go	25% <0%> (-75%)	⬇️
pkg/skaffold/runner/runner.go	54.63% <54.54%> (+0.18%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f728fd9...2182fc0. Read the comment docs.