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

[K8s] Resource Server Helm chart rework to use single deployment for all verticles #729

Open
wants to merge 9 commits into
base: master
Choose a base branch
from
6 changes: 3 additions & 3 deletions K8s-deployment/Charts/resource-server/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
apiVersion: v2
name: resourceServer
name: resource-server
description: A Helm chart for Resource Server

# A chart can be either an 'application' or a 'library' chart.
Expand All @@ -15,9 +15,9 @@ type: application
# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
# Versions are expected to follow Semantic Versioning (https://semver.org/)
version: 0.1.32
version: 1.0.0
# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application. Versions are not expected to
# follow Semantic Versioning. They should reflect the version the application is using.
# It is recommended to use it with quotes.
appVersion: "5.0.0-alpha"
appVersion: "5.5.0-ef36360"
621 changes: 85 additions & 536 deletions K8s-deployment/Charts/resource-server/README.md

Large diffs are not rendered by default.

166 changes: 7 additions & 159 deletions K8s-deployment/Charts/resource-server/example-aws-resource-values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -9,171 +9,17 @@ ingress:
## @param apiServer.resources.limits The resources limits for the apiServer containers
## @param apiServer.resources.requests The requested resources for the apiServer containers
##
apiServer:
resourceServer:
enabled: true
nodeSelector:
node.kubernetes.io/instance-type: t3a.medium
resources:
limits:
cpu: 1000m
memory: 1200Mi
requests:
cpu: 700m
memory: 1200Mi

## archivesDatabase resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
## @param archivesDatabase.resources.limits The resources limits for the archivesDatabase containers
## @param archivesDatabase.resources.requests The requested resources for the archivesDatabase containers
##
archivesDatabase:
enabled: true
nodeSelector:
node.kubernetes.io/instance-type: t3a.medium
resources:
limits:
cpu: 1000m
memory: 1.5Gi
requests:
cpu: 700m
memory: 1.5Gi

## authenticator resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
## @param authenticator.resources.limits The resources limits for the authenticator containers
## @param authenticator.resources.requests The requested resources for the authenticator containers
##
authenticator:
enabled: true
nodeSelector:
node.kubernetes.io/instance-type: t3a.medium
resources:
limits:
cpu: 600m
memory: 750Mi
requests:
cpu: 500m
memory: 500Mi

## databroker resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
## @param databroker.resources.limits The resources limits for the databroker containers
## @param databroker.resources.requests The requested resources for the databroker containers
##
databroker:
enabled: true
nodeSelector:
node.kubernetes.io/instance-type: t3a.medium
resources:
limits:
cpu: 500m
memory: 512Mi
requests:
cpu: 400m
memory: 400Mi

## encryption resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
## @param encryption.resources.limits The resources limits for the encryption containers
## @param encryption.resources.requests The requested resources for the encryption containers
##
encryption:
enabled: true
nodeSelector:
node.kubernetes.io/instance-type: t3a.medium
resources:
limits:
cpu: 600m
memory: 900Mi
requests:
cpu: 500m
memory: 700Mi

## latestDatabase resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
## @param latestDatabase.resources.limits The resources limits for the latestDatabase containers
## @param latestDatabase.resources.requests The requested resources for the latestDatabase containers
##
latestDatabase:
enabled: true
nodeSelector:
node.kubernetes.io/instance-type: t3a.medium
resources:
limits:
cpu: 1000m
memory: 1Gi
requests:
cpu: 800m
memory: 800Mi

## metering resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
## @param metering.resources.limits The resources limits for the metering containers
## @param metering.resources.requests The requested resources for the metering containers
##
metering:
enabled: true
nodeSelector:
node.kubernetes.io/instance-type: t3a.medium
resources:
limits:
cpu: 700m
memory: 1Gi
requests:
cpu: 500m
memory: 800Mi

## postgres resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
## @param postgres.resources.limits The resources limits for the postgres containers
## @param postgres.resources.requests The requested resources for the postgres containers
##
postgres:
enabled: true
nodeSelector:
node.kubernetes.io/instance-type: t3a.medium
resources:
limits:
cpu: 600m
memory: 600Mi
requests:
cpu: 400m
memory: 400Mi

## cache resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
## @param cache.resources.limits The resources limits for the cache containers
## @param cache.resources.requests The requested resources for the cache containers
##
cache:
enabled: true
nodeSelector:
node.kubernetes.io/instance-type: t3a.medium
resources:
limits:
cpu: 400m
memory: 750Mi
cpu: 2000m
memory: 3000Mi
requests:
Copy link
Collaborator

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.

cpu: 200m
memory: 600Mi

## async resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
## @param async.resources.limits The resources limits for the async containers
## @param async.resources.requests The requested resources for the async containers
##
async:
enabled: true
nodeSelector:
node.kubernetes.io/instance-type: t3a.medium
resources:
limits:
cpu: 1000m
memory: 1Gi
requests:
cpu: 800m
memory: 800Mi

memory: 512Mi
extraVolumes:
- name: rs-config
secret:
Expand All @@ -196,4 +42,6 @@ async:
storageClassName: efs-csi-storage-class
resources:
requests:
storage: 50Gi
storage: 5Gi


Loading