Log in here
Spotlighted blog5 min readVCFA Features Blog

Canada VCFA 3 tier app operator walkthrough

Canada VCFA 3 tier app operator walkthrough.

review the canada blueprint file. create or update it in project: Canada. release and deploy it in project: Canada. prove it in VCFA and kubectl.

article section

Canada operator walkthrough

This walkthrough stays in one place: Countries org, project-canada, namespace ns-quebec-01-6kf9r. I started with a plain Kubernetes manifest, then wrapped the same three tiers in a VCFA blueprint so the app had versioning, release history, and a real deployment record.

The important fix was small but real. VCFA wanted embedded manifests stored as structured objects under manifest, not string blocks. Once that was corrected, the blueprint validated cleanly and became something an operator could create, release, and deploy on purpose.

The Canada blueprint file is below first, then the side-by-side difference between Kubernetes manifest YAML and VCFA blueprint YAML.

Canada blueprint file contents

VCFA blueprint YAML versus Kubernetes manifest YAML

Canada blueprint in the VCFA list

Canada target namespace

article section

Deploy and prove the Canada app

Canada deployment resources

Proving the Canada 3 tier app pods deployed

article section

Summary

The operator path is direct once the blueprint file is clean. Read the VCFA blueprint YAML, create or update the blueprint in project-canada, release a version, deploy it, and then prove the result in both VCFA and kubectl.

Under the hood, we used VCFA blueprint YAML made of VCFA resources. Those VCFA resources wrapped Kubernetes manifest YAML under manifest blocks. VCFA pushed that into namespace ns-quebec-01-6kf9r in project-canada inside the Countries org, and Kubernetes turned it into the running web, API, and Postgres pods.

Guided track
3 stepsreadystaged simulation

This walkthrough is simulated. The commands are real, but playback from this page does not mutate live infrastructure.

current raw commands

Step 1/3
Get-Content .\manifests\vks\countries-three-tier-blueprint.yaml
01

Review the manifest file

Read the Kubernetes manifest

ready
Get-Content .\manifests\vks\countries-three-tier-blueprint.yaml
02

Apply the manifest with kubectl

Apply the manifest

pending
03

Inspect the direct manifest runtime

Prove the manifest runtime

pending
>

Kubernetes Manifest workflow

Expand to see the phase-by-phase operator sequence for this tab.

3 phases
>
phase 01Read the Kubernetes manifeststaged

Start with the raw Kubernetes manifest so users can see the plain YAML path before VCFA wraps anything.

1 cmds
  1. 01
    Open the raw Kubernetes manifest file that was applied directly into the Canada namespace.
    show raw commands
    selected command
    Get-Content .\manifests\vks\countries-three-tier-blueprint.yaml
>
phase 02Apply the manifeststaged

Apply the manifest directly into the namespace with kubectl and keep the command visible exactly as an operator would run it.

1 cmds
  1. 01
    Apply the three-tier app directly into ns-quebec-01-6kf9r with kubectl.
    show raw commands
    selected command
    kubectl apply -f .\manifests\vks\countries-three-tier-blueprint.yaml -n ns-quebec-01-6kf9r
>
phase 03Prove the manifest runtimestaged

Prove the direct manifest path with the services, pvc, and pods that land in the namespace.

1 cmds
  1. 01
    Read the service, pvc, and pod state for the directly applied manifest deployment.
    show raw commands
    selected command
    kubectl get svc -n ns-quebec-01-6kf9r | findstr countries-three-tier
    raw step 01
    kubectl get pvc -n ns-quebec-01-6kf9r | findstr countries-three-tier
    raw step 02
    kubectl get pods -n ns-quebec-01-6kf9r | findstr countries-three-tier
live terminalproof@lab

Canada VCFA 3 tier app operator walkthrough terminal

Guided proof playback. Commands stream automatically from start to finish.

command lineidle
proof@lab$

history buffer

Run a command to capture the last five entries here. Each row stays compact until you expand it.