Helm chart, GitHub deploy workflow, and Kubernetes/Compose parity#2
Open
aprilrieger wants to merge 33 commits intomainfrom
Open
Helm chart, GitHub deploy workflow, and Kubernetes/Compose parity#2aprilrieger wants to merge 33 commits intomainfrom
aprilrieger wants to merge 33 commits intomainfrom
Conversation
- Port chart from internal reference; rename templates to dataverseup - Chart version 0.1.0; scrub internal ops path references from values/messages - Fix helm test hook to wget /api/info/version over HTTP - docs/HELM.md install order, docs/DEPLOYMENT.md ticket context - values-examples/internal-solr-starter.yaml skeleton - README: Helm quick start and layout Made-with: Cursor
Made-with: Cursor
- Single source of truth under init.d/; Helm follows symlinks and helm package inlines file contents for portable tarballs - Align 010-mailrelay-set.sh header comments for Compose + Helm - Document in charts/dataverseup/README.md and docs/HELM.md Made-with: Cursor
… path) Made-with: Cursor
…t deploy for fine-tuning later
…ues files instaed for user config
…RIPT_REVISION to see if it sets the correct one
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Repository: github.com/notch8/dataverseup · Live demo (active): demo-dataverseup.notch8.cloud
Delivers Kubernetes support for DataverseUp while keeping Compose as the lab default: a Helm chart, deploy automation, one deployment runbook, a cleaner
scripts/layout, and working SMTP wiring for the demo environment (SendGrid + Dataverse 6.2+ MicroProfile mail settings).What’s included
Helm (
charts/dataverseup)solrInitinitContainer (standalone default; SolrCloud path documented).bootstrapJob.mode: composemirrors local flow (wait → configbaker →apply-branding.sh→seed-content.shvia ConfigMap-backed fixtures).awsS3.*) and mail relay script via ConfigMap;initdFromChartcan ship the full Payarascripts/init.d/*.shbundle.files/uses symlinks into the repo (especiallyfiles/init.d/→scripts/init.d/) sohelm packageinlines real content without duplicating scripts.SMTP / email (demo deploy + docs)
dataverse.mail.*, exposed as pod envDATAVERSE_MAIL_*(installation guide — SMTP/Email).ops/demo-deploy.tmpl.yamlsetsDATAVERSE_MAIL_SYSTEM_EMAIL,DATAVERSE_MAIL_SUPPORT_EMAIL(support@notch8.com),DATAVERSE_MAIL_MTA_*for SendGrid (host, 587, STARTTLS, userapikey, password from secret), andDATAVERSE_MAIL_DEBUG(falseby default; flip totruefor troubleshooting).010-mailrelay-set.sh(Payara JavaMail +:SystemEmail) remains for legacy/parity but is not sufficient alone for outbound mail on current Dataverse; theDATAVERSE_MAIL_*block is required for verification/password email.envsubstinjects onlyDB_PASSWORD,SMTP_PASSWORD, andGITHUB_RUN_IDinto the demo template; SMTP host/ports/addresses are literals in the template. Removed unusedMAIL_SMTP_PASSWORDand redundantSMTP_*workflow env vars that did not feedenvsubst.docs/DEPLOYMENT.md: SMTP checklist, SendGrid + SendGrid Activity,DATAVERSE_MAIL_DEBUG, Payara log path/opt/payara/appserver/glassfish/domains/domain1/logs, pod restart after mail secret changes (MTA session cached)..env.example: commented Compose SMTP variables for local testing.Operations & CI
bin/helm_deploy: opinionatedhelm upgrade --installwrapper (--atomic, default timeout,HELM_EXTRA_ARGS)..github/workflows/deploy.yaml: environment-driven deploy (kubeconfig, rendered values, rollout + optional bootstrap job wait).ops/demo-deploy.tmpl.yaml: example values pattern for a named environment (literals for URLs/hosts/mail;envsubstfor DB + SendGrid API key + rollout nonce).Documentation
docs/DEPLOYMENT.md: single runbook — Helm, SMTP/Dataverse mail, S3, Ingress, GitHub Actions secrets, upgrades, learnings.README.md: Helm + deployment pointer; repo + demo links;scripts/layout.Repo layout (scripts)
init.d/→scripts/init.d/(Compose still mounts to/opt/payara/init.d).triggers/→scripts/triggers/(Compose:/triggers,/opt/payara/triggers).config/update-fields.sh→scripts/solr/update-fields.sh(config/keeps Solr XML only).Behavior & quality
scripts/init.d/006-s3-aws-storage.sh: DRY/KISS; Amazon S3: leaveendpointUrlempty when using real AWS.How to test
helm lint charts/dataverseupandhelm templatewith your values (e.g. demo template).SMTP_PASSWORD(SendGrid API key); deploy and roll Dataverse pods; trigger signup/verify or password reset; confirm in SendGrid Activity. Optionally setDATAVERSE_MAIL_DEBUG=truein the template briefly and inspectkubectl logs/server.log.docker composeafter pull;.env.exampleSMTP block for010-mailrelayparity.Risks / follow-ups
scripts/init.dscripts assume Compose-only resources (MinIO,scripts/triggers). Review beforeinitdFromCharteverywhere.DATAVERSE_MAIL_MTA_PASSWORDchanges require Payara restart (cached session).scripts/init.d/vendor-solr/update-fields.shvsscripts/solr/update-fields.sh— see README for IQSS refresh.Stats
~87+ files touched; net addition mostly chart templates, deployment doc, ops template, and SMTP env wiring.