[SIG-Network] Ingress NGINX meeting 20210706

Summary

The July 6, 2021 Kubernetes community meeting focused on welcoming new member Carol Chan from F5 and addressing various technical issues. The team discussed unlabeled support requests, including a potential bug with set timeouts, the challenge of retaining source IP in UDP streaming, and scaling issues during load testing. They also touched on template updates for issue reporting and branch management for the upcoming v1 release. The meeting concluded with action items and a plan for a new release to align with Kubernetes v1.22.

Takeaways

• 📅 The meeting took place on July 6, 2021, and was focused on the Kubernetes community with an emphasis on following the code of conduct.
• 🔐 Any violations of the code of conduct should be reported privately to the SIG chairs or the meeting organizer.
• 👋 A new member, Carol Chan, introduced herself, joining from the F5 team with 15 years of experience, and will assist with technical project management.
• 🔍 The meeting agenda included issues triage and action items, with a focus on unlabeled support requests that are over a month old.
• 🆚 Discussion on a potential bug involving 'set timeout' and 'set timeouts' functions in the Lua part of the project, where there is confusion about the correct usage.
• 👷‍♂️ There was a debate on whether certain issues were bugs or not, and the need for more information to make accurate assessments.
• 🛑 A suggestion to close an issue regarding retaining the source IP during UDP streaming, as it may not align with the ingress controller's purpose.
• 📝 A mention of a template for reporting issues to ensure consistency and provide necessary information for triage.
• 🚀 The importance of branch management and the release of v1.8.0 were discussed, with updates on the progress of addressing related issues.
• 🔄 The need for testing and feedback on the new version of the ingress controller, especially from those who have mistakenly deployed the wrong manifest.
• 🗂️ A discussion on manifest files and the need to update documentation to avoid confusion, especially regarding the stable version of the ingress controller.

Q & A

What is the main purpose of the meeting described in the transcript?

The main purpose of the meeting is a Kubernetes community meeting focused on discussing issues and action items related to the Sign Network Ingress Engineer subproject.

What is the Code of Conduct mentioned in the meeting?

The Code of Conduct is a set of guidelines that participants are asked to follow, which essentially involves being excellent with each other, and any violations should be reported privately to the SIG chairs or the meeting organizer.

Who is Carol Chan and what is her role in the meeting?

Carol Chan is a new participant who has joined from the F5 team. She has been with F5 for 15 years and recently moved to the NGINX side. She will be assisting with technical project management and providing direction to the team.

What is the issue with the 'setTimeout' and 'setInterval' functions discussed in the meeting?

The issue discussed is that there are two functions with similar names but different numbers of arguments, which is causing confusion. The meeting participants are unsure whether the complaint about the functions is valid or if the code is correct.

What is the approach to handling unlabeled support requests in the meeting?

The approach is to go through the unlabeled support requests, especially those that are a month old and have not been addressed, to ensure they are properly labeled and triaged.

Why is the issue about retaining the source IP during UDP streaming considered not an issue?

The issue is considered not an issue because when using NGINX as a proxy, it naturally creates a new stream, and retaining the source IP in such a context is not typical behavior for an ingress controller.

What is the general approach to dealing with issues that require more information?

The general approach is to ask the issue reporter to follow a template that provides necessary information, such as the NGINX version, service details, and configuration. If the information is not provided, the issue is labeled as 'needs-information'.

What is the significance of the 'v1' and 'v1beta1' admission webhook in the context of the meeting?

The 'v1' and 'v1beta1' admission webhooks are significant because the team is discussing the transition and support for these versions in the context of Kubernetes updates and ensuring compatibility.

What is the role of the 'stable.txt' file mentioned in the meeting?

The 'stable.txt' file is used to point to the stable version of the manifests for users, especially when there have been changes that could break compatibility with older versions, ensuring users are directed to the correct resources.

What is the plan for the next release of the ingress controller?

The plan is to release a new version, likely v0.48, after addressing certain issues and completing cherry picks of changes like the 'modsecurity' updates and other optimizations, ensuring compatibility with the upcoming Kubernetes v1.22 release.