-
Notifications
You must be signed in to change notification settings - Fork 101
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
Add example of how to use e2e framework with real cluster #149
Conversation
|
Welcome @matrus2! |
Hi @matrus2. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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 is a great contribution. However, since this project is not using Go workspaces yet, the changes introduce new dependencies for the entire project. I would suggest one the followings:
- Just submit a markdown with the code embedded it (recommended)
- Submit the code without the changes to mod.go and document how to run it.
Hi @vladimirvivien, Thank you for quick reply and recommendation. I commented out cloud vendor auth dependencies, added description . The example may be still used with self-managed cluster. Please validate if PR is ok now. Thank you |
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.
Thank you, these changes look great.
I left couple of comments.
examples/real_cluster/README.md
Outdated
|
||
This package shows how the test framework can be used with a real self-managed or cloud vendor managed cluster (AKS/GKE/EKS), since one may want to launch some tests inside the cluster. This example creates a random namespace, deploys simple deployment and if done removes the namespace. | ||
|
||
To properly connect to a cloud provider cluster it is required to import for side effects one of auth module. If testing on self-managed cluster there is no need to include these dependencies. |
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.
module
-> modules
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.
If testing on a self-managed...
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.
fixed
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.
Thanks for the contribution @matrus2 !!
Hi @vladimirvivien, I committed small change to pass CI. Thanks |
/test pull-e2e-framework-test |
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
/test pull-e2e-framework-verify |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: matrus2, ShwethaKumbla, vladimirvivien The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
Hi,
I have been struggling for a while on how to execute e2e tests in the real cloud provider cluster. I though it might be useful to extend examples set by this particular use case.
Thanks