-
Notifications
You must be signed in to change notification settings - Fork 0
Configure tests / Begin set up for all K8 resources #4
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per #1 the tests from kubetest2 are running, but they currently get stuck at the end of the initialization phase with the error:
I suspect there is supposed to be an additional message, but, none seems to appear...
In the meantime, I figure I can work on getting the rest of the resources ready, then come back to looking into that error (which will hopefully speed up testing once the error is fixed) which I started to do on this branch before realizing it should probably be done on a new branch; however, I am going to leave those changes in this PR in case anyone else picks this up.
The commits that could probably be in a different branch are:
64bf9b5
35d9bb0
8b97cad