-
Notifications
You must be signed in to change notification settings - Fork 83
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 CI #803
Fix CI #803
Conversation
Fixed and related to helm/kind-action#42 the fix was to upgrade to 0.11.1 (kind) |
@@ -29,16 +29,3 @@ EOF | |||
# connect the registry to the cluster network | |||
# (the network may already be connected) | |||
docker network connect "kind" "${reg_name}" || true | |||
|
|||
# Document the local registry | |||
cat <<EOF | kubectl apply -f - |
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.
We actually don't need this
kubever: [ "v1.17.0", "v1.18.0", "v1.19.0", "v1.20.0" ] | ||
# See https://kubernetes.io/releases for the current releases | ||
kubever: [ "v1.19.0", "v1.20.0", "v1.21.1" ] | ||
fdbver: ["6.2.30", "6.3.15"] |
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.
I think it makes sense to test at least these version (we could also test 6.1
but I think 6.2
and 6.3
is fine.
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.
Lgtm 👍
Description
Fixes: #802
Please include a summary of the change and which issue is addressed. If this change resolves an issue, please include the issue number in the description.
Type of change
Please select one of the options below.
Discussion
Are there any design details that you would like to discuss further?
Testing
Please describe the tests that you ran to verify your changes. Unit tests?
Manual testing?
Do we need to perform additional testing once this is merged, or perform in a larger testing environment?
Documentation
Did you update relevant documentation within this repository?
If this change is adding new functionality, do we need to describe it in our user manual?
If this change is adding or removing subreconcilers, have we updated the core technical design doc to reflect that?
If this change is adding new safety checks or new potential failure modes, have we documented and how to debug potential issues?
Follow-up
Are there any follow-up issues that we should pursue in the future?
Does this introduce new defaults that we should re-evaluate in the future?