Deployment

This is the primary tenant workflow for managed non-production application deployment.

Standard local developer deployment lifecycle

For the normal interactive developer path, build the application locally and let gwebc upload and import the image into the GWEB-managed internal registry.

1. Build application locally
2. Run tests
3. Inspect the deployment plan
4. Push the local image through gwebc
5. GWEB imports the image into its internal registry
6. GWEB updates the managed tenant Deployment
7. Inspect rollout state and diagnostics
8. Advance to preprod when ready
9. Request controlled production promotion when ready

Example:

docker build --platform linux/amd64 -t <application>:dev .

gwebc --profile <profile> \
  deploy push <application> \
  --environment dev \
  --local-image <application>:dev \
  --replicas <replicas> \
  --port <container-port>

gwebc deploy push is the canonical local developer path because it keeps registry ingestion and Kubernetes mutation inside the GWEB control plane. Tenants do not need kubectl, cluster credentials, internal-registry credentials, or Kubernetes imagePullSecrets for this workflow.

Inspect deployment service

gwebc --profile <profile> deploy status

Plan first

gwebc --profile <profile> \
  deploy plan <application> \
  --environment dev

Deploy an already available image reference

deploy apply --image is a separate path for an image that is already reachable by the GWEB runtime under the applicable registry policy.

gwebc --profile <profile> \
  deploy apply <application> \
  --environment dev \
  --image <registry>/<repository>@sha256:<digest>

Do not assume that an arbitrary private external-registry reference is pullable by the cluster. If the image is local to the developer workstation, use deploy push --local-image instead.

Inspect rollout state

gwebc --profile <profile> \
  deploy show <application> \
  --environment dev

gwebc --profile <profile> \
  deploy history <application> \
  --environment dev

gwebc --profile <profile> \
  app diagnostics <application> \
  --environment dev

Application availability and latest-rollout convergence are related but distinct. An application can remain READY because an older healthy ReplicaSet is still serving while the newest revision has not yet become Ready. Use deployment history and application diagnostics to confirm the newest revision has converged.

Production

Normal gwebc deploy push, deploy restart, deploy apply, and deploy rollback are not production commands. Production uses the controlled promotion workflow.