-
Notifications
You must be signed in to change notification settings - Fork 526
Rework gardenadm
kustomizations (move to /dev-setup
)
#12331
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
Conversation
aa22627
to
9813fc2
Compare
9813fc2
to
6d3a70f
Compare
/assign |
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.
Generally lgtm.
Thanks for your efforts on reworking this mess 😄
…ardenadm` In a later commit, they will actually be moved to `/dev-setup/gardenadm/resources`.
It doesn't fit perfectly there since it is not a typical Kustomize component/part, but it doesn't make sense to move it elsewhere, so let's live with it.
…tup/gardenadm/resources` Since this `resources` folder is no typical Kustomize part anyways, let's also move the other files there so that they are at one place.
`/dev-setup/extensions/networking-{calico,cilium}` now have the same structure like `/dev-setup/extensions/provider-local`
Otherwise, `gardenadm` might complain if we put the generated files into the same directory that also contains the `kustomzation.yaml`: ``` Error: failed reading Kubernetes resources from config directory ./dev-setup/gardenadm/resources/medium-touch: failed reading Kubernetes resources from config directory: failed decoding resource at index 0 in kustomization.yaml: no kind "Kustomization" is registered for version "kustomize.config.k8s.io/v1beta1" in scheme "pkg/runtime/scheme.go:110" exit status 1 ```
6d3a70f
to
50717ac
Compare
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!
/lgtm
LGTM label has been added. Git tree hash: a733c181a818c3075463400d111a407c9c0cee6c
|
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.
The new dev-setup is growing. Nice 🚀
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: oliver-goetz 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 |
How to categorize this PR?
/area dev-productivity
/kind cleanup
What this PR does / why we need it:
This PR reworks the dev/e2e setup for
gardenadm
in the/dev-setup
folder/dev-setup/gardenadm/machines
contains the machine config for the high-touch scenario (machineStatefulSet
and related resources)/dev-setup/gardenadm/resources
is a Kustomization with overlays for the high-touch and the medium-touch scenariomanifests.yaml
from theresources
Kustomization, but also the.skaffold-image
and.imagevector-overwrite.yaml
) are stored in/dev-setup/gardenadm/resources/generated
Now, there should be no
gardenadm
dev/test setup-related config anymore in theexample
folder.Which issue(s) this PR fixes:
Part of #11958
Special notes for your reviewer:
/cc @timebertt @oliver-goetz
Release note: