-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
OpenShift Projects and ProjectRequests not ordered appropriately with namespaces #2563
Comments
@tylerauerbeck kustomize build --reorder none ... Using that option you are on your own how to order objects. I use that in combination with OCP successfully, but currently in a 3.11 cluster. Therefore I cannot verify whether that option is included in the latest Of course the fallback solution is to separate the project creation in a setup configuration which is executed on its own first in the chain. |
Thanks @mpreu -- that's what I had thought the case was going to be, but would also like to hear from some of the folks on the kustomize end to see if they've got input as well. I was hoping to be able to stick with features that are available in |
@tylerauerbeck You are maybe referring to something like this #97 and this https://github.com/adnovum/kustomize-openshift (supporting CRDs before When I am not missing something, this method is not allowing for "rewriting" the Unfortunate to see that the CLIs are not integrating a more recent version kubernetes/kubectl#818. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In 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. |
When creating a kustomization that creates Projects/ProjectRequests, kustomize doesn't create these objects in the order that I'd expect. Since Projects/ProjectRequests are functionally namespaces, I would expect them to be created as some of the initial objects just as namespaces are. However it appears that kustomize treats them more like CustomResources and doesn't try to create them until the end of the list (which causes issues for any objects that need to be created in those projects.
Is there anyway (ideally in v2.0.3 which is bundled with
oc
andkubectl
) to force this order?The text was updated successfully, but these errors were encountered: