-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validate sandbox and container metadata #1274
Validate sandbox and container metadata #1274
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold Refers to a previous discussion in cri-o/cri-o#3774, cri-o/cri-o#3618 |
/unhold |
We pre-validate the container metadata before creation the sandbox/container. Fixes kubernetes-sigs#1273 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
d96416a
to
75c136c
Compare
/lgtm |
Cri-tools 1.29[0] now pre-validates container metadata before running with crictl[1]. The required uid field was missing in our test causing the following failure. ``` load podSandboxConfig: name, namespace or uid is not in metadata \"&PodSandboxMetadata{Name:rhcos-crio-pod-restart-test,Uid:,Namespace:redhat.test.crio,Attempt:0,}\ ``` [0] https://github.com/kubernetes-sigs/cri-tools/releases/tag/v1.29.0 [1] kubernetes-sigs/cri-tools#1274
Cri-tools 1.29[0] now pre-validates container metadata before running with crictl[1]. The required uid field was missing in our test causing the following failure. ``` load podSandboxConfig: name, namespace or uid is not in metadata \"&PodSandboxMetadata{Name:rhcos-crio-pod-restart-test,Uid:,Namespace:redhat.test.crio,Attempt:0,}\ ``` [0] https://github.com/kubernetes-sigs/cri-tools/releases/tag/v1.29.0 [1] kubernetes-sigs/cri-tools#1274
Cri-tools 1.29[0] now pre-validates container metadata before running with crictl[1]. The required uid field was missing in our test causing the following failure. ``` load podSandboxConfig: name, namespace or uid is not in metadata \"&PodSandboxMetadata{Name:rhcos-crio-pod-restart-test,Uid:,Namespace:redhat.test.crio,Attempt:0,}\ ``` [0] https://github.com/kubernetes-sigs/cri-tools/releases/tag/v1.29.0 [1] kubernetes-sigs/cri-tools#1274
Cri-tools 1.29[0] now pre-validates container metadata before running with crictl[1]. The required uid field was missing in our test causing the following failure. ``` load podSandboxConfig: name, namespace or uid is not in metadata \"&PodSandboxMetadata{Name:rhcos-crio-pod-restart-test,Uid:,Namespace:redhat.test.crio,Attempt:0,}\ ``` [0] https://github.com/kubernetes-sigs/cri-tools/releases/tag/v1.29.0 [1] kubernetes-sigs/cri-tools#1274
What type of PR is this?
/kind bug
What this PR does / why we need it:
We pre-validate the container metadata before creation the sandbox/container.
Which issue(s) this PR fixes:
Fixes #1273
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?