Update kubernetes test version to 1.31.4

[martinhny]

Summary by CodeRabbit

• Chores
  • Updated Kubernetes version from 1.30.0 to 1.31.4 in project configuration

[coderabbitai]

Warning

Rate limit exceeded

@martinhny has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 14 minutes and 10 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between df65187 and a01bcd5.

📒 Files selected for processing (1)

• Makefile (2 hunks)

Walkthrough

The pull request involves updating the Kubernetes version in the Makefile from version 1.30.0 to 1.31.4. This change specifically modifies the KUBERNETES_VERSION variable, which consequently impacts the KIND_IMAGE variable that depends on the Kubernetes version. The modification is straightforward and does not introduce any structural changes to the Makefile's existing targets or functionality.

Changes

File	Change Summary
Makefile	Updated KUBERNETES_VERSION from 1.30.0 to 1.31.4

Poem

🐰 A Kubernetes hop, version's new leap,
From 1.30 to 1.31, a version so sweet!
In Makefile's garden, numbers dance light,
Updating clusters with technological might.
Rabbit's version bump, smooth and clean! 🚀

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Files

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f5ea3db and 33e0e1b.

📒 Files selected for processing (1)

• Makefile (1 hunks)

🧰 Additional context used

🪛 GitHub Actions: Test

Makefile

[error] 63-63: Failed to create cluster due to invalid Docker image 'kindest/node:v1.31.3'. The specified image version does not exist in the registry.

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Build container image
• GitHub Check: Analyze (go)

🔇 Additional comments (1)

Makefile (1)

27-27: Verify impact on dependent targets.

The invalid KIND_IMAGE will break several dependent targets including:

• kind-cluster
• setup-local
• test
• run-test

This affects both local development and CI/CD pipelines.

Let's analyze the dependency chain: