Custom plugins are a large part of customer deployments, but getting these plugins deployed and configured with a Kong Gateway instance has been painful. Since KGO aims to offer the E2E operational model for Kong Gateway on Kubernetes it should provide a way to ship and use custom plugins with Kong Gateways deployed and managed by KGO.
[x] based on documents mentioned above spike the option and effort to provide Kong Gateway plugins distribution in KGO (if the implementation is sufficiently complex or consensus is hard to achieve, then the result of this issue should be a design doc)
[ ] create an action plan for implementing this - prepare issues with clear acceptance criteria and prioritize them
lahabana
commented
1 week ago
Problem Statement
Custom plugins are a large part of customer deployments, but getting these plugins deployed and configured with a Kong Gateway instance has been painful. Since KGO aims to offer the E2E operational model for Kong Gateway on Kubernetes it should provide a way to ship and use custom plugins with Kong Gateways deployed and managed by KGO.
Additional Information
Documents to get familiar with
Acceptance Criteria