docs: update NEXT.md with Post-v1.15.0 changes

[oilbeater]

Summary

• Add Post-v1.15.0 section to NEXT.md with user-facing changes merged since v1.15.0
• Covers new features, reliability, performance, security improvements, and Helm chart enhancements

Test plan

• Verify NEXT.md format matches existing conventions
• Verify all PR links are valid

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @oilbeater, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the NEXT.md document to include a new "Post-v1.15.0" section. This section enumerates significant user-facing changes, new features, and improvements across various domains such as networking, reliability, performance, security, and Helm chart configurations that have been merged since the v1.15.0 release.

Highlights

• NetworkPolicy Enhancements: NetworkPolicy now supports provider-scoped policies for multi-network pods using the ovn.kubernetes.io/policy-for annotation.
• IP/MAC Management: Added support for static IP/MAC configurations for multiple interfaces on the same logical switch.
• MetalLB Integration: MetalLB underlay integration has been extended to support IPv6 and dual-stack environments.
• KubeVirt Improvements: KubeVirt live-migration multi-chassis options now apply to all VM NICs, not just the primary one.
• CRD Usability: Human-readable descriptions were added to all Kube-OVN CRD fields to improve kubectl explain output.
• VPC NAT Gateway Flexibility: User-defined annotations are now supported on NAT gateway Pod templates.
• Interconnection Conflict Avoidance: Vendor IDs were added to transit switches to prevent conflicts with other OVN controllers.
• Reliability Improvements: Enhanced OpenFlow synchronization to detect and recover from stale/missing OVS flows, and improved OVN DB recovery by backing up Raft headers.
• Performance Optimizations: Memory usage was reduced by stripping managedFields from the informer cache, and API server load was decreased by adding field selectors to the informer factory.
• Security Hardening: RBAC configurations were tightened by replacing wildcard verbs with explicit lists and specifying ephemeral storage limits for containers.
• Helm Chart Configurability: The Helm chart now allows configuring DaemonSet update strategy, introducing extraEnv for all components, and adding affinity and nodeSelector support for ovs-ovn and ovs-ovn-dpdk DaemonSets, along with an external-gateway-config-ns option for the controller.

Changelog

• NEXT.md
  • Added a new "Post-v1.15.0" section detailing features and improvements.
  • Updated the document to reflect changes merged into the master branch for the next minor release.

Activity

• The pull request content was generated using Claude Code.
• The author verified the NEXT.md format matches existing conventions.
• The author verified all PR links are valid.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the NEXT.md changelog with changes for the upcoming v1.15.0 release. The changes are well-structured and informative. I've added a few minor suggestions to improve formatting consistency for technical terms, which will enhance readability.

[gemini-code-assist]

For consistency with how OVS is formatted elsewhere in this file (e.g., line 64), it's recommended to wrap OpenFlow and OVS in backticks to improve readability.

Suggested change

	- OpenFlow synchronization: detect and recover from stale or missing OVS flows automatically. [#6117](https://github.com/kubeovn/kube-ovn/pull/6117)
	- `OpenFlow` synchronization: detect and recover from stale or missing `OVS` flows automatically. [#6117](https://github.com/kubeovn/kube-ovn/pull/6117)

[gemini-code-assist]

For consistency with how OVN is formatted elsewhere in this file (e.g., line 64), it's recommended to wrap OVN DB and Raft in backticks. Raft is a proper name for a consensus algorithm and should be formatted as code.

Suggested change

	- OVN DB: back up Raft header before rejoining cluster to improve recovery. [#6106](https://github.com/kubeovn/kube-ovn/pull/6106)
	- `OVN DB`: back up `Raft` header before rejoining cluster to improve recovery. [#6106](https://github.com/kubeovn/kube-ovn/pull/6106)

[gemini-code-assist]

For consistency, it's recommended to wrap ovs-ovn and ovs-ovn-dpdk in backticks, as they are component names.

Suggested change

	- Add `affinity` and `nodeSelector` support for ovs-ovn and ovs-ovn-dpdk DaemonSets. [#6308](https://github.com/kubeovn/kube-ovn/pull/6308)
	- Add `affinity` and `nodeSelector` support for `ovs-ovn` and `ovs-ovn-dpdk` DaemonSets. [#6308](https://github.com/kubeovn/kube-ovn/pull/6308)