Move to Deployment from DeploymentConfig for investigator and metrics-exporter #2707
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.
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
andmetrics-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.
The text was updated successfully, but these errors were encountered: