-
Notifications
You must be signed in to change notification settings - Fork 255
Description
Expected behavior
Container images are successfully built and builds succeed.
Actual behavior
Builds are failing: https://github.com/kptdev/kpt/actions/runs/22597384156/job/65525954615#step:5:645 due to bad SSL certificate on https://kubernetesjsonschema.dev/
--- FAIL: TestFnEval (4.35s)
--- FAIL: TestFnEval/testdata/fn-eval/privilege-options/mount (0.21s)
runner.go:82: Using kpt binary: /home/runner/work/kpt/kpt/go/bin/kpt
runner.go:293: Running test against package mount
runner.go:383: running command: KRM_FN_RUNTIME=docker /usr/bin/bash /home/runner/work/kpt/kpt/go/src/github.com/kptdev/kpt/e2e/testdata/fn-eval/privilege-options/mount/.expected/exec.sh
runner.go:391: kpt error, stdout: ; stderr: curl: (60) SSL: no alternative certificate subject name matches target host name 'kubernetesjsonschema.dev'
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
fn_test.go:89: failed when running test: actual exit code 60 doesn't match expected 0
Information
Proposal is to update to this:
curl -sSL 'https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/master-standalone/configmap-v1.json' -o $SCHEMA_DIR/configmap-v1.json
Steps to reproduce the behavior
Run the command
$ curl -sSL 'https://kubernetesjsonschema.dev/master-standalone/configmap-v1.json'