clean up, use attempt from container runtime service as restart count

[chengjoey]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

use attempt from container runtime service as restart count
don't need to parse the restartCount from the container's annotation, but directly obtain it from the status returned by the cri

kubernetes/pkg/kubelet/kuberuntime/kuberuntime_container.go

Lines 342 to 348 in 2c7bda5

	containerLogsPath := buildContainerLogsPath(container.Name, restartCount)
	restartCountUint32 := uint32(restartCount)
	config := &runtimeapi.ContainerConfig{
	Metadata: &runtimeapi.ContainerMetadata{
	Name: container.Name,
	Attempt: restartCountUint32,
	},

Special notes for your reviewer:

[k8s-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: chengjoey
Once this PR has been reviewed and has the lgtm label, please assign derekwaynecarr for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• pkg/kubelet/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @chengjoey. Thanks for your PR.

I'm waiting for a kubernetes 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.

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.

[chengjoey]

/sig kubelet

[k8s-ci-robot]

@chengjoey: The label(s) sig/kubelet cannot be applied, because the repository doesn't have them.

In response to this:

/sig kubelet

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.

[bart0sh]

/triage accepted
/priority important-longterm
/ok-to-test

[bart0sh]

/cc

[chengjoey]

Because the original toKubeContainerStatus function needs to parse annotatedInfo from status, and when status.State == runtimeapi.ContainerState_CONTAINER_EXITED, it needs to parse annotatedInfo again, so passing annotatedInfo as a pointer to toKubeContainerStatus avoids parsing annotatedInfo twice.

[chengjoey]

/test pull-kubernetes-e2e-gce