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

Make default configuration installable on most platforms #1111

Closed
tennix opened this issue Nov 7, 2019 · 5 comments · Fixed by #1854
Closed

Make default configuration installable on most platforms #1111

tennix opened this issue Nov 7, 2019 · 5 comments · Fixed by #1854
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@tennix
Copy link
Member

tennix commented Nov 7, 2019

Feature Request

Currently, the default tidb cluster configuration is for "half-production". This makes it difficult to deploy for the first time, but also not production-ready configuration. Users have to tune the parameters in the default values.yaml to make it production-ready.

To overcome this dilemma, we should make the default installation available for most platforms including minikube and kind. So users can have a real quick-start experience using tidb-operator. As for production deployment, we can provide a detailed guide about the best practice and how to adjust parameters to make TiDB cluster both secure, stable and performant.

@tennix
Copy link
Member Author

tennix commented Nov 12, 2019

Managed platforms like GKE, EKS, minikube, kind all enables DefaultStorageClass admission controller to set a default storage class when a PVC does not specify a storage class.
ref: https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#defaultstorageclass

@aylei
Copy link
Contributor

aylei commented Nov 15, 2019

ref: #700

@aylei
Copy link
Contributor

aylei commented Dec 25, 2019

This should be included in 1.1

@aylei aylei added this to the v1.1.0 milestone Dec 25, 2019
@cofyc
Copy link
Contributor

cofyc commented Jan 20, 2020

this will be addressed by #1111 and #1449.
and we should have an e2e job to verify it in one node cluster started by minkube or kind

@cofyc cofyc self-assigned this Feb 25, 2020
@cofyc
Copy link
Contributor

cofyc commented Feb 25, 2020

I'm going to add some basic e2e tests in Github Actions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants