CRD: `ManagedOSVersionChannel` about elemental HOT 5 CLOSED

@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.

from elemental.

Blocked by #67

from elemental.

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"]}]}

from elemental.

Included in rancher-sandbox/rancheros-operator#14

from elemental.

Follow-ups are tracked in #58

from elemental.