[WIP] Shipperctl installs management and application CRDs independently

[osdrv]

Up until now, shipper has been installing CRD objects to management clusters only and this was a part of shipperctl clusters setup management command. As we're splitting shipper in management and application components, these components need their own CRDs to operate on the relevant cluster.

Therefore, an updated list of CRD groups:

• Management
  • Application
  • Release
  • Cluster
  • RolloutBlock
• Application
  • InstallationTarget
  • CapacityTarget
  • TrafficTarget

Folow-up to: https://github.com/bookingcom/shipper/pull/292

Signed-off-by: Oleg Sidorov oleg.sidorov@booking.com

[osdrv]

The build predictably failed as we test against 2 distinct clusters: kind-mgmt and kind-app. The PR could be put on hold and rebased once targetObjects are migrated to app clusters.

[osdrv]

Implemented in #306