Skip to content

Conversation

markpanganiban
Copy link
Contributor

Summary

The backend-api Service was included by default even though it’s only needed when a deployment intentionally exposes the backend to API/CLI users via a dedicated subdomain. Keeping it enabled by default caused confusion and could conflict with the frontend’s wildcard routing.

What changed

  • Removed the backend-api Service from the default deployment manifest.

Rationale

  • Avoids routing conflicts with the frontend’s wildcard setup.
  • Reduces unnecessary surface area (e.g., NodePort exposure) for deployments that don’t need external API access.
  • Aligns defaults with the principle of least privilege and least surprise.

Impact / Compatibility

  • No impact for typical deployments that don’t use the external API.
  • Deployments that relied on backend-api must re-enable it explicitly. TBD if we need to provide a separate guide for this.

Security

  • Removes cluster-wide exposure by default; safer out-of-the-box posture.

Copy link

netlify bot commented Sep 24, 2025

Deploy Preview for seqera-docs ready!

Name Link
🔨 Latest commit 55f7afc
🔍 Latest deploy log https://app.netlify.com/projects/seqera-docs/deploys/68ed1983773b810008932b7b
😎 Deploy Preview https://deploy-preview-843--seqera-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@markpanganiban markpanganiban requested review from gavinelder, justinegeffen and llewellyn-sl and removed request for gavinelder September 24, 2025 20:03
@gwright99
Copy link
Contributor

gwright99 commented Sep 29, 2025

Asked in ticket, but I'll ask here too: "What was the benefit of exposing this API endpoint publicly in the first place? (beyond just specific subdomain control)"

Copy link
Contributor

@gwright99 gwright99 left a comment

Choose a reason for hiding this comment

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

IMO there should be placeholder text explaining that we used to have a service there but it was removed (with a link to this issue), along with some guidance on why sites might wish to keep it around (if at all).

Let's do a favour to future us and any client doing an upgrade to help explain within the manifests why something is different rather than having to answer it one-off via support tickets.

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