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

Be more flexible for instance type #310

@MattiasGees

Description

@MattiasGees

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:

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions