In this directory you'll find documents which use the upstream Kubernetes Enhancement Proposals (KEP) as a guideline to propose changes and improvements in the Kong Kubernetes Ingress Controller (KIC).
In a general sense we try to follow the upstream KEP template and rules, but it's more important that we are able to express our motivations, goals, non-goals, design, and history about improvements than it is to rigorously follow any process, so note that you may encounter some variance from upstream and the KIC maintainers consider KEP more of a guideline, so we're not super strict on form.
If you want to write a new KEP the basic process is:
- copy the upstream KEP template
- focus on Summary, Motivation, Goals, and Non-Goals for the first iteration (we try to avoid technical implementation details when first exploring a new proposal)
- delete any sections not in use (they can be added back later)
- submit a PR with the bare minimum content required to express what you would like to see improved
If you want to contribute but you're feeling a bit stuck, feel free to catch us in #kong on Kubernetes Slack for help!