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

Move to Deployment from DeploymentConfig for investigator and metrics-exporter #2707

Open
harshad16 opened this issue Nov 25, 2022 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@harshad16
Copy link
Member

Is your feature request related to a problem? Please describe.
We follow openshift principles for deployments and have been using deployment config since OCP 3.11, with OCP 4.6 it is observed that openshift recommends using either one based on requirements.
As we have limited resource quota in namespace thoth-infra-stage
where workloads like investigator and metrics-exporter are executed.
with the growth of these applications, it would help with the deployment process
if we update them to the Deployment method instead of DeploymentConfig.
As it would remove the necessity to track the resource utilization by the deploy pod of DeploymentConfig.

https://github.com/thoth-station/thoth-application/blob/master/investigator/base/deploymentconfig.yaml
https://github.com/thoth-station/thoth-application/blob/master/metrics-exporter/base/deploymentconfig.yaml

Describe the solution you'd like
Simple update of investigator and metrics-exporter to deployment

Describe alternatives you've considered
Increasing the resource quota, (which has it whole tendious process of ticketing)
only to be done when required.

@harshad16 harshad16 added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 25, 2022
@harshad16
Copy link
Member Author

/triage accepted
/sig devsecops
/priority important-soon

@sesheta sesheta added triage/accepted Indicates an issue or PR is ready to be actively worked on. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Nov 25, 2022
@harshad16 harshad16 moved this to 🆕 New in Planning Board Nov 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants