Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Disable ephemeral storage in Katib Config #2315

Merged
merged 5 commits into from
Nov 13, 2020
Merged

Disable ephemeral storage in Katib Config #2315

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
e8d28dc
Add info about negative values for ephemeral storage
andreyvelich Oct 27, 2020
dbb70a5
Move to one line
andreyvelich Nov 5, 2020
5f39e10
Remove old config
andreyvelich Nov 11, 2020
4c7c55a
Add info
andreyvelich Nov 11, 2020
e63e496
Address comments
andreyvelich Nov 12, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions content/en/docs/components/katib/katib-config.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,23 @@ a default value is set automatically.
- `cpu = 500m`
- `ephemeral-storage = 5Gi`

You can run your metrics collector's container without requesting
the `ephemeral-storage` resource from the Kubernetes cluster.
For instance, when using the
[Google Kubernetes Engine cluster autoscaler](https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-autoscaler#limitations)
for your Katib experiments, you can remove the `ephemeral-storage` resource
from the metrics collector's container by setting the negative values for the
`ephemeral-storage` requests and limits in your Katib config as follows:

```json
"requests": {
"ephemeral-storage": "-1"
},
"limits": {
"ephemeral-storage": "-1"
}
```

## Suggestion settings

These settings are related to Katib suggestions, where:
Expand Down Expand Up @@ -205,6 +222,23 @@ a default value is set automatically.
- `cpu = 500m`
- `ephemeral-storage = 5Gi`

You can run your suggestion's container without requesting
the `ephemeral-storage` resource from the Kubernetes cluster.
For instance, when using the
[Google Kubernetes Engine cluster autoscaler](https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-autoscaler#limitations)
for your Katib experiments, you can remove the `ephemeral-storage` resource
from the suggestion's container by setting the negative values for the
`ephemeral-storage` requests and limits in your Katib config as follows:

```json
"requests": {
"ephemeral-storage": "-1"
},
"limits": {
"ephemeral-storage": "-1"
}
```

1. `serviceAccountName` - [service account](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/)
for the suggestion's container with a `random` algorithm.

Expand Down