-
Notifications
You must be signed in to change notification settings - Fork 229
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
fix: update documentation for support matrix #1370
Conversation
Signed-off-by: matttrach <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGMT.
I left a few comments but they should not block the merging of the PR.
the `release/v4` branch with 4.0.0+ is aligned with Rancher 2.8, | ||
and the `master` branch with 5.0.0+ is aligned with Rancher 2.9. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: maybe removing the leading spaces?
* We have 'out of band' flexibility and are only tied to releasing a new version of the provider when we get a new 2.x Rancher minor version. | ||
|
||
See the [compatibility matrix](docs/compatibility-matrix.md) for details. | ||
|
||
If you are using Terraform to provision clusters on instances of Rancher 2.7 and 2.8, you must have a separate configuration in a separate dir for each provider. Otherwise, Terraform will overwrite the `.tfstate` file every time you switch versions. | ||
If you are using Terraform to provision clusters on instances of Rancher 2.7 and 2.8, | ||
you must have a separate configuration in a separate dir for each provider. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: maybe removing the leading spaces?
Update support matrix information.