Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use rke provider #13

Open
outscale-mdr opened this issue Jul 27, 2022 · 0 comments
Open

Use rke provider #13

outscale-mdr opened this issue Jul 27, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@outscale-mdr
Copy link
Contributor

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
@outscale-mdr outscale-mdr added the enhancement New feature or request label Jul 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant