-
Notifications
You must be signed in to change notification settings - Fork 8
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
e2e: generate deployment yaml #189
Conversation
Signed-off-by: Paul Meyer <[email protected]>
Signed-off-by: Paul Meyer <[email protected]>
coordinatorForwarder := PortForwarder("coordinator", ns). | ||
WithListenPort(1313). | ||
WithForwardTarget("coordinator", 1313). | ||
PodApplyConfiguration |
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 wonder whether the portforwarder pod should even be part of this bundle, because it's only useful for the corresponding exposure logic in kubeclient I'm implementing in #185.
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.
For now, this is just to fulfill the interface with our current workflow. As we previously discussed, it is unclear if the sets will be called by the e2e at all, or if the e2e tests will just construct their own individual set.
Signed-off-by: Paul Meyer <[email protected]>
Signed-off-by: Paul Meyer <[email protected]>
Signed-off-by: Paul Meyer <[email protected]>
We want to generate the yaml for the tests etc instead of keeping a lot of yaml laying around in-tree. This shifts the source of truth into the Go code. This PR implements a first small step, generating the simple deployment. Patching is still done in the justfile using kypatch.