Skip to content
Snippets Groups Projects
Marc Burnie [AWS]'s avatar
Marc Burnie [AWS] authored
Adding support for EKS 1.23

See merge request !342

(cherry picked from commit af389b85)

0d1e304d upgrade dependencies
d75a3313 Merge branch 'master' into master-dev-merge-bios
2ed13075 Merge branch 'master' into master-dev-merge-bios
a1c4bdfc Merge remote-tracking branch 'origin/master' into master-dev-merge
3f1ce709 Merge remote-tracking branch 'origin/master' into master-dev-merge
53e78452 Fix Spring vulnerabilities
af1ef586 Merge remote-tracking branch 'origin/master' into master-dev-merge
2d1118dc Fix Spring vulnerabilities
f906fbca Update core common lib version and fix vulnerable libs
401f4816 Merge remote-tracking branch 'origin/master' into master-dev-merge
c760a4fa Update versions of vulnerable libs
03800aeb Set pathmatch strategy to ant-path-matcher
ce91a89b Migration from Springfox to springdoc-openapi
5015de1f Merge remote-tracking branch 'origin/master' into master-dev-merge
c2adc600 Merge remote-tracking branch 'origin/master' into master-dev-merge
f1a80d83 Merge remote-tracking branch 'origin/master' into master-dev-merge
a7338ad1 adding support for EKS 1.23
a98c7c76 Update NOTICE
c72ce8be
History
Code owners
Assign users and groups as approvers for specific file changes. Learn more.

Helm Chart

Introduction

The following document outlines how to deploy and update the service application onto an existing Kubernetes deployment using the Helm package manager.

Prerequisites

The below software must be installed before continuing:

Additionally, an OSDU on AWS environment must be deployed.

Installation/Updating

To install or update the service application by executing the following command in the CHART folder:

helm upgrade [RELEASE_NAME] . -i -n [NAMESPACE]

To observe the Kubernetes resources before deploying them using the command:

helm upgrade [RELEASE_NAME] . -i -n [NAMESPACE] --dry-run --debug

To observe the history of the current release, use the following command:

helm history [RELEASE_NAME] -n [NAMESPACE]

To revert to a previous release, use the following command:

helm rollback [RELEASE] [REVISION] -n [NAMESPACE]

Customizing the Deployment

It is possible to modify the default values specified in the values.yaml file using the --set option. The below parameters can be modified by advanced users to customize the deployment configuration:

Name Example Value Description Type Required
global.accountID 000123456789 The AWS account ID. int yes
global.region us-east-1 The AWS region containing the OSDU deployment. str yes
global.resourcePrefix osdu The resource prefix of the OSDU deployment. str yes
global.allowOrigins {http://localhost,https://www.osdu.aws} A list of domains that are permitted by CORS policy. An empty list permits all origins. array[str] no
podAnnotations podAnnotations.version=v1.0.0 Additional annotations on the service pod dict no
imagePullPolicy IfNotPresent The service image pull policy str no
replicaCount 1 The number of pod replicas to be deployed int no
autoscaling.minReplicas 1 Minimum number of pod replicas int no
autoscaling.maxReplicas 100 Maximum number of pod replicas int no
autoscaling.targetCPUUtilizationPercentage 80 CPU utilization target int no

Uninstalling the Chart

To uninstall the helm release:

helm uninstall [RELEASE] -n [NAMESPACE] --keep-history