release: update manifest and helm charts for v1.4.5

[aramase]

• update manifest and helm charts for v1.4.5

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aramase

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 [aramase]

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

[aramase]

/hold

for #1609 to be merged and tagged.

[k8s-ci-robot]

@aramase: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-secrets-store-csi-driver-e2e-aws	093828b	link	false	/test pull-secrets-store-csi-driver-e2e-aws
release-secrets-store-csi-driver-e2e-aws	093828b	link	false	/test release-secrets-store-csi-driver-e2e-aws

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[aramase]

*-secrets-store-csi-driver-e2e-aws are failing because of quota issues. Pinged @simonmarty on slack to assist with this. Other release jobs are passing, so not going to block release on this.

2024-08-20 18:45:33 [✖]  AWS::EC2::InternetGateway/InternetGateway: CREATE_FAILED – "Resource creation cancelled"
2024-08-20 18:45:33 [✖]  AWS::EC2::EIP/NATIP: CREATE_FAILED – "Resource handler returned message: \"The maximum number of addresses has been reached. (Service: Ec2, Status Code: 400, Request ID: 2d075628-6128-4c6d-98bb-93621d526d2e)\" (RequestToken: 3b087f02-6bdd-228c-78d6-a76571be498c, HandlerErrorCode: GeneralServiceException)"
2024-08-20 18:45:33 [!]  1 error(s) occurred and cluster hasn't been created properly, you may wish to check CloudFormation console
2024-08-20 18:45:33 [ℹ]  to cleanup resources, run 'eksctl delete cluster --region=us-west-2 --name=integ-cluster-2024-08-20-18-42-49'
2024-08-20 18:45:33 [✖]  ResourceNotReady: failed waiting for successful resource state
Error: failed to create cluster "integ-cluster-2024-08-20-18-42-49"
An error occurred (ResourceNotFoundException) when calling the DescribeCluster operation: No cluster found for name: integ-cluster-2024-08-20-18-42-49.
Flag --name has been deprecated, use --cluster
Error: unable to describe cluster control plane: operation error EKS: DescribeCluster, https response error StatusCode: 404, RequestID: 2bc00446-8e74-427d-9929-8a9c6830da5f, ResourceNotFoundException: No cluster found for name: integ-cluster-2024-08-20-18-42-49.
Error: unable to describe cluster control plane: operation error EKS: DescribeCluster, https response error StatusCode: 404, RequestID: ac5e54e1-3535-4cec-b11b-0a2467b67a46, ResourceNotFoundException: No cluster found for name: integ-cluster-2024-08-20-18-42-49.

[nilekhc]

/lgtm

[aramase]

/hold cancel