Community discussion on project name and confusion with Nginx INC. projects

[strongjz]

Throughout the project, there has been confusion around the name with the F5 Nginx Inc open-source and Nginx+ projects.

https://docs.nginx.com/nginx-ingress-controller/intro/nginx-ingress-controllers/

• Isn't NGINX Ingress Controller naming confusing? nginxinc/kubernetes-ingress#1910
• https://www.reddit.com/r/kubernetes/comments/pcexjt/nginx_ingress_controller_v100_is_released_it/
• https://kubernetes.slack.com/archives/CANQGM8BA/p1626703572022300
• https://kubernetes.slack.com/archives/CANQGM8BA/p1629810152486800
• Warning when configuring VirtualServerRoute proxy #5964

We are working with the Nginx inc team on how to best go forward and welcome the community to join the discussion in Slack and on our bi-weekly community meeting.

[strongjz]

/triage accepted
/priority important-longterm

[strongjz]

/assign

[shurup]

As the author of the original issue mentioned here, I am really excited to see this initiative! Thank you, James, and I hope for the best solution for everyone.

[fblgit]

this is not a coincidence :)

Note: this project is different from the NGINX Ingress controller in kubernetes/ingress-nginx repo. See this doc to find out about the key differences.

There is a banner, but I don't think its helping much.. maybe nginxinc-controller would be a better name for them :)

[dims]

cc @swinslow @caniszczyk - thoughts please!

[mrbobbytables]

Created CNCF Service Desk ticket CNCFSD-915 as a pointer 👍

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[strongjz]

/lifecycle frozen

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[k8s-ci-robot]

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/test-infra repository.

[shurup]

Hi @strongjz! Does it mean the name change isn't expected to happen? Or is it just left for consideration on the other side?

[strongjz]

Hi @strongjz! Does it mean the name change isn't expected to happen? Or is it just left for consideration on the other side?

There has been no movement on either side we, @rikatz and I decided to close to this issue.