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.

Sign up for GitHub

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

Jump to bottom

Split KubernetesProcessor into pieces #12545

Closed
iocanel opened this issue Oct 6, 2020 · 2 comments · Fixed by #12655
Closed

Split KubernetesProcessor into pieces #12545

iocanel opened this issue Oct 6, 2020 · 2 comments · Fixed by #12655
Assignees
@iocanel
Labels
area/kubernetes kind/enhancement New feature or request
Milestone
1.10.0.CR1

Comments

@iocanel
Copy link
Contributor

iocanel commented Oct 6, 2020

Description
Currently, the KubernetesProcessor is pretty fat and handles everything Kubernetes related including Openshift and Knative specific stuff. These should be handled by different classes that will communicate with the KubernetesProcessor via build items.

In the future, these classes should even move to their own modules. But for now a bit of cleaning up is good enough.
@iocanel iocanel added the kind/enhancement New feature or request label Oct 6, 2020
@quarkusbot
Copy link

/cc @geoand

@iocanel iocanel self-assigned this Oct 21, 2020
@iocanel
Copy link
Contributor Author

iocanel commented Oct 23, 2020

This can be closed now that #12655 is merged

@iocanel iocanel linked a pull request Oct 23, 2020 that will close this issue
Kubernetes cleanup #12655
Merged
@iocanel iocanel closed this as completed Oct 23, 2020
@gsmet gsmet added this to the 1.10 - master milestone Oct 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iocanel iocanel

Labels
area/kubernetes kind/enhancement New feature or request
Projects
None yet
Milestone
1.10.0.CR1
Development

Successfully merging a pull request may close this issue.

Kubernetes cleanup iocanel/quarkus
3 participants
@iocanel @gsmet @quarkusbot