tarmak icon indicating copy to clipboard operation
tarmak copied to clipboard

Default instances sizes can be too small

Open MattiasGees opened this issue 6 years ago • 0 comments

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened: Ran out of CPU credits for vault and etcd. This caused problems with running a production setup.

What you expected to happen: Running with default instances should be enough to bring up a production workloads

How to reproduce it (as minimally and precisely as possible):

  1. tarmak init
  2. tarmak apply

Anything else we need to know?: Maybe we can tweak the defaults a bit more, but we should also document this a bit better (eg best practices for production)

Environment:

  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration**:
  • Install tools:
  • Others:

MattiasGees avatar Jan 21 '19 13:01 MattiasGees