Fix annoted_skaffold.yaml
apiVersion: skaffold/v1alpha2
kind: Config
-
build:
# tagPolicy determines how skaffold is going to tag your images.
# We provide a few strategies here, although you most likely won't need to care!
@@ -21,8 +20,9 @@ build:
# DIGEST | Digest of the newly built image. For eg. `sha256:27ffc7f352665cc50ae3cbcc4b2725e36062f1b38c611b6f95d6df9a7510de23`.
# DIGEST_ALGO | Algorithm used by the digest: For eg. `sha256`.
# DIGEST_HEX | Digest of the newly built image. For eg. `27ffc7f352665cc50ae3cbcc4b2725e36062f1b38c611b6f95d6df9a7510de23`.
- envTemplate:
- template: "{{.RELEASE}}-{{.IMAGE_NAME}}"
+ # Example
+ # envTemplate:
+ # template: "{{.RELEASE}}-{{.IMAGE_NAME}}"
# artifacts is a list of the actual images you're going to be building
# you can include as many as you want here.
@@ -84,14 +84,14 @@ deploy:
kubectl:
# manifests to deploy from files.
manifests:
- - /home/mrick/path/to/different/project/deploy/*
- ../examples/getting-started/k8s-*
# manifests to deploy from remote cluster.
# The path to where these manifests live in remote kubernetes cluster.
- remoteManifests:
- - deployment/web-app1
- - namespace:deployment/web-app2
+ # Examples
+ # remoteManifests:
+ # - deployment/web-app1
+ # - namespace:deployment/web-app2
helm:
# helm releases to deploy.
@@ -106,11 +106,10 @@ deploy:
# setValues get appended to the helm deploy with --set.
setValues:
key: "value"
-
-# profiles can be used to override any build or deploy configuration.
-# When applied, a profile replaces either build or deploy or both default configurations.
+# profiles section has all the profile information which can be used to override any build or deploy configuration
profiles:
- name: gcb
build:
googleCloudBuild:
projectId: k8s-skaffold
+ # Google Cloud Build's project id
