Add Cluster creation test #192
Merged
Conversation
This file contains 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.
Ref:
This PR adds a first Cluster creation test.
It will check for the readiness state of the server and kubelet, and it will wait for the bootstrap secret to be created.
Note that we are not yet checking for it to be "functional". A next PR will be made, after a small check and refactor of the kubeconfig generation.
The
PullPolicyfor the kubelet was removed, with the defaultIfNotPresent. This is because we are pushing dev images locally, and they do not exists in the remote registry.For testing development you should be aware that the image in your environment could be cached, and other tags should be used instead. Using the
latesttag should enable theAlwayspolicy.We could think adding a dedicated environment variable, or enable this strategy when the
debugis true.