Remove confusing warning in cri runtime config migration#10980
Remove confusing warning in cri runtime config migration#10980AkihiroSuda merged 1 commit intocontainerd:mainfrom
Conversation
|
Skipping CI for Draft Pull Request. |
|
/test all |
59dcd6b to
fae7c34
Compare
53f74e9 to
2a0bdee
Compare
2a0bdee to
3a25e7b
Compare
|
/test pull-containerd-node-e2e |
3a25e7b to
7a118cb
Compare
0dd5e24 to
7913322
Compare
7913322 to
398022a
Compare
|
Hi @AkihiroSuda when you have some time could you PTAL this PR? This removes unnecessary WARN from cri runtime config migration. It was reported in a few issues (#10959, #11221 (comment)). thank you! |
398022a to
793b773
Compare
6c092dc to
023badb
Compare
|
/test pull-containerd-k8s-e2e-ec2 |
Signed-off-by: Jin Dong <[email protected]>
023badb to
fb44e37
Compare
|
/retest-required |
|
Hi @dmcgowan @AkihiroSuda thanks for reviewing. Do we need to cherrypick this to release/2.0? |
|
/cherry-pick release/2.0 |
|
@AkihiroSuda: new pull request created: #11256 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Fix #10959
In current cri runtime config migration, it only changes
sandbox_modetosandboxerbut left fields that are already moved to cri image/grpc services in place. That causes confusingWARNfrom toml parsing for cri runtime config, because those leftover cri image/grpc config fields don't have entries inRuntimeconfig struct.This PR explicitly skips those fields that are moved to cri image/grpc during cri runtime config migration, thus avoiding the
WARNs.Test using the 1.7 default config.toml
After this PR:
On main branch: