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

add comment about keda documentation #358

Merged
merged 5 commits into from
Jun 17, 2024
Merged

add comment about keda documentation #358

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
53e3cc3
add comment about keda documentation
Richard87 Jun 17, 2024
bdcc9cf
remove keda radixconfig validation
Richard87 Jun 17, 2024
4dae86c
type
Richard87 Jun 17, 2024
f868724
move release news
Richard87 Jun 17, 2024
b372126
type
Richard87 Jun 17, 2024
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
7 changes: 4 additions & 3 deletions public-site/docs/radix-config/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -425,9 +425,10 @@ If overriding `portName` it will have to match one of the defined ports in the c

Scale your components replicas up and down based on resources or external metrics like CRON or Azure Service Bus.

More triggers are available at https://keda.sh/docs/latest/scalers/, and open a feature request on https://github.com/equinor/radix
If you need any other trigger types, find the list of available triggers at https://keda.sh/docs/latest/scalers/ and open a feature request on https://github.com/equinor/radix

You can override horizontalScaling in your environments and we will merge `minReplicas`, `maxReplicas`, `pollingInterval` and `CooldownPeriod`, if more any triggers is defined in the environment, the will override all triggers defined on the component level.
You can override horizontalScaling in your environments and we will merge `minReplicas`, `maxReplicas`, `pollingInterval` and `cooldownPeriod`. If any triggers are defined in the environment, they will replace all triggers on the component level.
Read more about polling intervall and cooldown period in KEDAs documentation [here](https://keda.sh/docs/latest/concepts/scaling-deployments/#pollinginterval)

```yaml
spec:
Expand All @@ -437,7 +438,7 @@ spec:
minReplicas: 0 # defaults to 1 if not set
maxReplicas: 6
# pollingInterval: 30 # Default
# CooldownPeriod: 300 # Default
# cooldownPeriod: 300 # Default
triggers:
# Cpu/Memory triggers will scale up/down so the average usage
# is 85% of requested Cpu across all pods,
Expand Down
Loading