Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

Default instances sizes can be too small #692

Open
MattiasGees opened this issue Jan 21, 2019 · 0 comments
Open

Default instances sizes can be too small #692

MattiasGees opened this issue Jan 21, 2019 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@MattiasGees
Copy link
Member

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:
@jetstack-bot jetstack-bot added the kind/bug Categorizes issue or PR as related to a bug. label Jan 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants