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
Actually, the rke yaml is crafted manually and then we must execute rke initby ourself in order to deploy the cluster.
What could be improve ?
the cluster could become a terraform resource and no more clean omittion
the rke configuration is not easily readable
the rke yaml needs to be maintained by ourself (structure, syntax)
What could be done ?
Suse maintains a rke provider that adds rke cluster as a terraform resource (rancher/terraform-provider-rke).
Drawbacks
Add another layer around rke. We know that kubernetes version are not rapidly upgraded into rke. Here rke needs to be updated intio the provider to become available therefore the user is less free to choose the version he wants
The text was updated successfully, but these errors were encountered:
Actually, the rke yaml is crafted manually and then we must execute
rke init
by ourself in order to deploy the cluster.What could be improve ?
What could be done ?
Suse maintains a rke provider that adds rke cluster as a terraform resource (rancher/terraform-provider-rke).
Drawbacks
The text was updated successfully, but these errors were encountered: