Skip to content
This repository was archived by the owner on Nov 18, 2019. It is now read-only.

Support for better default plans in KubeDB #48

Open
bikramnehra opened this issue Mar 9, 2019 · 2 comments
Open

Support for better default plans in KubeDB #48

bikramnehra opened this issue Mar 9, 2019 · 2 comments
Assignees

Comments

@bikramnehra
Copy link

Issue

Currently, there are too many options users have to provide in order to do db service instance provisioning eg:

{
  "metadata": {
    "labels": {
      "app": "my-mysql"
    }
  },
  "spec": {
    "storage": {
      "accessModes": [
        "ReadWriteOnce"
      ],
      "resources": {
        "requests": {
          "storage": "1Gi"
        }
      },
      "storageClassName": "gp2"
    },
    "storageType": "Durable",
    "terminationPolicy": "WipeOut",
    "version": "8.0-v1"
  }
}

Solution

The idea is to have a set of default plans beyond the regular and demo plans being offered currently to minimize end user overhead.

More input from @troytop on this: https://appscode.slack.com/archives/CGDV0U52R/p1552083691041600

@tamalsaha
Copy link
Member

Bikram, I have not had a chance to work on the default plans issue. We are preparing next release of KubeDB which will have support for MongoDB sharding and mysql clustering. We are going to introduce the default plans after that unless there is a reason to rush it.

We are trying to get the next release of KubeDB out by end of the month if not sooner.

@bikramnehra
Copy link
Author

@tamalsaha Thanks for the update. I guess it should be okay. Just wanted to make sure this is on the agenda.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants