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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support k8s 1.30 on release #2914

Closed
rquitales opened this issue Mar 27, 2024 · 0 comments 路 Fixed by #2932
Closed

Support k8s 1.30 on release #2914

rquitales opened this issue Mar 27, 2024 · 0 comments 路 Fixed by #2932
Assignees
Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed

Comments

@rquitales
Copy link
Contributor

Hello!

  • Vote on this issue by adding a 馃憤 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Kubernetes v1.30 release is in progress. The provider should support v1.30 as soon as its available.

Current tag is rc.0: https://github.com/kubernetes/kubernetes/releases/tag/v1.30.0-rc.0

The final release is scheduled for 17 April 2024 (ref: https://github.com/kubernetes/sig-release/tree/master/releases/release-1.30)

@rquitales rquitales added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Mar 27, 2024
@mjeffryes mjeffryes removed the needs-triage Needs attention from the triage team label Mar 28, 2024
rquitales added a commit that referenced this issue Apr 18, 2024
### Proposed changes

Update Kubernetes schema and client libraries to v1.30. Go is also
updated to v1.22 as an upstream library requires this.

### Related issues (optional)

Closes: #2914
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants