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

Drop support for routine versus pod building strategy #5967

Open
squakez opened this issue Nov 28, 2024 · 0 comments
Open

Drop support for routine versus pod building strategy #5967

squakez opened this issue Nov 28, 2024 · 0 comments
Labels
kind/discussion kind/feature New feature or request
Milestone

Comments

@squakez
Copy link
Contributor

squakez commented Nov 28, 2024

The necessity to support the routine building strategy is a kind of a limitation as it requires the operator to be able to manage the operations concerns and the build concern, delegating this to some external Maven processes but on the same running Pod. I think that we should remove the support of routine entirely, letting the operator to spin off a Pod and perform the build accordingly as it already happens with pod strategy. This would simplify the design and maintenance of the project and likely the usage of the operator with one less concern to care. Anyway it would be something to consider in a major release only. Feedback are welcome.

@squakez squakez added the kind/feature New feature or request label Nov 28, 2024
@squakez squakez added this to the 3.x milestone Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/discussion kind/feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant