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.

Sign up for GitHub

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

Jump to bottom

[2.6.7] Deprecate RKE1 Windows provisioning capabilities due to EOL #343

Open
rosskirkpat opened this issue May 19, 2022 · 2 comments
Open

[2.6.7] Deprecate RKE1 Windows provisioning capabilities due to EOL #343

rosskirkpat opened this issue May 19, 2022 · 2 comments
Labels
team/area2

Comments

@rosskirkpat
Copy link

rosskirkpat commented May 19, 2022 •
edited
Loading

As part of the RKE1 Windows EOL upcoming in Rancher v2.6.6, we need to deprecate the provisioning of new RKE1 Windows clusters in the rke terraform provider.

rancher/windows#179
rancher/windows#182
@rosskirkpat rosskirkpat changed the title [2.6.6] Remove RKE1 Windows provisioning due to EOL [2.6.6] Remove RKE1 Windows provisioning capabilities due to EOL May 19, 2022
@paynejacob
Copy link

@rosskirkpat 2.6.6 is scheduled to be released before September do we want to disable this functionality before then or wait for a later release?

@rosskirkpat
Copy link
Author

@paynejacob Yes, the functionality needs to be deprecated and include a warning when someone tries to use the resource(s) but not removed.

@rosskirkpat rosskirkpat changed the title [2.6.6] Remove RKE1 Windows provisioning capabilities due to EOL [2.6.6] Deprecate RKE1 Windows provisioning capabilities due to EOL Jun 14, 2022
@snasovich snasovich changed the title [2.6.6] Deprecate RKE1 Windows provisioning capabilities due to EOL [2.6.7] Deprecate RKE1 Windows provisioning capabilities due to EOL Jul 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
team/area2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@paynejacob @rosskirkpat