FAQ

What does “the chart version is the product version” mean?

Under the hood, Marshal is made up of several components (API, gateway, web dashboard, marketplace service, and the images used inside each session), each with its own version number. On their own, those numbers don’t tell you what “Marshal 1.4.0” means.

The Helm chart solves this by acting as a Bill of Materials: its values.yaml pins the exact, tested image for every component that makes up a given release. So when you install chart version 1.4.0, you’re installing one specific, known-good combination of every component — not a set of independently-moving parts that happen to be running at the same time. One number tells you exactly what’s installed, which makes upgrades, rollbacks, and support conversations much simpler.

Can I run multiple instances (e.g. prod and staging) on one cluster?

Yes. Each instance is its own Helm release, installed into its own namespace — for example marshal-prod and marshal-staging on the same cluster. Each release gets its own session-pod namespace, its own configuration and secrets, and its own set of resources, so the two instances are fully isolated from each other. This is a common pattern for rehearsing an upgrade in staging before promoting the same chart version to production.

Is Marshal exposed to the internet?

No. Marshal is not exposed to the public internet by default. It’s designed to be reached over your own private network (VPN, bastion, or equivalent), and the only outbound access it needs is HTTPS to a small set of Marshal endpoints for image pulls and license verification. No inbound access into your environment is ever required.

How do I get support, renew my license, or contact Marshal?

Reach out to your Marshal contact — they’re your point of contact for support, license renewal, onboarding new credentials, and getting the latest chart version. Keep the onboarding details they gave you (deployment ID, license token, registry pull token) on hand, since most support requests start there.

Is Marshal air-gapped, or can it run fully offline?

Not yet. Today’s installation model assumes outbound HTTPS access to Marshal’s registry for image pulls and license verification (typically routed through a pull-through cache you run in your own environment). A fully air-gapped, offline-bundle installation path is on the roadmap but not available today — if that’s a hard requirement for your environment, talk to your Marshal contact about timing.