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

Update empty resources in Katib config #2799

Merged
merged 1 commit into from
Jun 30, 2021
Merged

Update empty resources in Katib config #2799

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
32 changes: 20 additions & 12 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 @@ -96,18 +96,22 @@ a default value is set automatically.
- `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:
the `cpu`, `memory`, or `ephemeral-storage` resource from the Kubernetes cluster.
For instance, you have to remove `ephemeral-storage` from the container resources to use the
[Google Kubernetes Engine cluster autoscaler](https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-autoscaler#limitations).

To remove specific resources from the metrics collector's container set the
negative values in requests and limits in your Katib config as follows:

```json
"requests": {
"cpu": "-1",
"memory": "-1",
"ephemeral-storage": "-1"
},
"limits": {
"cpu": "-1",
"memory": "-1",
"ephemeral-storage": "-1"
}
```
Expand Down Expand Up @@ -239,18 +243,22 @@ any other settings, a default value is set automatically.
- `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:
the `cpu`, `memory`, or `ephemeral-storage` resource from the Kubernetes cluster.
For instance, you have to remove `ephemeral-storage` from the container resources to use the
[Google Kubernetes Engine cluster autoscaler](https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-autoscaler#limitations).

To remove specific resources from the suggestion's container set the
negative values in requests and limits in your Katib config as follows:

```json
"requests": {
"cpu": "-1",
"memory": "-1",
"ephemeral-storage": "-1"
},
"limits": {
"cpu": "-1",
"memory": "-1",
"ephemeral-storage": "-1"
}
```
Expand Down