Fix busybox path in plugin job with switch to x86_64_sysroot
skaffold profile
#1943
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary: Fix busybox path in plugin job with switch to
x86_64_sysroot
skaffold profile#1941 switched the cloud skaffold build to use the x86_64_sysroot profile. After that was introduced, the plugin load job no longer runs due to a missing
/busybox
path. This change updates the kubernetes manifests to work with the correct path.Relevant Issues: N/A
Type of change: /kind cleanup
Test Plan: Verified the following:
/busybox
in other k8s manifestssrc/cloud/plugin/load_db:plugin_db_updater_image
doesn't contain/busybox
when sysroot config is used (current skaffold behavior)src/cloud/plugin/load_db:plugin_db_updater_image
does contain/busybox
without sysroot config (previous behavior in skaffold)