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.

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

Rename Helm HPA option + fixes to Helm READMEs #523

Merged
merged 2 commits into from
Nov 6, 2024

Conversation

eero-t
Copy link
Contributor

@eero-t eero-t commented Nov 4, 2024

Description

Rename horizontalPodAutoscaler option as autoscaling, to align it with the name used in Nvidia Helm charts:
https://github.com/NVIDIA/nim-deploy/blob/main/helm/nim-llm/README.md#autoscaling-parameters

And fix how bool options are shown in Helm READMEs.

Issues

n/a.

Type of change

Fixes README typos, changes (very rarely used) Helm option name:

  • Bug fix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would break existing design and interface)

Dependencies

n/a.

Tests

Change is automated (+ some README editing to align table columns):
git grep -l horizontalPodAutoscaler | xargs sed -i s/horizontalPodAutoscaler/autoscaling/g

And from the diff it's clearly doing the right thing so there should be no need for testing. If things worked earlier, they still work.

@eero-t eero-t changed the title rename Helm HPA option + fixes to Helm READMEs Rename Helm HPA option + fixes to Helm READMEs Nov 4, 2024
@eero-t eero-t mentioned this pull request Nov 5, 2024
3 tasks
@@ -15,7 +15,7 @@

## Introduction

`horizontalPodAutoscaler` option enables HPA scaling for relevant service components:
`autoscaling` option enables HPA scaling for relevant service components:
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/
Copy link
Collaborator

Choose a reason for hiding this comment

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

I would like to use just hpa instead of autoscaling, and then open that as Horizontal Pod Autoscaling in the text. autoscaling is to generic and can mean horizontal or vertical pod, or cluster (node) autoscaling.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Is cluster node autoscaling something that Helm charts would control (install rules for), and something that could be added to OPEA Helm charts later on? And if yes, why that would not be also be under autoscaling option:

  • autoscaling.scaleNodes: true
  • autoscaling.maxNodes: 99
    ?

Copy link
Collaborator

Choose a reason for hiding this comment

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

autoscaling.hpa is good. We can extend the autoscaling in the future then, if needed.

Copy link
Contributor Author

@eero-t eero-t Nov 6, 2024

Choose a reason for hiding this comment

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

Also, these are OPEA application Helm charts, so I think it's quite clear that it's the application (deployments) that are being scaled, instead of (potentially unrelated) nodes...

Copy link
Collaborator

Choose a reason for hiding this comment

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

yes, that is the case. My point is that autoscaling is too generic. If this is about HPA autoscaling, lets have the hpa in the name. So, hpa or autoscaling.hpa are both fine.

Copy link
Contributor Author

@eero-t eero-t Nov 6, 2024

Choose a reason for hiding this comment

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

autoscaling.hpa is good. We can extend the autoscaling in the future then, if needed.

As cluster scaling is not really an application install setting, there should be no confusion with that.

Are there also other relevant ways of (auto) scaling k8s applications than HPA?

(.enabled -> .hpa change is OK to me, but I'm not yet seeing compelling reason for it i.e. to differ from NIM Helm charts.)

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yeah, the NIM point is valid. Let's keep it similar.

@poussa poussa removed the request for review from yongfengdu November 6, 2024 14:39
@poussa poussa merged commit e80f581 into opea-project:main Nov 6, 2024
18 checks passed
@eero-t eero-t deleted the autoscaling branch November 14, 2024 13:12
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