[SIG-Network] Ingress NGINX meeting 20210511

Summary

The transcript captures a meeting of the Ingress Nginx subproject, focusing on addressing and cleaning up open issues, including stale and bug reports. New members introduce themselves, expressing their eagerness to contribute to the Kubernetes community. Discussions revolve around prioritizing issues, understanding the impact of breaking changes, and the need for better versioning and support strategies. The meeting also touches on the importance of adhering to the code of conduct and the collaborative effort to improve the project.

Takeaways

• 🗓️ The meeting took place on May 11th, 2021, focusing on the Ingress Nginx subproject within the Kubernetes community.
• 👥 New members introduced themselves, including those with experience in Kubernetes release engineering and others looking to contribute to the project.
• 📝 The meeting aimed to address stale issues and encourage movement on open issues to clean up the project's backlog.
• 👍 The importance of adhering to the code of conduct, which emphasizes being excellent with each other, was highlighted.
• 🔍 The discussion included reviewing and categorizing issues from the GitHub API to understand the scale of work ahead.
• 📉 There was an emphasis on investigating and potentially deprecating older versions of Nginx that are no longer supported.
• 📝 The process of labeling and managing issues, such as applying 'help wanted' labels, was discussed to encourage community involvement.
• 🔄 The team considered the implications of making breaking changes, such as changing annotations, and the need for clear communication in the changelog.
• 🤔 The challenge of supporting older issues with potentially outdated versions of software was acknowledged, and strategies for addressing these were explored.
• 📋 The need for better issue triage, including requesting more information or testing, was identified to move issues forward.
• 🚀 The meeting concluded with a commitment to continue working through issues and improving the project's development cycle.

Q & A

What was the main purpose of the meeting on May 11th, 2021?

The main purpose of the meeting was to discuss and clean up open issues in the NGINX Ingress subproject, particularly focusing on stale issues, and to encourage new members to introduce themselves and contribute to the project.

What is the expected behavior during the Kubernetes community meeting according to the code of conduct?

Participants are expected to be excellent with each other, adhering to the code of conduct, and any issues should be reported privately to the SIG chairs or meeting organizers.

What is the role of the person who introduced themselves as the 'release note shadow' for Kubernetes 1.22?

The person is responsible for shadowing or assisting with the release notes for the Kubernetes 1.22 version, contributing to the documentation process and ensuring that release information is accurate and complete.

Why did Carlos join the NGINX Ingress subproject meeting?

Carlos joined the meeting because he works on the secret release as a branch manager and also has involvement in Cluster API and Engine X Ingress. He has a space in his heart for the project and wants to contribute and help the community.

What is the primary concern of the user from the startup IoT company mentioned in the script?

The user is looking for options to replace Apache for web services and load balancing, as they are currently using Apache but are interested in exploring alternatives that might better suit their needs.

What is the process for handling issues that are considered stale or rotten in the NGINX Ingress project?

The process involves reviewing the stale or rotten issues to determine if they are still relevant or helpful. If they are not, the tag is removed, and the issues are either updated, closed, or moved forward based on their current relevance and the project's needs.

What is the significance of the 'good first issue' label in the context of the NGINX Ingress project?

The 'good first issue' label is used to identify issues that are suitable for new contributors to work on, providing them with an opportunity to get acquainted with the project and make their first contributions.

Why is the versioning and support of Kubernetes important in the context of the issues discussed in the meeting?

Versioning and support are important because many of the issues discussed are related to older versions of Kubernetes. Understanding the support status helps in determining whether issues are still relevant or if they have been resolved in newer versions.

What is the general approach to addressing issues that require testing with newer versions of Kubernetes?

The approach involves asking the issue submitters or the community to test the issues on newer versions of Kubernetes. This helps in validating whether the issues persist in the current or recent versions of the software.

What is the role of the steering committee in the context of the NGINX Ingress project?

The steering committee may be involved in providing resources such as funding or access to cloud services for testing and replicating issues, especially when such tasks require significant resources or infrastructure.

How does the NGINX Ingress project handle breaking changes in annotations or other features?

The project follows semantic versioning, and breaking changes typically involve revising the version number. It's important to communicate these changes clearly in the changelog to ensure users are aware of the impact and necessary actions, such as redeployment.