GoogleContainerTools/skaffold

[Test Failure] TestBuildKanikoInsecureRegistry is timing our consistently

Open

#7,121 opened on Feb 16, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (12,822 stars) (1,416 forks)batch import
bugbash/q4-2022build/kanikohelp wantedkind/todopriority/p2

Description

The latest version of kaniko is broken due to auth issues.

  1. Pinning our test to older version to see if it fixes the Test.
    • It did not fix the test.

TestBuildKanikoInsecureRegistry needs more investigation. Skipping it for now.

Contributor guide

Tech stack
go
Domain
testingdevops
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
GotestingkanikoDocker
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the TestBuildKanikoInsecureRegistry test in the skaffold repository. Check the test file for the insecure registries setup and the kaniko builder configuration. Look at the kaniko version being used and any recent changes to auth handling. The issue notes that pinning the test to an older version did not fix, so the root cause may be elsewhere.