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

add requirement for apiversion of unstructured when decoding #110809

Conversation

weilaaa
Copy link
Member

@weilaaa weilaaa commented Jun 27, 2022

What type of PR is this?
/kind bug

What this PR does / why we need it:
add requirement for apiversion of unstructured when decoding

Which issue(s) this PR fixes:
#109023

/cc @apelisse @kevindelgado @liggitt
/sig api-machinery

@k8s-ci-robot
Copy link
Contributor

@weilaaa: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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/test-infra repository.

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jun 27, 2022
@k8s-ci-robot
Copy link
Contributor

Hi @weilaaa. Thanks for your PR.

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

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/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Jun 27, 2022
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: weilaaa
To complete the pull request process, please assign smarterclayton after the PR has been reviewed.
You can assign the PR to them by writing /assign @smarterclayton in a comment when ready.

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

Needs approval from an approver in each of these files:

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

@k8s-ci-robot k8s-ci-robot added the kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API label Jun 27, 2022
@k8s-triage-robot
Copy link

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

@liggitt
Copy link
Member

liggitt commented Jun 27, 2022

thanks for the PR... before tightening validation here, the following item from the issue needs research:

Ideally, our decoding would consistently require kind and apiVersion, but we need to understand whether there are any currently working scenarios that are omitting apiVersion from unstructured data before we do so.

@weilaaa
Copy link
Member Author

weilaaa commented Jun 28, 2022

It seems difficult to check out any currently working scenarios, shall we add warning log here to prompt users to make change?

@leilajal
Copy link
Contributor

/assign @kevindelgado
/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 30, 2022
@liggitt
Copy link
Member

liggitt commented Jul 1, 2022

It seems difficult to check out any currently working scenarios, shall we add warning log here to prompt users to make change?

Unfortunately, an error log wouldn't be visible or noticed by API-level callers

At a minimum, the categories of use we'd want to check are from the command line (e.g. kubectl), config files, and the API server decoding requests to typed and untyped APIs via all write methods (create, update, and all supported patch types). If any of those currently accept content without apiVersion and do reasonable things with it, it's going to be hard to make a case for this being a backwards-compatible change.

@weilaaa
Copy link
Member Author

weilaaa commented Jul 4, 2022

It seems difficult to check out any currently working scenarios, shall we add warning log here to prompt users to make change?

Unfortunately, an error log wouldn't be visible or noticed by API-level callers

At a minimum, the categories of use we'd want to check are from the command line (e.g. kubectl), config files, and the API server decoding requests to typed and untyped APIs via all write methods (create, update, and all supported patch types). If any of those currently accept content without apiVersion and do reasonable things with it, it's going to be hard to make a case for this being a backwards-compatible change.

Thanks for your answer. I will temporarily close this pr, wish it will be reopened in the future. I'm willing to be assigned if needed anyway.

@weilaaa weilaaa closed this Jul 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/bug Categorizes issue or PR as related to a bug. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants