Skip to content
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

Merged
merged 5 commits into from
Mar 5, 2024
Merged

e2e: generate deployment yaml #189

merged 5 commits into from
Mar 5, 2024

Conversation

katexochen
Copy link
Member

@katexochen katexochen commented Mar 4, 2024

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.

@katexochen katexochen marked this pull request as draft March 4, 2024 14:00
Signed-off-by: Paul Meyer <[email protected]>
@katexochen katexochen requested a review from burgerdev March 4, 2024 14:24
@katexochen katexochen marked this pull request as ready for review March 4, 2024 14:24
e2e/internal/kuberesource/sets.go Outdated Show resolved Hide resolved
Comment on lines +10 to +13
coordinatorForwarder := PortForwarder("coordinator", ns).
WithListenPort(1313).
WithForwardTarget("coordinator", 1313).
PodApplyConfiguration
Copy link
Contributor

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.

Copy link
Member Author

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.

@katexochen katexochen merged commit eebbc03 into main Mar 5, 2024
6 checks passed
@katexochen katexochen deleted the p/yml-e2e branch March 5, 2024 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants