[chart] Update kubernetes-csi/livenessprobe

[ialidzhikov]

/kind feature

Fixes #1044

[k8s-ci-robot]

@ialidzhikov: The label(s) kind/enhacement cannot be applied, because the repository doesn't have them.

In response to this:

/kind enhacement

Fixes #1044

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/test-infra repository.

[k8s-ci-robot]

Hi @ialidzhikov. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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/test-infra repository.

[ialidzhikov]

/kind feature

[ialidzhikov]

/cc @wongma7

[vdhanan]

/ok-to-test

[ialidzhikov]

/retest

[ialidzhikov]

Failures seem to be related to

/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/hack/e2e/csi-test-artifacts/bin/kops: line 1: `<?xml version="1.0" encoding="utf-8"?><Error><Code>ServerBusy</Code><Message>Egress is over the account limit.'
###
## Creating cluster test-cluster-23625.k8s.local with /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-23625.k8s.local.kops.yaml (dry run)
#
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/hack/e2e/csi-test-artifacts/bin/kops: line 1: syntax error near unexpected token `<'
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/hack/e2e/csi-test-artifacts/bin/kops: line 1: `<?xml version="1.0" encoding="utf-8"?><Error><Code>ServerBusy</Code><Message>Egress is over the account limit.'
make: *** [Makefile:168: test-e2e-multi-az] Error 2
+ EXIT_VALUE=2
+ set +o xtrace

cc @wongma7

[ialidzhikov]

/assign @wongma7

[ialidzhikov]

ping @wongma7
for review/approval

[ialidzhikov]

ping @wongma7
for review/approval

[ialidzhikov]

/assign @nckturner

[ialidzhikov]

ping @wongma7 @nckturner

[wongma7]

/lgtm
/approve

sorry for delay, I wanted to get v2.4.0 pushed to private ECR as well to keep the GCR and ECR kustomize in sync. Now the ECR public kustomize will drift out of sync anyway so ultimately I don't think it matters much if the templates go out of sync...as long as they are the same major version

~ $ aws ecr get-login-password | docker login --username AWS --password-stdin 602401143452.dkr.ecr.us-west-2.amazonaws.com
    docker pull 602401143452.dkr.ecr.us-west-2.amazonaws.com/eks/livenessprobe:v2.4.0

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ialidzhikov, wongma7

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:

• OWNERS [wongma7]

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

[wongma7]

ref, table of sidecar image availability for ecr/ecr public: #1136 (comment)