☔ Migrate CRDs to kong/kubernetes-configuration repo

[randmonkey]

Is there an existing issue for this?

• I have searched the existing issues

Does this enhancement require public documentation?

• I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)

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

• Change import source of CRDs to packages in kong/kubernetes-configuration
• Change the scripts to download CRD manifests from kong/kubernetes-configuration
• Remove CRD packages and CRD manifests in the repo (Should we do this? Maybe there are dependencies elsewhere)

Additional information

No response

Acceptance Criteria

• KIC imports CRDs from kong/kubernetes-configuration repo
• KIC generate manifests from CRDs downloaded from kong/kubernetes-configuration repo
• Documents mentioning CRD download URLs changed to URLs in kong/kubernetes-configuration

Tasks

Beta Give feedback

1. Import CRDs and clientsets from kong/kubernetes-configuration repo #6578
   area/CRD +1
   
2. KIC CRDs reference is generated from kong/kubernetes-configuration types #6618
   area/docs +1
   
3. Generate manifests from CRDs in kong/kubernetes-configuration repo #6579
   area/CRD +1
   
4. Update the URL to download URLs to URLs in kong/kubernetes-configuration #6580
   area/CRD blocked +2
5. Support controlplane reference of KIC type #6581
   area/CRD blocked +2

[randmonkey]

It is required for KGO to operate it.

[czeslavo]

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.