Skip to content
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

update kubernetes dependency to 1.30 #4569

Closed
3 of 5 tasks
Madhu-1 opened this issue Apr 19, 2024 · 5 comments
Closed
3 of 5 tasks

update kubernetes dependency to 1.30 #4569

Madhu-1 opened this issue Apr 19, 2024 · 5 comments
Labels
wontfix This will not be worked on

Comments

@Madhu-1
Copy link
Collaborator

Madhu-1 commented Apr 19, 2024

Kubernetes 1.30 is released https://kubernetes.io/blog/2024/04/17/kubernetes-v1-30-release/ let's make use of it in cephcsi

Copy link

github-actions bot commented Jun 1, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the wontfix This will not be worked on label Jun 1, 2024
@Madhu-1
Copy link
Collaborator Author

Madhu-1 commented Jun 3, 2024

@iPraveenParihar anything pending on this one?

@iPraveenParihar
Copy link
Contributor

@iPraveenParihar anything pending on this one?

@Madhu-1, I have updated tasks as completed with PRs linked in the Issue description.

  • For k8s E2E tests mandatory in CI run, we do have conditions in mergify right?

    ceph-csi/.mergify.yml

    Lines 75 to 78 in aa2cc67

    - "status-success=ci/centos/k8s-e2e-external-storage/1.27"
    - "status-success=ci/centos/k8s-e2e-external-storage/1.28"
    - "status-success=ci/centos/k8s-e2e-external-storage/1.29"
    - "status-success=ci/centos/k8s-e2e-external-storage/1.30"

    did you mean anything else?

  • For Readme update, I don't see anything to be done.
    As we only updated k8s 1.30 in devel, not in release v3.11. Or did I miss anything? 🤔

@Madhu-1
Copy link
Collaborator Author

Madhu-1 commented Jun 3, 2024

Yes i meant the same, in that case can we close it if all the required works are completed?

@iPraveenParihar
Copy link
Contributor

Yes, good to close.

@Madhu-1 Madhu-1 closed this as completed Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants