-
Notifications
You must be signed in to change notification settings - Fork 34
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
chore: bump go and k8s version to fix the DOS Vulnerability #506
chore: bump go and k8s version to fix the DOS Vulnerability #506
Conversation
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
k8s.io/api v0.30.2 | ||
k8s.io/apimachinery v0.30.2 | ||
k8s.io/client-go v0.30.2 |
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.
This will break chaos-mesh
.
But as it is not in use at the moment, we should be fine doing that.
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.
Agreed. Once we decide to merge chaos mesh, we can choose a working k8s version.
…-k8s-version-to-fix-the-DOS-Vulnerability
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.
Is it on purpose to not merge this into main?
baebcf6
into
mojtaba/457-removing-loadEnvVars
Since the SantizeName is not yet removed on main, the tests would panic if we merge it into the main. So it is merged into another branch that has that SanitizeName fixed |
* chore: Deploy timeout-handler before traefik and minio * chore: removing the loadEnvVars func * chore: rename TestScope field (#504) * chore: docs updated * chore: bump go and k8s version to fix the DOS Vulnerability (#506) * chore: rename TestScope field * chore: bump k8s version to fix the DOS Vulnerability * chore: bumped go version to fix it * chore!: remove Executor from knuu (#508) * chore: rename TestScope field * chore: bump k8s version to fix the DOS Vulnerability * chore: bumped go version to fix it * chore: deprecate Executor * fix: rename the deprecated NewExecutor * chore: refactor e2e system tests to new knuu obj (#520) * chore: refactor system e2e tests to new knuu obj * fix: added missing commit before start * fix: added missing commit before start * fix: added missing commit before start * chore: code cleanup * chore: some more cleanup * fix: a typo in err var
Closes #505