Neon Law | Workshops | Deploy The Navigator | Step

Agenda

Six steps, each tagged with its Bloom verb. You are the admin operator; the navigator CLI is the instrument:

Create — stand up a billed project and authenticate.
Predict — run --dry-run and read every API call before sending one.
Identify — name the twenty-three Google Cloud APIs the provisioner enables.
Explain — describe the VPC, five core buckets, optional archive/telemetry lanes, private image registry, and three service deployments.
Execute — bring up the cluster, the static IP, and Fleet membership.
Verify — ship the service images and confirm /readyz answers 200.

Presenter notes

Each step is tagged with the Bloom verb it exercises (the Anderson & Krathwohl 2001 revision). You are the admin operator; the navigator CLI is the instrument. Create — stand up a billed Google Cloud project and authenticate so navigator can act on your behalf. Predict — run navigator ops gcp setup --dry-run and read every API call the provisioner would make before sending one. Identify — name the twenty-three Google Cloud APIs the provisioner enables, and why each is needed. Explain — describe the VPC, the five core storage buckets and optional archive/telemetry lanes, the private image registry, the two service deployments, and why re-running setup is always safe. Execute — bring up the GKE Autopilot cluster, the static IP, and Fleet membership with one command. Verify — ship the service images and confirm the running service answers /readyz with a 200.

View all slides Open display