Update Twistlock to v30
This MR contains the following updates:
| Package | Update | Change |
|---|---|---|
| registry1.dso.mil/ironbank/twistlock/console/console | major |
22.12.415 -> 30.02.123
|
| registry1.dso.mil/ironbank/twistlock/defender/defender | major |
22.12.415 -> 30.02.123
|
Configuration
-
If you want to rebase/retry this MR, click this checkbox.
This MR has been generated by Renovate Bot.
Merge request reports
Activity
mentioned in issue #70 (closed)
assigned to @dhilgaertner2
added statusdoing label
added 1 commit
- 41d4753e - Modifications to dashboards as per maintanance doc
@dhilgaertner2 per the vendor (and release notes), Twistlock Big Bang users must ensure they are running 22.12.415 before they attempt to upgrade to 30.01.153. 22.06.x users must upgrade to 22.12.x before making the jump to 30.x. There are some breaking changes in the way some configuration items are stored in JSON (e.g., runtime container policies).
Resolved by Michael Martin@phillip.warner Thanks for the information. Do you have a few to discuss this today?
- Last reply by Phillip Warner
-
@dhilgaertner2 @andrew_vu is this MR ready for testing? (I see the pipeline clean install job failed)
When this is ready for testing, I'd like to deploy it to a representative environment.
Edited by Phillip Warner -
@phillip.warner Yea this MR is ready for testing but I haven’t been able to do so successfully before my leave. I should be back tomorrow to try again if anyone is also stuck on the testing.
-
@phillip.warner it looks like the clean install pipeline is failing due to a cypress failure. How would I go about getting additional information about the cypress tests that failed. Am I missing some additional details in this log? https://repo1.dso.mil/big-bang/product/packages/twistlock/-/jobs/23903522#L171
added 1 commit
- 65305781 - Testing to see if increasing timeout resolves issues in CleanInstall pipeline