Add support for `IngressClass` objects

levikobi commented 9 months ago

What would you like to be added: Add support for reading and taking into account IngressClass objects.

Why this is needed: If users do not specify ingressClassName, we need to understand the default IngressClass that should be used for the conversion.

levikobi commented 9 months ago

/help

k8s-ci-robot commented 9 months ago

@levikobi: This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

Why are we solving this issue?
To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
Does this issue have zero to low barrier of entry?
How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to [this](https://github.com/kubernetes-sigs/ingress2gateway/issues/117): >/help Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

mlavacca commented 8 months ago

/good-first-issue

k8s-ci-robot commented 8 months ago

@mlavacca: This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

Why are we solving this issue?
To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
Does this issue have zero to low barrier of entry?
How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-good-first-issue command.

In response to [this](https://github.com/kubernetes-sigs/ingress2gateway/issues/117): >/good-first-issue Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

akagami-harsh commented 8 months ago

/assign

Varun1300211 commented 7 months ago

I have created a PR for the same. Kindly review it.

levikobi commented 7 months ago

I just now noticed that @akagami-harsh asked to work on this issue first. @akagami-harsh are you still interested in working on it?

akagami-harsh commented 7 months ago

@levikobi yes i am interested. i was busy with other things, but now i am free

akagami-harsh commented 7 months ago

Since there's already an open PR for this issue, should I create a new one?

LiorLieberman commented 7 months ago

Hi @akagami-harsh, no. There is already a PR @Varun1300211 opened.

Please check out other issues like https://github.com/kubernetes-sigs/ingress2gateway/issues/81 if you are still up for contributing. We would love to have you.

@Varun1300211 While we appreciate you quickly made a PR and sent for review, next time, please kindly try to confirm with the current assignee if he is working on it before proceeding with a PR

Varun1300211 commented 7 months ago

Apologies @akagami-harsh, I am still very new to the open source. Never seen you were already assigned to it before. Hope you understand.

Sure @LiorLieberman will keep it in mind from the next time onwards.

akagami-harsh commented 7 months ago

No worries at all, @Varun1300211! It happens, and I appreciate you being open to the feedback. Thanks for letting me know, @LiorLieberman . I'll take a look at issue #81.

ipsum-0320 commented 6 months ago

hi @akagami-harsh, are you still working on it, I would like to give it a try. 😊 /assign

mlavacca commented 6 months ago

@ipsum-0320, please notice @Varun1300211 is already assigned to this issue.

@Varun1300211, are you still working on it?

ipsum-0320 commented 6 months ago

@ipsum-0320, please notice @Varun1300211 is already assigned to this issue.

@Varun1300211, are you still working on it?

okok, I will wait until @Varun1300211 replies before taking the next step 😊

VasuDevrani commented 4 months ago

/assign

VasuDevrani commented 4 months ago

@levikobi @LiorLieberman If neither the ingressClassName field nor the kubernetes.io/ingress.class annotation is set on the Ingress, the tool skips processing that Ingress, resulting in no Gateway API resources?

levikobi commented 4 months ago

@levikobi @LiorLieberman If neither the ingressClassName field nor the kubernetes.io/ingress.class annotation is set on the Ingress, the tool skips processing that Ingress, resulting in no Gateway API resources?

At the time I opened this issue this was correct @VasuDevrani, I think this still holds true though. The purpose of this issue is to add support for reading the ingressClasses, one of them should be the default. Then we will be able to convert ingresses without the field or annotation being specified

mlavacca commented 3 months ago

Hi @VasuDevrani, any news on this issue? If you need some help, please let us know :)

kubernetes-sigs / ingress2gateway

Add support for `IngressClass` objects #117

Guidelines

Guidelines