kpt-functions-catalog CI broken due to the Kpt/WASM dependency #3507
Labels
area/devops
area/fn-catalog
Functions Catalog
bug
Something isn't working
triaged
Issue has been triaged by adding an `area/` label
The github CI is broken due to the WASM dependency introduced from Kpt. This affects all new checkins to the catalog repo.
Error build log: https://github.com/GoogleContainerTools/kpt-functions-catalog/runs/8026401841?check_suite_focus=true
Temporary workaround: https://github.com/GoogleContainerTools/kpt-functions-catalog/pull/906/files#diff-944291df2c9c06359d37cc8833d182d705c9e8c3108e7cfe132d61a06e9133ddR101
Long term solution: Ideally, kpt should have a CI (in https://github.com/GoogleContainerTools/kpt) to run against all catalog functions to verify that any kpt change is compatible with the curated KRM functions. Besides, the catalog repo should run each e2e test against the most recently released kpt, from downloading the binary rather than building the kpt. This guarantees the catalog and Kpt can have different go modules and won't affect each other.
Short term solution: WASM requires Go 1.18 and above. To specifically fix the WASM dependencies on the catalog repo, we can upgrade the catalog functions Go to v1.18
The text was updated successfully, but these errors were encountered: