Skip to content

fix(docs): Add required TLS and fix stale fields in S3 examples - #919

Open
sweb wants to merge 2 commits into
mainfrom
fix/tls-s3-examples
Open

fix(docs): Add required TLS and fix stale fields in S3 examples#919
sweb wants to merge 2 commits into
mainfrom
fix/tls-s3-examples

Conversation

@sweb

@sweb sweb commented Jul 28, 2026

Copy link
Copy Markdown
Member

Description

Fixes s3 connection examples to use TLS

Definition of Done Checklist

  • Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
  • Please make sure all these things are done and tick the boxes

Author

  • Links to generated (nightly) docs added

Reviewer

  • Documentation added or updated. Follows the style guide.

Acceptance

  • Links to generated (nightly) docs added

@sweb
sweb force-pushed the fix/tls-s3-examples branch from 9f9f00e to 53650ff Compare July 28, 2026 13:57
@sweb
sweb marked this pull request as ready for review July 28, 2026 13:58
@sweb sweb moved this to Development: Waiting for Review in Stackable Engineering Jul 28, 2026
Comment on lines +10 to +14
No configuration change is applied until the connection is fixed, including changes unrelated to S3.
The Stacklet keeps running with its previous configuration and still reports the `Available` condition as `True`, and no Kubernetes event is emitted.
Check the logs of the Trino operator if a catalog or a configuration change appears to have no effect.
Adding the missing `tls` section is enough to recover; the pending changes are applied within seconds.
This applies to both of the forms shown below.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

To be honest this sounds a bit verbose to me as it's not S3 specific at all, but a general platform thing. I would be in favor of removing it or placing it somewhere more "central" in the docs

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

You are right - addressed in e59e1c3

I missed that there is an event on the TrinoCluster - without noticing this, the failing reconciliation felt way more concerning than it actually is.

@sbernauer sbernauer moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering Jul 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development: In Review

Development

Successfully merging this pull request may close these issues.

2 participants