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

Be more flexible for instance type #310

Open
MattiasGees opened this issue Jun 18, 2018 · 1 comment · May be fixed by #314
Open

Be more flexible for instance type #310

MattiasGees opened this issue Jun 18, 2018 · 1 comment · May be fixed by #314
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@MattiasGees
Copy link
Member

MattiasGees commented Jun 18, 2018

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
At this moment in tarmak.yaml, we can only provide small, medium, large, ...

What you expected to happen:
I would expect we can specify a specific AWS instance like c5.large. This makes tarmak more tweakable for end-user.

For master I would do a check that we don't launch instances that are too small to run everything (eg t2.nano, t2.micro, ...). A sensible default should also be set.

Especially for masters we should make this tweakable. People have totally different workloads (eg memory, cpu, gpu, ...)

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

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration**:
  • Install tools:
  • Others:
@jetstack-bot jetstack-bot added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 18, 2018
@MattiasGees MattiasGees changed the title Change instance type Be more flexible for instance type Jun 18, 2018
@JoshVanL
Copy link
Contributor

/assign

@JoshVanL JoshVanL linked a pull request Jun 18, 2018 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants