Allow for remote kustomize bases#2269
Conversation
|
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. What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
|
I've signed the CLA. |
|
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
balopat
left a comment
There was a problem hiding this comment.
This looks great, thank you!
Can you add one more testcase for the existing base case?
Codecov Report
|
Kustomize will error if it can't find a base dependency, so it's safe for Skaffold to assume that any base file that does not exist locally is intended to be a remote path that can be ignored since Skaffold can't monitor remote paths for changes.
|
Added additional requested test case. |
|
but weren't bases just removed from kustomize? |
|
like they are replaced with ordered resources |
|
@matti is apparently correct! I am not sure if remote resources are still supported, but this code will need to be modified to support the new version's implementation. Another issue can be opened for that, but here's the relevant documentation for the change for everyone's edification: https://github.com/kubernetes-sigs/kustomize/blob/dc433e12fb7063c57fec74e3ee0a24587c8ca84b/docs/v2.1.0.md#field-changes--deprecations |
|
Could you open another issue. That would be awesome! |
Fixes #2082
Kustomize will error if it can't find a base dependency, so it's safe for
Skaffold to assume that any base file that does not exist locally is intended
to be a remote path that can be ignored since Skaffold can't monitor remote
paths for changes.