fix: Kaniko skip-push-permission-check (#193) #8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "193-kaniko-skip-push-check"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Adds
--skip-push-permission-checkto the Kaniko build step. Theinsecure-registrysetting does not apply to Kaniko's push permission check, which uses a separate HTTPS transport that probes port 443 and times out against the in-cluster Harbor endpoint. This flag bypasses that check entirely.Changes
.woodpecker.yaml: Addedextra_opts: "--skip-push-permission-check"to thebuild-and-pushstep settings, after the existinginsecure-registryline.Test Plan
harbor.harbor.svc.cluster.local/pal-e-mail/apiReview Checklist
Related Notes
pal-e-platform-- the platform project this fix relates toQA Review
Diff: 1 file changed, 1 line added, 0 deleted.
Findings
extra_optsis a valid parameter forwoodpeckerci/plugin-kaniko:2.3.0-- passes raw flags to the Kaniko executor--skip-push-permission-checkis a valid Kaniko flag that bypasses the pre-push auth probeinsecure-registrycontrols pull/push transport but not the permission check probe, which uses a separate HTTPS connection that times out on port 443insecure-registry, withinsettingsblock)VERDICT: APPROVED