Kong / kubernetes-ingress-controller

:gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
https://docs.konghq.com/kubernetes-ingress-controller/
Apache License 2.0
2.22k stars 593 forks source link

☔ Migrate CRDs to kong/kubernetes-configuration repo #6488

Open randmonkey opened 2 months ago

randmonkey commented 2 months ago

Is there an existing issue for this?

Does this enhancement require public documentation?

Problem Statement

Now we have created kong/kubernetes-configuration repository to store CRDs corresponding to Kong configuration. The repo is expected to be shared by KIC and KGO. We need to import source of CRDs from internal packages to packages in kong/kubernetes-configuration.

Proposed Solution

Additional information

No response

Acceptance Criteria

### Tasks
- [ ] https://github.com/Kong/kubernetes-ingress-controller/issues/6578
- [ ] https://github.com/Kong/kubernetes-configuration/issues/105
- [ ] https://github.com/Kong/kubernetes-ingress-controller/issues/6618
- [ ] https://github.com/Kong/kubernetes-ingress-controller/issues/6579
- [ ] https://github.com/Kong/kubernetes-ingress-controller/issues/6580
- [ ] https://github.com/Kong/kubernetes-ingress-controller/issues/6581
- [ ] https://github.com/Kong/kubernetes-ingress-controller/issues/6635
- [ ] https://github.com/Kong/kubernetes-ingress-controller/issues/6641
- [ ] https://github.com/Kong/kubernetes-ingress-controller/issues/6663
randmonkey commented 1 month ago

It is required for KGO to operate it.

czeslavo commented 3 weeks ago

We should also take care of handling the control plane reference in KIC and ignore objects that are not attached to other CPs (the default is KIC) OR have the reference non-empty and refer to non-KIC CP.