pantsel/konga

[enhancement/feature] Ingress Controller persistence

Open

#319 创建于 2019年1月7日

在 GitHub 查看
 (2 评论) (1 反应) (0 负责人)JavaScript (4,258 star) (810 fork)batch import
enhancementhelp wanted

描述

When installed as an Ingress Controller (this is not a bug) Kong only respects configs saved to the cluster as CRDs. This means that it deletes any config set in Konga UI (i.e. it is useless to create resources with Admin API).

A really nice feature for Konga would be the ability to save changes as CRDs into a cluster instead of saving them with Admin API.

The known CRDs are:

  • KongConsumer
  • KongCredential
  • KongPlugin
  • KongIngress

贡献者指南

技术栈
javascriptkubernetes
领域
backendinfrastructurecloud
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Kubernetes CRDsKonga internalsNode.jsKong Ingress Controller
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
15
研究方向
First, understand the existing Konga codebase, especially how it interacts with the Kong Admin API (likely in services or controllers). Review the Kubernetes CRD definitions for Kong (e.g., KongConsumer, KongPlugin) in the Kong Ingress Controller repository. Then, explore how Konga could be extended to generate Kubernetes manifests instead of direct API calls. Consider creating a new module in Konga that handles CRD creation. Look at existing issues or discussions in the repository for prior analysis. Discuss with maintainers on what approach they prefer.