The committers listed above are authorized under a signed CLA.

• ✅ login: Kesavaraja67 / name: Kesavaraja M (2b57ebf)

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Welcome @Kesavaraja67!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

Hi @Kesavaraja67. Thanks for your PR.

I'm waiting for a github.com 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.

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Kesavaraja67
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Hi @thockin @derekwaynecarr, I have fixed the CLA and release-note formatting issues. This PR is now ready for review and testing. Could you please take a look and /ok-to-test if this is ready for the CI suite? Thank you!

/sig api-machinery
/sig apps

/sig api-machinery

is this theoretical or a real world scenario?

Hi @dims! To be honest, I found this through code analysis and testing while looking at the parser, so it's 'theoretical' in the sense that I haven't seen a specific bug report for it yet.

However, I realized that while math.MaxInt64 is a perfectly valid int64 value, the parser's 18-digit fast-path check effectively blocks it. Since Kubernetes is increasingly used for massive resource quantities (like bytes for very large storage), I figured it was better to fix this logic gap now before it becomes a real-world production issue for someone.

/ok-to-test

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

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.