Skip to content

Addworkloadrule#20

Open
Rupam-It wants to merge 14 commits into
mainfrom
addworkloadrule
Open

Addworkloadrule#20
Rupam-It wants to merge 14 commits into
mainfrom
addworkloadrule

Conversation

@Rupam-It
Copy link
Copy Markdown

add workloadrule for terraform devzero provider

## Example Usage

```terraform
# Minimal — auto-generate all fields
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe adding some comments for whole workload rule. I think best is. to hceck this with our firends @f-leu and @Parthiba-Hazra they did a lot of wrok here, also here we support hpa but I do not see that config here.

Comment thread docs/resources/workload_rule.md Outdated

action_triggers = ["on_schedule"]
cron_schedule = "0 2 * * *"
cooldown_minutes = 60
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove cooldown_minutes

Comment thread docs/resources/workload_rule.md Outdated
oom_enabled = true
oom_memory_multiplier = 2.0
oom_max_reactions = 3
oom_cooldown_seconds = 60
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove oom_cooldown_seconds

Comment thread docs/resources/workload_rule.md Outdated
- `action_triggers` (List of String) When to apply recommendations. Valid values: 'on_detection', 'on_schedule'
- `auto_generate` (Boolean) When true the engine generates all rule fields automatically; manual field overrides are ignored
- `containers` (Attributes List) Per-container resource rule configurations. When empty, workload-level rules apply to all containers. (see [below for nested schema](#nestedatt--containers))
- `cooldown_minutes` (Number) Minimum minutes between consecutive recommendation applications
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove all mentions of cooldowns - engine takes care of that

Comment thread docs/resources/workload_rule.md Outdated
- `live_migration_enabled` (Boolean) Allow live pod migration when applying recommendations
- `memory_rule` (Attributes) Memory vertical scaling rule configuration (see [below for nested schema](#nestedatt--memory_rule))
- `scheduler_plugins` (List of String) Kubernetes scheduler plugins to activate
- `startup_period_seconds` (Number) Seconds after workload start to exclude from usage data
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove startup_period_seconds and anything time related

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants