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

doc: state the reason to build csi-sidecars #825

Merged
merged 1 commit into from
Jan 22, 2024

Conversation

satoru-takeuchi
Copy link
Member

We build csi-sidecars in our own. It's convenient for developers to clarify why we do so.

Fixes: #822

We build csi-sidecars in our own. It's convenient for developers
to clarify why we do so.

Fixes: #822

Signed-off-by: Satoru Takeuchi <satoru.takeuchi@gmail.com>
@ryanfaircloth
Copy link
Contributor

While the reason makes sense on the surface any emergency would likely impact all similar projects equally has this ever occurred is the overhead actually worth the reword. As a counter point I think a more likely issue is conflict with a distro provided side car, aks, eks and open shift all provide their own builds. Redhat does not use the project container ,building their own. While there reason you raise is valid it appears to me to simply be a trade off. As a middle ground the project could build and provide the side cars as independent builds and default to use those images or make that a option selected as part of the deployment

@peng225 peng225 merged commit 7ecf7a0 into main Jan 22, 2024
9 checks passed
@peng225 peng225 deleted the state-the-reason-to-build-csi-sidecars branch January 22, 2024 01:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
4 participants