Bump the k8s group with 5 updates

[dependabot]

Bumps the k8s group with 5 updates:

Package	From	To
k8s.io/api	0.35.2	0.35.3
k8s.io/apiextensions-apiserver	0.35.2	0.35.3
k8s.io/apimachinery	0.35.2	0.35.3
k8s.io/client-go	0.35.2	0.35.3
k8s.io/kube-aggregator	0.35.2	0.35.3

Updates k8s.io/api from 0.35.2 to 0.35.3

Commits

• 3897036 Update dependencies to v0.35.3 tag
• See full diff in compare view

Updates k8s.io/apiextensions-apiserver from 0.35.2 to 0.35.3

Commits

• 073f527 Update dependencies to v0.35.3 tag
• 791831a Merge pull request #136903pohly/automated-cherry-pick-of-#136455
• 85fbdc0 Merge pull request #136387vikasbolla/automated-cherry-pick-of-#135567
• 0e52304 fake client-go: un-deprecate NewSimpleClientset
• f4ff589 Fix flaky TestApplyCRDuringCRDFinalization test
• See full diff in compare view

Updates k8s.io/apimachinery from 0.35.2 to 0.35.3

Commits

• See full diff in compare view

Updates k8s.io/client-go from 0.35.2 to 0.35.3

Commits

• 4f1f0a2 Update dependencies to v0.35.3 tag
• f80003c Merge pull request #136903pohly/automated-cherry-pick-of-#136455
• 8b41556 fake client-go: un-deprecate NewSimpleClientset
• See full diff in compare view

Updates k8s.io/kube-aggregator from 0.35.2 to 0.35.3

Commits

• a997ab6 Update dependencies to v0.35.3 tag
• 2d94f45 Merge pull request #136903pohly/automated-cherry-pick-of-#136455
• ff8205b fake client-go: un-deprecate NewSimpleClientset
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

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

Details

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-sigs/prow repository.