-
Notifications
You must be signed in to change notification settings - Fork 32
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
[K8s] Catalogue Helm chart rework to use single deployment for all verticles #727
base: master
Are you sure you want to change the base?
Conversation
sivanaikk
commented
Aug 29, 2024
- Modified values.yaml to remove all the verticles except apiServer
- Modified aws and azure resource-values files to have only resources and limits of single verticle
Can one of the admins verify this patch? |
Update app and chart versions in Chart.yaml |
@@ -20,208 +20,3 @@ apiServer: | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Increase the resources since all verticles will run in single pod now.
@@ -20,209 +20,3 @@ apiServer: | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Increase the resources since all verticles will run in single pod now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change deployment name, container name and labels to catalogue-server, to avoid confusion. Also update selectors in service and target ref in HPA.