GraphDB Helm 11.3.0

What's Changed

New

• Added new configuration properties for the license

  • Added license.mountPath to configure where the license volume is mounted
  • Added license.optional to configure the license volume as optional if needed
  • Added license.readOnly to configure the read/write mode of the license volume mount

• Updated to GraphDB 10.8.0

Updated

• Removed any pre-install, pre-upgrade, pre-rollback Helm hooks annotations to allow seamless ArgoCD deployments.
• Changed the license directory to /opt/graphdb/home/conf/license/ with license.mountPath in order to avoid using a subPath volume
  mount. This allows kubelet to update the license when the Secret has been updated.
• Changed the license volume mount as read-only by default with license.readOnly

Full Changelog: v11.2.2...v11.3.0

GraphDB Helm 11.2.2

What's Changed

• Updated to GraphDB 10.7.6

Full Changelog: v11.2.1...v11.2.2

GraphDB Helm 11.2.1

What's Changed

• Updated to GraphDB 10.7.5

Full Changelog: v11.2.0...v11.2.1

GraphDB Helm 11.2.0

What's Changed

New

• Added CronJob for scheduling GraphDB backups. The CronJob supports both local and cloud backups.
  • Added new configurations under backup: backup.enabled for toggling the backup CronJob, backup.type for selecting between local and cloud and more.
  • Local backups support saving the GraphDB backup archives in volume from an existing persistent volume claim, configured with backup.local
  • Cloud backups support uploading the GraphDB backup archives in one of the supported cloud object storage services, configured with backup.cloud
• Added a new property security.provisioner.passwordHash to define an initial password for the provisioner user as a bcrypt hash.
• Configured graphdb.extra.plugins to load plugins from /opt/graphdb/home/extra-plugins by default
• Added configuration examples under examples/
  • Added examples for deploying GraphDB in Azure
  • Added examples for deploying GraphDB in GKE
  • Added examples for configuring the new backup options
  • Added examples for GraphDB virtualization features
  • Added examples for providing extra GraphDB plugins

Fixed

• Updated the GraphDB containers to explicitly use /tmp as a working directory to avoid permission errors due to the default security context's readOnlyRootFilesystem when the container has a starting folder different from /tmp.

Full Changelog: v11.1.5...v11.2.0

GraphDB Helm 11.1.5

What's Changed

• Added GraphDB security configurations examples by @cloudvlad in #121
• Added GraphDB configuration examples by @cloudvlad in #122
• Updated GraphDB version to 10.7.4 by @Sukhumi in #131

Full Changelog: v11.1.4...v11.1.5

GraphDB Helm 11.1.4

What's Changed

• Fixed bug related to extraVolumeClaimTemplates rendering. by @Secchol in #120

New Contributors

• @Secchol made their first contribution in #120

Full Changelog: v11.1.3...v11.1.4

GraphDB Helm 11.1.3

New

• Updated to GraphDB 10.7.3

GraphDB Helm 11.1.2

New

• Updated to GraphDB 10.7.2

Improvements

• Added examples for deploying GraphDB in AWS

GraphDB Helm 11.1.1

New

• Updated to GraphDB 10.7.1

GraphDB Helm 11.1.0

New

• Updated to GraphDB 10.7.0
• Added podAntiAffinity and proxy.podAntiAffinity for configuring a default podAntiAffinity for the GraphDB pods and GraphDB proxy pods. The default values configure a "soft" podAntiAffinity that tries to schedule GraphDB pods across different Kubernetes hosts but does not enforce it.
• Added new configuration options for the Jobs
  • Added job.schedulerName for overriding the default Kubernetes scheduler
  • Added job.dnsConfig and job.dnsPolicy for customizing the DNS resolution
  • Added job.priorityClassName for defining the pods scheduling importance
  • Added job.nodeSelector, job.affinity, job.tolerations and job.topologySpreadConstraints for customizing the
    node scheduling
• Added persistence.volumeClaimRetentionPolicy and proxy.persistence.volumeClaimRetentionPolicy to control the retention policy of the PVCs when the StatefulSets are scaled and deleted. These configurations are used only for Kubernetes 1.27 and above.