You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What we could have instead is exposing the ContainerSpec in suc and if empty fallback to current as defaults. In that way will be easier later to create a OSUpgradeCatalog of ContainerSpecs based on the os2 derivative
The text was updated successfully, but these errors were encountered:
* Allow to specify a upgradeContainerSpec on ManagedOS
#59
Signed-off-by: Ettore Di Giacinto <edigiacinto@suse.com>
* Run go generate and update wrangler
Also pin golang.org/x/tools to latest, to workaround
golang/go#37617
Signed-off-by: Ettore Di Giacinto <edigiacinto@suse.com>
* Update docs
Signed-off-by: Ettore Di Giacinto <edigiacinto@suse.com>
* Adapt to new wrangler signal context
rancher/wrangler@9460166
Signed-off-by: Ettore Di Giacinto <edigiacinto@suse.com>
* Fixup license headers
Signed-off-by: Ettore Di Giacinto <edigiacinto@suse.com>
Currently os2 applies Plans from
ManagedOS
resources in a hardcoded way: https://github.com/rancher-sandbox/os2/blob/9fed2edefc12cbcb426874db137631f9d52de3cd/pkg/controllers/managedos/template.go#L138 .This doesn't make possible to reuse the
ManagedOS
resource outside theos2
context, and doesn't allow much flexibility if someone wants to customize the upgrade process.What we could have instead is exposing the
ContainerSpec
in suc and if empty fallback to current as defaults. In that way will be easier later to create aOSUpgradeCatalog
ofContainerSpec
s based on the os2 derivativeThe text was updated successfully, but these errors were encountered: