Skip to content

Adding IngressClass to networking/v1beta1#88509

Merged
k8s-ci-robot merged 1 commit intokubernetes:masterfrom
robscott:ingress-v1beta1-class
Mar 2, 2020
Merged

Adding IngressClass to networking/v1beta1#88509
k8s-ci-robot merged 1 commit intokubernetes:masterfrom
robscott:ingress-v1beta1-class

Conversation

@robscott
Copy link
Copy Markdown
Member

What type of PR is this?
/kind api-change

What this PR does / why we need it:
This builds on the initial PR filed to graduate Ingress to v1. It has become clear that the scope of changes was too large to fit into a graduation to v1. This PR takes the IngressClass portion of that PR and adds it to v1beta1 in preparation for graduation to v1 in 1.19.

Does this PR introduce a user-facing change?:

A new IngressClass resource has been added to enable better Ingress configuration.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/cc @cmluciano
/sig network
/priority important-soon

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. sig/network Categorizes an issue or PR as relevant to SIG Network. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. area/apiserver area/kubectl area/test sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels Feb 25, 2020
@robscott robscott force-pushed the ingress-v1beta1-class branch from f9269a9 to 7e229f4 Compare February 25, 2020 05:53
@fejta-bot
Copy link
Copy Markdown

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.

Copy link
Copy Markdown
Contributor

@sftim sftim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor things!

Comment thread pkg/registry/networking/ingressclass/strategy.go Outdated
Comment thread plugin/pkg/admission/ingressclass/admission.go Outdated
@fedebongio
Copy link
Copy Markdown
Contributor

/cc @liggitt
(just in case)

@k8s-ci-robot k8s-ci-robot requested a review from liggitt February 25, 2020 21:12
@robscott robscott force-pushed the ingress-v1beta1-class branch 2 times, most recently from 64e30f6 to c50d833 Compare February 25, 2020 21:21
@k8s-ci-robot k8s-ci-robot added area/kubelet sig/node Categorizes an issue or PR as relevant to SIG Node. labels Feb 25, 2020
@robscott robscott force-pushed the ingress-v1beta1-class branch from c50d833 to a1185b8 Compare February 25, 2020 21:26
@robscott
Copy link
Copy Markdown
Member Author

All the related feedback from the initial PR should now be resolved. Please take another look whenever you have time.

/assign @thockin @liggitt

@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 1, 2020
@robscott robscott force-pushed the ingress-v1beta1-class branch from 00a8d58 to 9eb8c3f Compare March 1, 2020 23:37
@robscott
Copy link
Copy Markdown
Member Author

robscott commented Mar 2, 2020

/retest

Comment thread plugin/BUILD Outdated
Co-authored-by: Christopher M. Luciano <cmluciano@us.ibm.com>
@robscott robscott force-pushed the ingress-v1beta1-class branch from 9eb8c3f to 132d2af Compare March 2, 2020 02:17
@liggitt
Copy link
Copy Markdown
Member

liggitt commented Mar 2, 2020

/test pull-kubernetes-conformance-kind-ga-only

@liggitt
Copy link
Copy Markdown
Member

liggitt commented Mar 2, 2020

/retest

@liggitt
Copy link
Copy Markdown
Member

liggitt commented Mar 2, 2020

/lgtm
/approve
/hold for clean ga-only test run

@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm "Looks good to me", indicates that a PR is ready to be merged. labels Mar 2, 2020
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liggitt, robscott

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

The pull request process is described here

Details 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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 2, 2020
@robscott
Copy link
Copy Markdown
Member Author

robscott commented Mar 2, 2020

/retest

@liggitt
Copy link
Copy Markdown
Member

liggitt commented Mar 2, 2020

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 2, 2020
@k8s-ci-robot k8s-ci-robot merged commit fdb2cb4 into kubernetes:master Mar 2, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Mar 2, 2020
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

@robscott: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
pull-kubernetes-e2e-gce-alpha-features 132d2af link /test pull-kubernetes-e2e-gce-alpha-features

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.

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/test-infra repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/apiserver area/kubectl area/kubelet area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

Status: API review completed, 1.18

Development

Successfully merging this pull request may close these issues.

7 participants