ingress2gateway icon indicating copy to clipboard operation
ingress2gateway copied to clipboard

Added IngressClass objects support #117

Open Varun1300211 opened this issue 1 year ago • 12 comments

What type of PR is this? This pull request implements IngressClass support.

Add one of the following kinds: /kind feature

What this PR does / why we need it: It retrieves the default IngressClass based on its API group (networking.k8s.io) and a dedicated annotation (ingressclass.kubernetes.io/is-default-class). If no explicit IngressClass is specified in the Ingress object or via annotation, the default class is used for resource processing.

Which issue(s) this PR fixes:

Fixes #117

Does this PR introduce a user-facing change?:


Please do let me know if it was done in the correct way.

Varun1300211 avatar Feb 13 '24 18:02 Varun1300211

CLA Signed

The committers listed above are authorized under a signed CLA.

  • :white_check_mark: login: Varun1300211 / name: Varun Kumar Gupta (6293f14b68407e2e93a233e1f744a19d30b4dde2, 5b80862d241e80ed5d86ca762c9de195aaff27a1)

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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 avatar Feb 13 '24 18:02 k8s-ci-robot

Welcome @Varun1300211!

It looks like this is your first PR to kubernetes-sigs/ingress2gateway 🎉. 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-sigs/ingress2gateway 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. :smiley:

k8s-ci-robot avatar Feb 13 '24 18:02 k8s-ci-robot

Hi @Varun1300211. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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 avatar Feb 13 '24 18:02 k8s-ci-robot

/easycla

Varun1300211 avatar Feb 13 '24 18:02 Varun1300211

/ok-to-test

LiorLieberman avatar Feb 13 '24 18:02 LiorLieberman

Thanks @Varun1300211 !

I will probably look at it tomorrow. In the meantime, can you:

  1. add a release_note block in the PR description (it should be added by default every PR but looks like you deleted it)
  2. Retitle the PR to reflect exactly the change your are adding
  3. Why did you update go mod (probably you run go mod tidy)? I dont think thats needed so if you can revert it it will be awesome.

Thanks! /hold

LiorLieberman avatar Feb 13 '24 18:02 LiorLieberman

Done all the changes requested by you @LiorLieberman, please let me know if anything else is required.

Varun1300211 avatar Feb 13 '24 20:02 Varun1300211

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

Test name Commit Details Required Rerun command
pull-ingress2gateway-verify 5b80862d241e80ed5d86ca762c9de195aaff27a1 link true /test pull-ingress2gateway-verify
pull-ingress2gateway-test 5b80862d241e80ed5d86ca762c9de195aaff27a1 link true /test pull-ingress2gateway-test

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.

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.

k8s-ci-robot avatar Feb 14 '24 21:02 k8s-ci-robot

Hi @levikobi, I made the changes suggested by you. Please take a look.

Varun1300211 avatar Feb 14 '24 21:02 Varun1300211

@Varun1300211 Just checking in, please let us know if you need any help with moving this forward

LiorLieberman avatar Mar 02 '24 16:03 LiorLieberman

@Varun1300211 a friendly ping, are you still planning to work on this?

LiorLieberman avatar Apr 03 '24 09:04 LiorLieberman