-
Notifications
You must be signed in to change notification settings - Fork 614
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
Add a dry-run mode to flux build kustomization #3317
Conversation
The reason to this is because MakeSecureFSOnDisk is not consistent between OS. Signed-off-by: Soule BA <soule@weave.works>
3f9dfcb
to
ce3688b
Compare
ce3688b
to
e514b3e
Compare
7bd769e
to
482cf09
Compare
If implemented user will be able to use `flux build kustomization` without any connection to the cluster. Signed-off-by: Soule BA <soule@weave.works>
482cf09
to
ad5daee
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.
Given the introduction of the secure FS was more to ensure the behavior between controller and CLI was the same, rather than offering a real security layer (which is more up to the OS and user space in non multi-tenant environments). I am fine with these changes.
Thanks @souleb 🙇
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.
LGTM
Thanks @souleb 🏅
so I assume this will be included into the next release? do you mind sharing when is the next release (approx)? |
Verified fixed in 0.37.0. Had the same issue as #2785 in 0.36.0 |
yep, works on 0.37.0 for me as well |
Signed-off-by: Soule BA soule@weave.works
fixes #2785
This is has to be merged after fluxcd/pkg#392.
If implemented user will be able to use
flux build kustomization
without any connection to the cluster.This also revert the use of
MakeSecureFSOnDisk
, mainly because it is not consistent between OS. It was also not used in theflux/pkg/kustomize
generator, so it was still possible to by-pass the enforcement.