1. Schema version
apiVersion pins the skaffold config schema; v4beta11 is a current Config version.
apiVersion: skaffold/v4beta11Typorithm · easy
Step 1 of 8 · intro card
Skaffold & Dev
skaffold.yaml ties build and deploy together: build.artifacts say what image to build and from where, and deploy.kubectl.manifests say what to apply — so one config drives the whole local loop.
A skaffold.yaml is a single Config (apiVersion: skaffold/v4beta*, kind: Config) that wires together how your app is built and how it is deployed.
build.artifacts each declare an image and a context directory; Skaffold builds them and rewrites that image reference in your manifests with the freshly built tag.
deploy chooses a deployer — kubectl with a list of manifests, or helm with releases — so build output flows straight into the cluster.
kind: Config is the pipeline root.
build.artifacts: image + context per build.
deploy.kubectl.manifests applies the YAML.
apiVersion: skaffold/v4beta11
kind: Config
build:
artifacts:
- image: web
context: ./web
deploy:
kubectl:
manifests:
- k8s/*.yamlConnect each part of the code to the concept before you type.
apiVersion pins the skaffold config schema; v4beta11 is a current Config version.
apiVersion: skaffold/v4beta11kind: Config marks this as a top-level Skaffold pipeline definition.
kind: Configbuild.artifacts[].image names the image Skaffold builds and substitutes into manifests.
image: webcontext is the directory (with its Dockerfile) Skaffold builds the artifact from.
context: ./webdeploy.kubectl.manifests lists the YAML Skaffold applies after building.
manifests:Read the concept map and follow the code breakdown.
Type the implementation, repair mistakes and work through every recall exercise.
Use the final check without hints; revisit weak concepts in short practice sessions.