CRD: ManagedOSVersionChannel

[mudler]

Part of #58

Create the following new CRDs and controller for the resources types described below

ManagedOSVersionChannel and the controller

the ManagedOSVersion resources are populated by a controller, or either a kubernetes mechanism that satisfy ManagedOSVersionChannel source and constraints. The ManagedOSVersionChannel can be defined as such:

apiVersion: rancheros.cattle.io/v1
kind: ManagedOSVersionChannel
spec:
  type: "JSON"
  options: # map[string]interface{}
       url: "<file>.json"

where a type of channel (e.g. JSON, URL, XML, Github) populates ManagedOSVersions by using the specified options

It defines with which rules ManagedOSVersion should be populated (e.g. github repository tags, releases, a custom json file to parse)

The controller make sure to add labels/annotations where appropriately to notify that a ManagedOS version can be applied.

Ping the harvester team about their strategy and if it does cover their use cases too. Note they might have already a json file or something similar for their available versions, in which we might want to sync up within this card as we want to collect as much feedback as possible at this stage.

cc @bk201

[mudler]

Blocked by #67

[mudler]

I just had a quick look at the harvester code base to see how this is implemented specifically in their use case so we can cover their usage too:

• Harvester Version spec: https://github.com/harvester/harvester/blob/08453c7a9a2a9c8ba629229125705968784860a0/pkg/apis/harvesterhci.io/v1beta1/version.go#L21
• Harvester mechanism to keep in sync and fetch new available versions: https://github.com/harvester/harvester/blob/master/pkg/controller/master/upgrade/version_syncer.go#L96
• Release channel file: https://github.com/harvester/harvester/blob/9091d7d0de9e99ddc677e32c988d758065f87fbb/pkg/settings/settings.go#L33
  which can be tested with:

❯ curl -X POST https://harvester-upgrade-responder.rancher.io/v1/checkupgrade --header "Content-Type: application/json" -d '{ "HarvesterVersion": "v1.0.0" }'
{"versions":[{"name":"v0.2.0-rc4","releaseDate":"2021-04-26T22:00:00Z","tags":["latest"]}]}

[bk201]

@mudler Just want to add this might change slightly because we don't want to add custom fields to the responder. More detail about a version will be retrieved from another URL.

[mudler]

Included in rancher-sandbox/rancheros-operator#14

[mudler]

Follow-ups are tracked in #58