Make the hot-reload example more exemplary

[jonaseck2]

While investigating #1668 I found myself modifying the hot-reload example to actually test how sync works in 0.22, and doesn't in 0.23/master. The example is a little too succinct to understand how hot-reload works:

First off the example syncs exactly one source file. The Dockerfile does copy a glob, but the destination isn't a folder, so adding a second source file sibling crashes the build.

Secondly I was suspecting that nested folders might be the issue, so i added a src folder, which is probably closer to a real world example anyways. It also clarifies that the pattern isn't recursive like .gitignore (unless the folder name matches, then it's actually traversed), even though the k8s path does hint at that.

Now when the Dockerfile and sync pattern no longer exactly overlap, you can easily test that only files intersected by the Dockerfile and sync pattern are synced, files included by the Dockerfile but not the sync pattern fall back to docker build, and files matched by the pattern but outside the Dockerfile are ignored.

In hindsight it feels kinda obvious, but we'll probably end up with fewer issues on hot-reload with an example that is a little more verbose.

My comment on #1668 is probably a separate issue

/jonas

Signed-off-by: Jonas Eckerström jonaseck@gmail.com

[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.

Googlers can find more info about SignCLA and this PR by following this link.

[jonaseck2]

I signed it!

[googlebot]

CLAs look good, thanks!

Googlers can find more info about SignCLA and this PR by following this link.

[dgageot]

CI is green despite the status reported on GitHub.