Hi @swagatbora90. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Is there a particular reason you preferred upper-case for consistency rather than lower-case?

Mostly because majority of the existing comments are using upper-case and the usage seemed similar to how we refer a proper noun.

Mostly because majority of the existing comments are using upper-case and the usage seemed similar to how we refer a proper noun.

Makes sense. My bias would be lower-case, but we don't have a style guide so this is fine too. (Since you're at Amazon: you can check around with the doc writers there but the AWS style guide generally prefers lower-case for object names.)

Your fixup commit is causing CI to fail since it does not have a proper DCO signature. Mind squashing the commits together and making sure you retain the Signed-off-by line so that the CI workflow can continue?

Makes sense. My bias would be lower-case, but we don't have a style guide so this is fine too. (Since you're at Amazon: you can check around with the doc writers there but the AWS style guide generally prefers lower-case for object names.)

Thanks for the review. I have not seen any such style guide myself, but I will look around. Perhaps it will have some good justification around the using lower case.

prefer moving to and / or sticking with the lowercase, in this case

Sure, I have changed to use lower-case, since there is a clear preference now. PTAL.