Skip to content

[HWORKS-2971] Document Trino authentication in disaster-recovery backup/restore#620

Merged
jimdowling merged 2 commits into
logicalclocks:mainfrom
jimdowling:HWORKS-2971
Jul 23, 2026
Merged

[HWORKS-2971] Document Trino authentication in disaster-recovery backup/restore#620
jimdowling merged 2 commits into
logicalclocks:mainfrom
jimdowling:HWORKS-2971

Conversation

@jimdowling

Copy link
Copy Markdown
Contributor

JIRA: https://hopsworks.atlassian.net/browse/HWORKS-2971
Paired PRs: logicalclocks/hopsworks-ee#3177, logicalclocks/hopsworks-helm#2147

Summary

  • Documents Trino authentication in the DR backup section: the password/group files and the admin/monitoring credential Secrets are labelled and captured by the k8s-backups-main Velero schedule (included in the Kubernetes-objects backup).
  • Explains that after a restore Hopsworks rebuilds the Trino password and group files from the restored RonDB state (automatic, no operator step), and that the internal shared secret is deliberately not backed up (with the createSharedSecret: false DR note).
  • Adds operator warnings: the backup holds usable admin credentials (protect/encrypt the backup store), and ArgoCD self-healing installs must set ignoreDifferences + RespectIgnoreDifferences on the Trino auth Secrets.

Test plan

  • markdownlint-cli2 passes on the changed page.
  • Renders under Setup & Installation → Admin → HA/DR → Disaster Recovery → Backup.

… backups

https://hopsworks.atlassian.net/browse/HWORKS-2971

Document Trino authentication in the disaster-recovery backup section: the
password and group files and the admin and monitoring credentials are labelled
and captured by the k8s-backups-main Velero schedule, Hopsworks rebuilds the
password and group files from restored RonDB state after a restore, and the
internal shared secret is deliberately not backed up. Add the operator notes on
protecting the backup store (it holds usable admin credentials) and the ArgoCD
ignoreDifferences requirement for self-healing installs.

Signed-off-by: Jim Dowling <jim@logicalclocks.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jimdowling
jimdowling requested a review from Copilot July 22, 2026 18:56
@jimdowling
jimdowling marked this pull request as ready for review July 22, 2026 18:57

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Disaster Recovery documentation to explicitly cover how Trino authentication data is handled during Velero-backed backup/restore, including post-restore behavior and operator guidance for secure handling and ArgoCD-managed clusters.

Changes:

  • Expands the “Kubernetes objects” backup scope description to include Trino authentication artifacts.
  • Adds a new “Trino authentication” section describing what is backed up, what is rebuilt after restore, and what is intentionally not backed up.
  • Adds operator-facing warning/note callouts for credential exposure in backups and ArgoCD self-healing considerations.

@jimdowling
jimdowling requested a review from o-alex July 22, 2026 19:14

@o-alex o-alex left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From the HWORKS-2971 ticket review.

Comment thread docs/setup_installation/admin/ha-dr/dr.md
… backups

https://hopsworks.atlassian.net/browse/HWORKS-2971

Add an operator note to the Trino authentication DR section: the automatic
recovery holds only for backups taken after this feature was deployed. A
pre-upgrade backup does not contain the Trino Secrets (they were not yet
labelled for the k8s-backups-main schedule), and an existing cluster first
has such a backup only after its next backup cycle. Restoring an older backup
still recovers all RonDB-derived authentication via the reconciliation, but
not the admin/monitoring credential entries, which are re-rendered from chart
values on a fresh install, so out-of-band rotations are lost and Prometheus
may need its Trino monitoring credentials re-aligned.

Signed-off-by: Jim Dowling <jim@logicalclocks.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jimdowling
jimdowling merged commit 2b08a9f into logicalclocks:main Jul 23, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants