CRD structure prepared

[akgalwas]

Description

This PR defines contract between the Kyma Environment Broker, and the Infrastructure Manager.
There are the following assumptions:

• shoot name, and secret name must be passed to the Infrastructure Manager
• the GardenerCluster should be in 1:1 relation with shoot
• there will be exactly one secret for a particular GardenerCluster instance
• properties introduced in the first CR version should be grouped in an object, to allow to extend the CR easily
• the GardenerCluster CR should be namespaced
• KEB should create the Gardener Cluster CR in the following manner:
  • CR's name should be the same as RuntimeID.
  • CR's should contain the same set of labels as the secret KEB currently creates

Changes proposed in this pull request:

• CRD renamed to Gardener Cluster
• CRD contains secret name, namespace, and key name
• CRD contains status
• Example prepared

Related issue(s)
#9

[Disper]

Is this PR still a WiP? I'm unable to find the following parts:

• CRD contains the following data: shootName, secretName
• Example prepared

[Disper]

The Project Config(...) will store all plugins and input data used to generate the project and APIs to better enable plugins to make useful decisions when scaffolding.

Should anything else be adjusted (or re-scaffolded ?) after this change? It's just not clear to me how this setting is exactly used.

[akgalwas]

I did run make test and nothing was changed. I assume the change in CRD is enough.

[piotrmiskiewicz]

The GardenerCluster sample looks ok