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

Support for VirtualServer and other CRDs in ingress-nginx controller #12221

Closed
mnestian97 opened this issue Oct 21, 2024 · 3 comments
Closed
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@mnestian97
Copy link

mnestian97 commented Oct 21, 2024

Hi,
I have a question regarding the support for custom resources like VirtualServer and other CRDs (e.g., VirtualServerRoute, TransportServer, etc.) in the community-supported version of the ingress-nginx controller from Kubernetes.

I am aware that these custom resources are available in the nginx-controller supported Nginx INC, but I would like to clarify if they are also supported by this ingress-nginx controller.

If not, is there any planned support for them in the future?
Are there alternative ways to achieve similar functionality using the community version?
Your help would be greatly appreciated, as this would help us determine the best approach for our ingress use case.

@mnestian97 mnestian97 added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 21, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Oct 21, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@longwuyuan
Copy link
Contributor

@mnestian97 unfortunately the answer to all the questions is a "no".

This community controller is not sharing code with any other. And due to severe problems, a decision has been made to even deprecate features that are impossible to support & maintain. All that while implementing the Gteway-API.

Hopefully you would find solutions in the Gateway-API implementation in the future. Thanks

/close

@k8s-ci-robot
Copy link
Contributor

@longwuyuan: Closing this issue.

In response to this:

@mnestian97 unfortunately the answer to all the questions is a "no".

This community controller is not sharing code with any other. And due to severe problems, a decision has been made to even deprecate features that are impossible to support & maintain. All that while implementing the Gteway-API.

Hopefully you would find solutions in the Gateway-API implementation in the future. Thanks

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Development

No branches or pull requests

3 participants