Galileo On-Prem Stack Setup
This skill is render-first and handoff-only. It never invokes a mutating Helm,
Kubernetes, MicroK8s, CRD, node-label, rollback, or uninstall command. The
historical --apply-* flags are permanent fail-closed sentinels.
When to Activate
Use this skill when a Galileo On-Prem Kubernetes deployment needs entitled
chart inspection, immutable render evidence, target-bound read-only preflight,
status observation, or a Galileo/CSE joint-session handoff. Do not activate it
to execute Helm, kubectl, MicroK8s, CRD, upgrade, rollback, or uninstall
mutations.
Prerequisites
| Requirement |
Why it is required |
Entitled local galileo-stack chart archive, exact version, and SHA-256 |
The chart is proprietary and release-specific; never infer its values |
| Version-matched CSE questionnaire and values contract |
Product topology and secret paths must come from Galileo, not invented defaults |
Runtime-only secret values file, mode 0600 or stricter |
Secret material is inspected in memory and never copied into the bundle |
| Named kube context, exact API/CA/cluster/namespace identity |
Connected evidence must bind one reviewed target |
Helm 3, kubectl, Python 3, and PyYAML |
Required for local render and read-only connected inspection |
| External Galileo/CSE change authorization |
This local skill does not authenticate or replace change approval |
Required Intake
Ask for the Galileo instance console URL and record it exactly, for example
https://console.demo-v2.galileocloud.io/. Pass it with
--galileo-console-url; never assume a Galileo Cloud hostname for on-prem.
Never ask for or repeat passwords in chat. Never put credentials, tokens,
private keys, Secret payloads, or credential-bearing URLs in the spec, command
line, bundle, plans, evidence, logs, or support output.
Supported Outcomes
- Safely inspect a pinned umbrella chart and every nested chart for exact
dependencies, values/schema flags, images, hooks/migrations, CRDs, API kinds,
cluster-scoped objects, routes, and persistence surfaces.
- Render a content-addressed private bundle containing only non-secret inputs,
the exact chart archive, normalized spec, and derived inventories.
- Run a connected, read-only preflight that binds the target, release state,
active CRDs, API discovery, runtime Secret influence, rendered manifests,
images, endpoints, storage, routing, monitoring, data services, node pools,
Wizard/GPU intent, and air-gap handoff evidence.
- Observe live status without claiming health or provenance that was not
proven.
production_ready always remains false in this release.
- Prepare canonical pre-approval handoff candidates for all lifecycle changes,
including official installation methods, upgrades, rollback, retirement,
galileoctl, dedicated CRDs, GPU/local inference, air-gap, and MicroK8s lab
bootstrap.
The current Installation Guide defines four methods: galileoctl (Method A),
umbrella Helm CLI (Method B), deployment script (Method C), and step-by-step
(Method D). The galileoctl UI is identified for first install and its CLI is a
workstation/CI alternative. This skill recognizes all four methods and can
inspect pinned Method A/B chart artifacts. Method C remains incomplete without
the exact script/config hashes and static review; Method D remains incomplete
without the ordered chart/release/dependency contract. It executes none of the
methods. Do not call the raw Helm path vendor-recommended.
Do not use this skill for Galileo projects, datasets, scorers, model-provider
configuration, Agent Control ownership, or standalone Luna Studio; route those
through their dedicated Galileo skills.
Workflow Overview
┌───────────────────────────────────────────┐
│ Pinned artifacts + closed review inputs │
└───────────────────────────────────────────┘
▼
inspect -> render -> validate
▼
read-only connected preflight
▼
unauthorized candidate -> external Galileo/CSE session
▼
read-only status observation
Required Workflow
- Read reference.md,
references/lifecycle-contract.md, and
references/coverage-and-safety.md.
- Run
--inspect-chart. It emits only a runtime inventory and
coverage-review.yaml; it does not create a deployable bundle.
- Copy every exact reviewed ID into
spec.coverage, then run --render.
- Run offline validation on the immutable bundle.
- Run
--preflight --for-action <action> against the exact target with the
runtime secret file. Preflight is read-only; server-side dry-run admission
checks are non-persisting and are reported separately from observer access.
- Give the bundle, canonical redacted evidence, unresolved gates, and exact
target/release inventory to the Galileo/CSE operator. The operator executes
the vendor-approved command in the jointly controlled session. The emitted
handoff-candidate.json is authorized:false; it is not a final approval.
- Run
--status for retryable read-only observation. Without independently
authenticated adoption/provenance evidence it reports an unverified state,
never successful production completion.
Commands
bash skills/galileo-on-prem-stack-setup/scripts/setup.sh --help
bash skills/galileo-on-prem-stack-setup/scripts/validate.sh --help
bash skills/galileo-on-prem-stack-setup/scripts/setup.sh \
--inspect-chart \
--spec ./galileo-stack-deployment.yaml \
--galileo-console-url "$GALILEO_CONSOLE_URL" \
--output-dir ./galileo-on-prem-rendered
bash skills/galileo-on-prem-stack-setup/scripts/setup.sh \
--render \
--spec ./galileo-stack-deployment.yaml \
--galileo-console-url "$GALILEO_CONSOLE_URL" \
--output-dir ./galileo-on-prem-rendered
bash skills/galileo-on-prem-stack-setup/scripts/validate.sh \
--bundle ./galileo-on-prem-rendered/acme/<bundle-sha>
bash skills/galileo-on-prem-stack-setup/scripts/setup.sh \
--preflight \
--for-action install \
--bundle ./galileo-on-prem-rendered/acme/<bundle-sha> \
--secret-values-file /secure/runtime/secret-values.yaml \
--galileo-console-url "$GALILEO_CONSOLE_URL"
bash skills/galileo-on-prem-stack-setup/scripts/setup.sh \
--status \
--bundle ./galileo-on-prem-rendered/acme/<bundle-sha> \
--galileo-console-url "$GALILEO_CONSOLE_URL" \
--json
--apply-install, --apply-upgrade, --apply-rollback,
--apply-uninstall, and --apply-lab-bootstrap reject before reading a bundle,
opening a kubeconfig, resolving a binary, writing state, or running a
subprocess. Planning flags emit manual handoffs only.
Hard Safety Rules
- Require exact local archives and hashes; never fetch
latest or switch
installation ownership mid-lifecycle.
- Keep non-secret and runtime-secret values separate. Reject duplicate YAML
keys, aliases, merge keys, unknown spec fields, populated secret-like
non-secret fields, and unsafe runtime override paths. Until a version/hash-
bound closed CSE values/questionnaire contract is supplied, keep
cse_values_contract_missing open even when chart inspection succeeds.
- Never persist raw Secret bodies or unredacted Helm output. Runtime secret
leaves must independently influence only classified Secret payload fields.
- Shared CRDs must already exist and be semantically exact. Dedicated CRDs are
a handoff. Never create, patch, replace, or delete a CRD here.
- Treat hooks, migrations, operator-created claims, cluster-scoped resources,
RBAC, routing/TLS, monitoring, external services, GPU/model artifacts, and
air-gap mirrors as review surfaces, not implicit approval.
- Never delete or alter namespaces, PVCs, PVs, buckets, databases, nodes,
labels, load-balancer pools, or release history.
- A syntactically valid render is not production readiness. Keep explicit gaps
such as
entitled_chart_integration_unvalidated,
cse_values_contract_missing, and live_readonly_integration_unvalidated
open until exact artifacts and connected evidence exist.
Troubleshooting
| Symptom |
Safe response |
| Bundle validation fails |
Preserve the bundle and render a new one; never edit or rehash it |
| Runtime inventory drifts |
Review every new ID and rerender |
| Shared CRD differs |
Stop and coordinate with the cluster CRD owner and Galileo/CSE |
| Routing, storage, data-service, monitoring, or GPU proof is incomplete |
Keep the gate open in the handoff; do not convert an attestation into a pass |
| An apply flag is rejected |
This is expected; execute only through the reviewed Galileo/CSE joint session |
1---2name: galileo-on-prem-stack-setup3description: "Inspect, render, connected-preflight, and observe a pinned Galileo On-Prem galileo-stack deployment on Kubernetes; produce secret-safe evidence and Galileo/CSE joint-session handoffs for every install, upgrade, rollback, uninstall, CRD, galileoctl, GPU, air-gap, and lab-bootstrap change. Use when planning reusable Galileo On-Prem Kubernetes deployment work without unattended mutation."4compatibility: "No direct Splunk Platform runtime dependency. This workflow can be used alongside Splunk Cloud Platform 10.5.2605 through its documented external APIs or handoffs."5metadata:6 source: https://skillmd.com/skills/chambear2809/galileo-on-prem-stack-setup7 splunk_cloud_10_5: "not-applicable"8 compatibility_verified: "2026-08-20"9---1011# Galileo On-Prem Stack Setup1213This skill is render-first and handoff-only. It never invokes a mutating Helm,14Kubernetes, MicroK8s, CRD, node-label, rollback, or uninstall command. The15historical `--apply-*` flags are permanent fail-closed sentinels.1617## When to Activate1819Use this skill when a Galileo On-Prem Kubernetes deployment needs entitled20chart inspection, immutable render evidence, target-bound read-only preflight,21status observation, or a Galileo/CSE joint-session handoff. Do not activate it22to execute Helm, kubectl, MicroK8s, CRD, upgrade, rollback, or uninstall23mutations.2425## Prerequisites2627| Requirement | Why it is required |28|---|---|29| Entitled local `galileo-stack` chart archive, exact version, and SHA-256 | The chart is proprietary and release-specific; never infer its values |30| Version-matched CSE questionnaire and values contract | Product topology and secret paths must come from Galileo, not invented defaults |31| Runtime-only secret values file, mode `0600` or stricter | Secret material is inspected in memory and never copied into the bundle |32| Named kube context, exact API/CA/cluster/namespace identity | Connected evidence must bind one reviewed target |33| Helm 3, `kubectl`, Python 3, and PyYAML | Required for local render and read-only connected inspection |34| External Galileo/CSE change authorization | This local skill does not authenticate or replace change approval |3536## Required Intake3738Ask for the Galileo instance console URL and record it exactly, for example39`https://console.demo-v2.galileocloud.io/`. Pass it with40`--galileo-console-url`; never assume a Galileo Cloud hostname for on-prem.4142Never ask for or repeat passwords in chat. Never put credentials, tokens,43private keys, Secret payloads, or credential-bearing URLs in the spec, command44line, bundle, plans, evidence, logs, or support output.4546## Supported Outcomes4748- Safely inspect a pinned umbrella chart and every nested chart for exact49 dependencies, values/schema flags, images, hooks/migrations, CRDs, API kinds,50 cluster-scoped objects, routes, and persistence surfaces.51- Render a content-addressed private bundle containing only non-secret inputs,52 the exact chart archive, normalized spec, and derived inventories.53- Run a connected, read-only preflight that binds the target, release state,54 active CRDs, API discovery, runtime Secret influence, rendered manifests,55 images, endpoints, storage, routing, monitoring, data services, node pools,56 Wizard/GPU intent, and air-gap handoff evidence.57- Observe live status without claiming health or provenance that was not58 proven. `production_ready` always remains false in this release.59- Prepare canonical pre-approval handoff candidates for all lifecycle changes,60 including official installation methods, upgrades, rollback, retirement,61 galileoctl, dedicated CRDs, GPU/local inference, air-gap, and MicroK8s lab62 bootstrap.6364The current Installation Guide defines four methods: galileoctl (Method A),65umbrella Helm CLI (Method B), deployment script (Method C), and step-by-step66(Method D). The galileoctl UI is identified for first install and its CLI is a67workstation/CI alternative. This skill recognizes all four methods and can68inspect pinned Method A/B chart artifacts. Method C remains incomplete without69the exact script/config hashes and static review; Method D remains incomplete70without the ordered chart/release/dependency contract. It executes none of the71methods. Do not call the raw Helm path vendor-recommended.7273Do not use this skill for Galileo projects, datasets, scorers, model-provider74configuration, Agent Control ownership, or standalone Luna Studio; route those75through their dedicated Galileo skills.7677## Workflow Overview7879```text80┌───────────────────────────────────────────┐81│ Pinned artifacts + closed review inputs │82└───────────────────────────────────────────┘83 ▼84 inspect -> render -> validate85 ▼86 read-only connected preflight87 ▼88 unauthorized candidate -> external Galileo/CSE session89 ▼90 read-only status observation91```9293## Required Workflow94951. Read [reference.md](reference.md),96 [references/lifecycle-contract.md](references/lifecycle-contract.md), and97 [references/coverage-and-safety.md](references/coverage-and-safety.md).982. Run `--inspect-chart`. It emits only a runtime inventory and99 `coverage-review.yaml`; it does not create a deployable bundle.1003. Copy every exact reviewed ID into `spec.coverage`, then run `--render`.1014. Run offline validation on the immutable bundle.1025. Run `--preflight --for-action <action>` against the exact target with the103 runtime secret file. Preflight is read-only; server-side dry-run admission104 checks are non-persisting and are reported separately from observer access.1056. Give the bundle, canonical redacted evidence, unresolved gates, and exact106 target/release inventory to the Galileo/CSE operator. The operator executes107 the vendor-approved command in the jointly controlled session. The emitted108 `handoff-candidate.json` is `authorized:false`; it is not a final approval.1097. Run `--status` for retryable read-only observation. Without independently110 authenticated adoption/provenance evidence it reports an unverified state,111 never successful production completion.112113## Commands114115```bash116bash skills/galileo-on-prem-stack-setup/scripts/setup.sh --help117bash skills/galileo-on-prem-stack-setup/scripts/validate.sh --help118119bash skills/galileo-on-prem-stack-setup/scripts/setup.sh \120 --inspect-chart \121 --spec ./galileo-stack-deployment.yaml \122 --galileo-console-url "$GALILEO_CONSOLE_URL" \123 --output-dir ./galileo-on-prem-rendered124125bash skills/galileo-on-prem-stack-setup/scripts/setup.sh \126 --render \127 --spec ./galileo-stack-deployment.yaml \128 --galileo-console-url "$GALILEO_CONSOLE_URL" \129 --output-dir ./galileo-on-prem-rendered130131bash skills/galileo-on-prem-stack-setup/scripts/validate.sh \132 --bundle ./galileo-on-prem-rendered/acme/<bundle-sha>133134bash skills/galileo-on-prem-stack-setup/scripts/setup.sh \135 --preflight \136 --for-action install \137 --bundle ./galileo-on-prem-rendered/acme/<bundle-sha> \138 --secret-values-file /secure/runtime/secret-values.yaml \139 --galileo-console-url "$GALILEO_CONSOLE_URL"140141bash skills/galileo-on-prem-stack-setup/scripts/setup.sh \142 --status \143 --bundle ./galileo-on-prem-rendered/acme/<bundle-sha> \144 --galileo-console-url "$GALILEO_CONSOLE_URL" \145 --json146```147148`--apply-install`, `--apply-upgrade`, `--apply-rollback`,149`--apply-uninstall`, and `--apply-lab-bootstrap` reject before reading a bundle,150opening a kubeconfig, resolving a binary, writing state, or running a151subprocess. Planning flags emit manual handoffs only.152153## Hard Safety Rules154155- Require exact local archives and hashes; never fetch `latest` or switch156 installation ownership mid-lifecycle.157- Keep non-secret and runtime-secret values separate. Reject duplicate YAML158 keys, aliases, merge keys, unknown spec fields, populated secret-like159 non-secret fields, and unsafe runtime override paths. Until a version/hash-160 bound closed CSE values/questionnaire contract is supplied, keep161 `cse_values_contract_missing` open even when chart inspection succeeds.162- Never persist raw Secret bodies or unredacted Helm output. Runtime secret163 leaves must independently influence only classified Secret payload fields.164- Shared CRDs must already exist and be semantically exact. Dedicated CRDs are165 a handoff. Never create, patch, replace, or delete a CRD here.166- Treat hooks, migrations, operator-created claims, cluster-scoped resources,167 RBAC, routing/TLS, monitoring, external services, GPU/model artifacts, and168 air-gap mirrors as review surfaces, not implicit approval.169- Never delete or alter namespaces, PVCs, PVs, buckets, databases, nodes,170 labels, load-balancer pools, or release history.171- A syntactically valid render is not production readiness. Keep explicit gaps172 such as `entitled_chart_integration_unvalidated`,173 `cse_values_contract_missing`, and `live_readonly_integration_unvalidated`174 open until exact artifacts and connected evidence exist.175176## Troubleshooting177178| Symptom | Safe response |179|---|---|180| Bundle validation fails | Preserve the bundle and render a new one; never edit or rehash it |181| Runtime inventory drifts | Review every new ID and rerender |182| Shared CRD differs | Stop and coordinate with the cluster CRD owner and Galileo/CSE |183| Routing, storage, data-service, monitoring, or GPU proof is incomplete | Keep the gate open in the handoff; do not convert an attestation into a pass |184| An apply flag is rejected | This is expected; execute only through the reviewed Galileo/CSE joint session |