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

Additional testing and test plans for RKE2 GA and 2.6.7 Rancher #143

Open
7 of 24 tasks
sirredbeard opened this issue Jan 20, 2022 · 8 comments
Open
7 of 24 tasks

Additional testing and test plans for RKE2 GA and 2.6.7 Rancher #143

sirredbeard opened this issue Jan 20, 2022 · 8 comments

Comments

@sirredbeard
Copy link
Contributor

sirredbeard commented Jan 20, 2022

Test Plans

  • Review and update existing QA Test Plans for Windows.

Update QA Test Plans for the following:

  • RKE2 GA Testing - Linux and Windows
  • vSphere Node Provisioning - Linux and Windows
  • vSphere CSI Charts 1.23 for RKE1 and 1.22 RKE2 - Linux and Windows
  • GMSA - Windows
  • Windows Server 2022

Automation Areas

Vagrant

  • Standalone RKE2 Provisioning on PR (Luther) - Linux and Windows

New Go Testing Framework

Sonobuoy Workloads

  • Hybrid Windows/Linux Deployment (Jamie) - Linux and Windows
  • Complex Deployment with vSphere CSI (Jamie) - Linux and Windows

Stretch Goals

  • Add Sonobuoy Workloads to QA Jenkins - Linux and Windows
  • Airgap Provisioning for RKE2 - Linux and Windows

Unit Testing

@phillipsj
Copy link
Contributor

New testing framework: https://github.com/rancher/rancher/tree/release/v2.6/tests

@phillipsj
Copy link
Contributor

Workloads that are used for Linux testing have been provided, and we are going to create equivalents for those on Windows.

@sirredbeard
Copy link
Contributor Author

Have assisted with new framework but currently blocked by lack of custom cluster support.

@rosskirkpat rosskirkpat added this to In Progress in Windows Team 2.6.5 Mar 8, 2022
@rosskirkpat rosskirkpat self-assigned this Mar 8, 2022
@rosskirkpat
Copy link
Contributor

rosskirkpat commented Mar 8, 2022

rancher/rancher#36793

  • lay the ground work for rke2 windows v2prov provisioning tests
  • add vsphere extension to the new framework

@sirredbeard sirredbeard changed the title Automated tests for Windows on RKE2 in new framework Additional testing for Windows on RKE2 GA Mar 22, 2022
@sirredbeard sirredbeard changed the title Additional testing for Windows on RKE2 GA Additional testing and test plans for Windows on RKE2 GA Mar 22, 2022
@ronhorton ronhorton reopened this Mar 22, 2022
@phillipsj
Copy link
Contributor

phillipsj commented Mar 23, 2022

Closing this issue in favor of tracking the work here.

@phillipsj phillipsj changed the title Additional testing and test plans for Windows on RKE2 GA Additional testing and test plans for Windows on RKE2 GA and 2.6.5 Rancher Mar 23, 2022
@phillipsj phillipsj changed the title Additional testing and test plans for Windows on RKE2 GA and 2.6.5 Rancher Additional testing and test plans for RKE2 GA and 2.6.5 Rancher Apr 6, 2022
@phillipsj
Copy link
Contributor

First Sonobuoy plugin that checks for the CPI being installed. rancher/sonobuoy-plugins#1

@sirredbeard sirredbeard changed the title Additional testing and test plans for RKE2 GA and 2.6.5 Rancher Additional testing and test plans for RKE2 GA and 2.6.6 Rancher May 4, 2022
@sirredbeard sirredbeard modified the milestones: v2.6.5, v2.6.6 May 4, 2022
@rosskirkpat
Copy link
Contributor

rosskirkpat commented May 5, 2022

The go testing framework PR is ready for review: rancher/rancher#36793

@phillipsj phillipsj removed this from In Progress in Windows Team 2.6.5 May 25, 2022
@phillipsj phillipsj added this to Proposed in Windows Team 2.6.7 May 25, 2022
@snasovich snasovich changed the title Additional testing and test plans for RKE2 GA and 2.6.6 Rancher Additional testing and test plans for RKE2 GA and 2.6.7 Rancher Jul 7, 2022
@phillipsj phillipsj removed this from the v2.6.7 milestone Jul 19, 2022
@slickwarren
Copy link
Contributor

@aiyengar2 in my opinion this can be closed, as you are handling these cases differently and many of the tasks above have been completed or redesigned in separate requests. Would you close it if you agree?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests