Limit the number of names per image reported in the node status#32914
Conversation
|
/cc @dchen1107 |
|
LGTM |
| } | ||
|
|
||
| for _, image := range containerImages { | ||
| names := append(image.RepoDigests, image.RepoTags...) |
There was a problem hiding this comment.
Why Digests and Tags? Are they both really legit names?
There was a problem hiding this comment.
There is no actual "name" defined in docker images.. Digest is a content-addressable identifier which users can use to pull an image (which we also support in k8s), so it should be a legit "name" in our definition. I don't think there should be multiple digests per image (since it's sha256 hash based on the content), so I changed the order of the digests and tags to ensure that we always include the digest.
|
thanks for the quick fix! |
|
@k8s-bot test this issue: #IGNORE |
1 similar comment
|
GCE e2e build/test passed for commit 7ada991. |
|
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
|
GCE e2e build/test passed for commit 7ada991. |
|
Automatic merge from submit-queue |
|
@pwittrock this doesn't need to go into 1.4.0 but it would be good for it to end up in a 1.4.x. |
|
thx |
|
@yujuhong can you open the pull request to cherry-pick this into release-1.4, thanks! |
#33163-#33227-#33359-#33605-#33967-#33977-#34158-origin-release-1.4 Automatic merge from submit-queue Automated cherry pick of #32914 #33163 #33227 #33359 #33605 #33967 #33977 #34158 origin release 1.4 Cherry pick of #32914 #33163 #33227 #33359 #33605 #33967 #33977 #34158 on release-1.4. #32914: Limit the number of names per image reported in the node #33163: fix the appending bug #33227: remove cpu limits for dns pod. The current limits are not #33359: Fix goroutine leak in federation service controller #33605: Add periodic ingress reconciliations. #33967: scheduler: cache.delete deletes the pod from node specified #33977: Heal the namespaceless ingresses in federation e2e. #34158: Add missing argument to log message in federated ingress
|
Commit found in the "release-1.4" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
…ck-of-#32914-kubernetes#33163-kubernetes#33227-kubernetes#33359-kubernetes#33605-kubernetes#33967-kubernetes#33977-kubernetes#34158-origin-release-1.4 Automatic merge from submit-queue Automated cherry pick of kubernetes#32914 kubernetes#33163 kubernetes#33227 kubernetes#33359 kubernetes#33605 kubernetes#33967 kubernetes#33977 kubernetes#34158 origin release 1.4 Cherry pick of kubernetes#32914 kubernetes#33163 kubernetes#33227 kubernetes#33359 kubernetes#33605 kubernetes#33967 kubernetes#33977 kubernetes#34158 on release-1.4. kubernetes#32914: Limit the number of names per image reported in the node kubernetes#33163: fix the appending bug kubernetes#33227: remove cpu limits for dns pod. The current limits are not kubernetes#33359: Fix goroutine leak in federation service controller kubernetes#33605: Add periodic ingress reconciliations. kubernetes#33967: scheduler: cache.delete deletes the pod from node specified kubernetes#33977: Heal the namespaceless ingresses in federation e2e. kubernetes#34158: Add missing argument to log message in federated ingress
…ck-of-#32914-upstream-release-1.4 Automatic merge from submit-queue Automated cherry pick of kubernetes#32914 Cherry pick of kubernetes#32914 on release-1.4. kubernetes#32914: Limit the number of names per image reported in the node
Limit the number of names per image reported in the node status.
This fixes #32908
This change is