NKP ZeroTouch Framework

Nutanix Kubernetes Platform deployment console
Console Online jgoulden (Admin) CLI apply requires approval

Operator attention required before apply

Runtime checks are available, but blocked environments and drift signals require operator review. Apply-class work remains approval-gated through the controlled CLI path.

Recommended Operator Actions

Highest-signal actions based on current state, drift, evidence, and production gate checks.

Environment Profiles

Deployment targets, readiness signals, gate state, and next operator action.
NameType / ChannelLifecycle / ReadinessDeploy GateDriftEvidenceNext ActionManage

Recent Runs

Latest framework executions captured under the local .zt workspace.
    Destructive and apply actions are intentionally CLI-only. This console exposes validation, preparation, generation, verification, backup, and run inspection workflows.

    Setup and Install

    Editable first-run configuration for source bundles, endpoints, inventory, network, provider, and secret backend metadata.
    AreaCurrent ValueManage
    NKP version
    Standard bundle
    Prism Central endpoint
    Inventory nodes
    Secret backend

    Environment Config Files

    Config records expose add, edit, duplicate, and delete actions before operational use.
    NameFileProviderManage

    Jobs

    Execution queue, approval controls, and captured logs.
    JobActionStatusRequesterApproval

    Runs

    Latest framework execution summaries.

      Pipeline

      ZeroTouch phase progression for a controlled NKP rollout.

      CLI

      Apply-class commands require explicit flags and approval.
      Controlled CLI Window
      PS C:\workspace\nkp-zerotouch-framework>
      Allowed apply examples: registry --apply, deploy --apply, upgrade --apply, destroy --apply --confirm-destroy.

      Artifacts

      Generated plans, reports, logs, state, and configuration evidence.
      ArtifactTypeEnvironmentStatus

      Evidence Packs

      Reviewable evidence bundles created by the evidence phase under .zt/evidence.
      PackEnvironmentCreatedFilesRedactionOpen
      Evidence packs exclude raw kubeconfig and local secret values. Generated plans and logs can still contain topology, VIPs, endpoints, and environment names.

      UAT Readiness

      Maps documented UAT cases to local evidence records, evidence packs, jobs, backups, and run history.
      CaseStatusRequired ResultEvidence Requirement

      Deployment Evidence Records

      Controlled-UAT evidence captured from local phase outputs.
      EnvironmentStatusSignal CoverageBoundary
      UAT evidence is an operational readiness signal, not production validation. Partial coverage means the console found a candidate local signal; an operator still needs reviewed outcomes, exceptions, owners, and environment-specific acceptance before calling UAT complete.

      Restore

      Controlled backup-manifest review, restore plan generation, and approval request workflow.

      Restore Plans

      Clean metadata can request approval; blocked plans require operator remediation first.
      EnvironmentPlanStatusAction
      The approval job records authorization only. This demo, and the local console baseline, do not copy files or restore live infrastructure.

      Console Section

      Static demo snapshot of the local NKP ZeroTouch console.