Azure / karpenter-provider-azure / 15646568960

94%

Build Type

push

github

Committed by web-flow

Commit Message

fix: issue where container can come up but be unable to access token (#970)

When the process launches, if it doesn't check that it can retrieve a
token, then if it's unable to retrieve a token later it will continue to
retry getting a token, but won't ever exit the process.

This is a problem especially in the managed NAP case, because there's an
IMDS proxy that needs to be set up before the NAP pod can get a token,
but if the Karpenter pod starts too quickly it will open a connection in
the transport connection pool to the wrong address (not the proxy),
which will never serve it the correct token. This will mostly
self-recover if request load is low, because the transport idle timeout
will be hit and a new connection will go to the proxy, but if request
load is high enough it can keep the connection open forever.

Better to lose the race gracefully and just exit the pod if we can't get
a token.

Run Details

0 of 3 new or added lines in 1 file covered. (0.0%)

29 existing lines in 3 files now uncovered.

53983 of 56559 relevant lines covered (95.45%)

0.96 hits per line