New CRD for custom Kong Plugin installation

[programmer04]

Problem Statement

A new CRD for dealing with Kong Plugins is needed. It needs to have well-thought fields that won't require changes in the future it should be extensible and take into account adding in the foreseeable future.

• https://github.com/Kong/gateway-operator/issues/372

Of course, fields for signature verification are not in the scope of this issue.

Related Kubernetes controller typical boilerplate has to be generated too.

Proposed Solution

There is an initial proposition presented in Kong Gateway Plugins distribution that can be used as a starting point, inspiration. Naming hasn't been decided yet the proposed options for now are

• KongPluginInstallation
• KongPluginInstance

Acceptance Criteria

• [ ] There is a new CRD with well thought fields that serves the purpose
• [ ] There is all controller-related boilerplate code generated and ready for filling with proper implementation in subsequent tasks

[lahabana]

Do not forget to consider status as well