Allow multiple kustomization paths#659
Conversation
0cf97bb to
c926dea
Compare
|
/test |
|
@mangelajo: The
The following commands are available to trigger optional jobs:
Use
DetailsIn response to this:
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. |
This extends the single path /var/lib/microshift/manifests default into: - /usr/lib/microshift/manifests - /etc/microshift/manifests - /var/lib/microshift/manifests which will be evaluated in order. While the first one could be fully managed in ostree (core components), the second one could be managed by configuration management, the third one is maintained for backwards compatibility purposes. In addition the MicroShift configuration file supports customization of this via the manifestsDir entry.
c926dea to
241994b
Compare
|
/retest |
|
Thanks for the PR! I think we should test a specific config.yaml pointing at a set of manifests. Code wise looks good. |
|
|
It seems to work as expected :-) |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: oglok The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This commit documents the behaviour implemented in openshift/microshift#659
This commit documents the behaviour implemented in openshift/microshift#659
This extends the single path /var/lib/microshift/manifests
default into:
which will be evaluated in order. While the first one could be fully
managed in ostree (core components), the second one could be managed
by configuration management, the third one is maintained for backwards
compatibility purposes.
In addition the MicroShift configuration file supports customization
of this via the manifestsDir entry.