[License Review Request] kong/blixt

[mrbobbytables]

Kong would like to donate the blixt project to Kubernetes. However, sections of it are licensed under GPL. These sections are eBPF related and linked to kernel code which are obligated to be GPL compatible.

Is this an acceptable use of GPL licensed code that can be accepted by the Kubernetes project? Semi-related, but with the rise in eBPF this might be an issue in general for other projects - is there a good path forward for them?

cc @shaneutt

[leogr]

I can see the logic of @leogr's comment, but since the request for eBPF already got discussed by the Legal Committee I'd say it would make sense to raise kernel module license exceptions as a separate issue for their next meeting

Hey @lizrice Thank you for the response! :pray: How can we make this happen? Let me know if we can assist in some way.

I couldn't find clear information on the approval process for licensing exceptions. Do you know if it is documented somewhere? :thinking:

[shaneutt]

I couldn't find clear information on the approval process for licensing exceptions. Do you know if it is documented somewhere? 🤔

I think I would start by creating an issue like this one, labeled [License Review Request] <org>/<project>?

Also while I'm here: hello everyone! anyone got any news here?

[amye]

Approved by Legal Committee and GB as of a vote for 8-31, minutes will be approved as of the next governing board meeting.

A blanket exception for in-kernel eBPF programs licensed under either of the following licenses, either on its own or dual licensed in combination with any license already on the CNCF Licensing Allowlist Approved Licenses list (e.g., MIT License):

• GPL 2.0
• GPL 2.0 or later

[blixtra]

This is great news!

[astoycos]

Thanks for all the efforts here everyone!! 🎆

[shaneutt]

Yes, thank you! :vulcan_salute: