You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe. Tailor is a self-developed component of OpenDevStack (ODS) whose active development has ceased and is logically superseded by Helm.
As a user I require having control of the k8s resources I need for my components/deployments (actively or passively).
As a support team member of ODS I can give better/faster support if resources are defined as code, in the same repository.
Describe the solution you'd like
We want to provide a base chart in the most generic ODS quickstarter component, in the docker-plain. This will be the baseline for the other ODS quickstarters and for existing components in existing running ODS installations.
We want to provide such baseline with proper documentation of how to use common resources: Environment vars, config maps, secrets, storage, replicas, resource requirements, metadata, network policies, cert-manager, ...
We want to transition from the deprecated DeploymentConfig resource type to Deployment.
We want to provide a change that is not a hard-cut from tailor but provides a transition process and proper sunsetting of if.
Describe alternatives you've considered
N/A
Additional context
When looking at the different user types of ODS, we will benefit from Helm charts, as it:
pushes usage of IaC with already backed-in good practices and good defaults
helps on faster support from platforms team
empowers users to self-configure/fix by proper FAQs/HowTos and because of using a industry standard (Helm), that has great documentation.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Tailor is a self-developed component of OpenDevStack (ODS) whose active development has ceased and is logically superseded by Helm.
As a user I require having control of the k8s resources I need for my components/deployments (actively or passively).
As a support team member of ODS I can give better/faster support if resources are defined as code, in the same repository.
Describe the solution you'd like
We want to provide a base chart in the most generic ODS quickstarter component, in the
docker-plain
. This will be the baseline for the other ODS quickstarters and for existing components in existing running ODS installations.We want to provide such baseline with proper documentation of how to use common resources: Environment vars, config maps, secrets, storage, replicas, resource requirements, metadata, network policies, cert-manager, ...
We want to transition from the deprecated DeploymentConfig resource type to Deployment.
We want to provide a change that is not a hard-cut from tailor but provides a transition process and proper sunsetting of if.
Describe alternatives you've considered
N/A
Additional context
When looking at the different user types of ODS, we will benefit from Helm charts, as it:
The text was updated successfully, but these errors were encountered: