From fb6b62ef9c7a5468eb7a5e33b216ef5b267b4692 Mon Sep 17 00:00:00 2001 From: Tejal Desai Date: Tue, 2 Aug 2022 14:39:59 -0700 Subject: [PATCH] feat: respect CLI flag in skaffold render (#7664) * feat: respect CLI flag in skaffold render * fix: fix integration test * fix: integration test namespace * wip * fix: integration test when metadata name is not present * don't traverse recursively for setting namespace since it only appears at the parent level * feat: only set namespaces if a manifest is in resource selector * address code review comments * fix integration tests to make them compatible with v1 behavior * fix integration tests * offline set to true, then don't set namespace * fix unit tests * add namesapce back * fix typos --- cmd/skaffold/app/cmd/flags.go | 2 +- .../content/en/api-v2/skaffold.swagger.json | 7 +- docs-v2/content/en/api/skaffold.swagger.json | 59 ++- .../content/en/docs/references/api-v2/grpc.md | 3 + .../content/en/docs/references/api/grpc.md | 3 + docs/content/en/api-v2/skaffold.swagger.json | 7 +- docs/content/en/api/skaffold.swagger.json | 59 ++- .../content/en/docs/references/api-v2/grpc.md | 3 + docs/content/en/docs/references/api/grpc.md | 3 + docs/content/en/docs/references/cli/_index.md | 16 +- examples/getting-started/k8s-pod.yaml | 1 + integration/render_test.go | 36 +- pkg/skaffold/deploy/helm/helm.go | 1 + pkg/skaffold/deploy/kubectl/cli.go | 1 + pkg/skaffold/deploy/kubectl/kubectl_test.go | 6 +- pkg/skaffold/deploy/kubectl/kustomize_test.go | 6 +- pkg/skaffold/kubernetes/manifest/errors.go | 23 + .../kubernetes/manifest/namespace_test.go | 233 ++++++++++ .../kubernetes/manifest/namespaces.go | 70 ++- pkg/skaffold/render/config.go | 3 + pkg/skaffold/render/generate/generate_test.go | 3 +- pkg/skaffold/render/renderer/kpt/kpt.go | 9 +- pkg/skaffold/render/renderer/kpt/kpt_test.go | 7 +- .../render/renderer/kubectl/kubectl.go | 7 +- .../render/renderer/kubectl/kubectl_test.go | 8 +- pkg/skaffold/render/renderer/renderer.go | 6 +- pkg/skaffold/render/renderer/util/util.go | 13 +- proto/enums/enums.pb.go | 405 +++++++++--------- proto/enums/enums.proto | 6 + proto/v1/skaffold.pb.go | 3 + proto/v2/skaffold.pb.go | 3 + 31 files changed, 737 insertions(+), 275 deletions(-) diff --git a/cmd/skaffold/app/cmd/flags.go b/cmd/skaffold/app/cmd/flags.go index ac6019232d3..f11984d829e 100644 --- a/cmd/skaffold/app/cmd/flags.go +++ b/cmd/skaffold/app/cmd/flags.go @@ -109,7 +109,7 @@ var flagRegistry = []Flag{ { Name: "namespace", Shorthand: "n", - Usage: "Run deployments in the specified namespace", + Usage: "Runs deployments in the specified namespace. When used with 'render' command, renders manifests contain the namespace", Value: &opts.Namespace, DefValue: "", FlagAddMethod: "StringVar", diff --git a/docs-v2/content/en/api-v2/skaffold.swagger.json b/docs-v2/content/en/api-v2/skaffold.swagger.json index d15129a66bd..9b919612838 100644 --- a/docs-v2/content/en/api-v2/skaffold.swagger.json +++ b/docs-v2/content/en/api-v2/skaffold.swagger.json @@ -501,6 +501,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -526,7 +528,7 @@ "PORT_FORWARD_RUN_PROXY_START_ERROR" ], "default": "OK", - "description": "Enum for Status codes
\nThese error codes are prepended by Phase Name e.g.\nINIT, BUILD, TEST, DEPLOY, STATUSCHECK, DEVINIT
\nFor Success Error codes, use range 200 to 250.
\nFor Unknown error codes, use range 500 to 600.
\nFor Cancelled Error code, use range 800 to 850.
\n- OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist" + "description": "Enum for Status codes
\nThese error codes are prepended by Phase Name e.g.\nINIT, BUILD, TEST, DEPLOY, STATUSCHECK, DEVINIT
\nFor Success Error codes, use range 200 to 250.
\nFor Unknown error codes, use range 500 to 600.
\nFor Cancelled Error code, use range 800 to 850.
\n- OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist" }, "enumsSuggestionCode": { "type": "string", @@ -578,6 +580,7 @@ "SET_RENDER_FLAG_OFFLINE_FALSE", "KPTFILE_MANUAL_INIT", "KPTFILE_CHECK_YAML", + "REMOVE_NAMESPACE_FROM_MANIFESTS", "CONFIG_CHECK_FILE_PATH", "CONFIG_CHECK_DEPENDENCY_DEFINITION", "CONFIG_CHANGE_NAMES", @@ -601,7 +604,7 @@ "CHECK_TEST_COMMAND_AND_IMAGE_NAME" ], "default": "NIL", - "description": "Enum for Suggestion codes\n- NIL: default nil suggestion.\nThis is usually set when no error happens.\n - ADD_DEFAULT_REPO: Add Default Repo\n - CHECK_DEFAULT_REPO: Verify Default Repo\n - CHECK_DEFAULT_REPO_GLOBAL_CONFIG: Verify default repo in the global config\n - GCLOUD_DOCKER_AUTH_CONFIGURE: run gcloud docker auth configure\n - DOCKER_AUTH_CONFIGURE: Run docker auth configure\n - CHECK_GCLOUD_PROJECT: Verify Gcloud Project\n - CHECK_DOCKER_RUNNING: Check if docker is running\n - FIX_USER_BUILD_ERR: Fix User Build Error\n - DOCKER_BUILD_RETRY: Docker build internal error, try again\n - FIX_CACHE_FROM_ARTIFACT_CONFIG: Fix `cacheFrom` config for given artifact and try again\n - FIX_SKAFFOLD_CONFIG_DOCKERFILE: Fix `dockerfile` config for a given artifact and try again.\n - FIX_JIB_PLUGIN_CONFIGURATION: Use a supported Jib plugin type\n - FIX_DOCKER_NETWORK_CONTAINER_NAME: Docker build network invalid docker container name (or id).\n - CHECK_DOCKER_NETWORK_CONTAINER_RUNNING: Docker build network container not existing in the current context.\n - FIX_DOCKER_NETWORK_MODE_WHEN_EXTRACTING_CONTAINER_NAME: Executing extractContainerNameFromNetworkMode with a non valid mode (only container mode allowed)\n - RUN_DOCKER_PRUNE: Prune Docker image\n - SET_CLEANUP_FLAG: Set Cleanup flag for skaffold command.\n - BUILD_FIX_UNKNOWN_PLATFORM_FLAG: Build platform error suggestion codes\n - CHECK_CLUSTER_CONNECTION: Check cluster connection\n - CHECK_MINIKUBE_STATUS: Check minikube status\n - INSTALL_HELM: Install helm tool\n - UPGRADE_HELM: Upgrade helm tool\n - FIX_SKAFFOLD_CONFIG_HELM_ARTIFACT_OVERRIDES: Fix helm `releases.artifactOverrides` config to match with `build.artifacts` (no longer used in Skaffold v2)\n - UPGRADE_HELM32: Upgrade helm version to v3.2.0 and higher.\n - FIX_SKAFFOLD_CONFIG_HELM_CREATE_NAMESPACE: Set `releases.createNamespace` to false.\n - INVALID_KPT_MANIFESTS: check the Kptfile validation.\n - ALIGN_KPT_INVENTORY: align the inventory info in kpt live apply.\n - INSTALL_KUBECTL: Install kubectl tool\n - CHECK_CONTAINER_LOGS: Container run error\n - CHECK_READINESS_PROBE: Pod Health check error\n - CHECK_CONTAINER_IMAGE: Check Container image\n - ADDRESS_NODE_MEMORY_PRESSURE: Node pressure error\n - ADDRESS_NODE_DISK_PRESSURE: Node disk pressure error\n - ADDRESS_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - ADDRESS_NODE_PID_PRESSURE: Node PID pressure error\n - ADDRESS_NODE_UNSCHEDULABLE: Node unschedulable error\n - ADDRESS_NODE_UNREACHABLE: Node unreachable error\n - ADDRESS_NODE_NOT_READY: Node not ready error\n - ADDRESS_FAILED_SCHEDULING: Scheduler failure error\n - CHECK_HOST_CONNECTION: Cluster Connectivity error\n - START_MINIKUBE: Minikube is stopped: use `minikube start`\n - UNPAUSE_MINIKUBE: Minikube is paused: use `minikube unpause`\n - RUN_DOCKER_PULL: Run Docker pull for the image with v1 manifest and try again.\n - SET_RENDER_FLAG_OFFLINE_FALSE: Rerun with correct offline flag value.\n - KPTFILE_MANUAL_INIT: Manually run `kpt pkg init` or `kpt live init`\n - KPTFILE_CHECK_YAML: Check if the Kptfile is correct.\n - CONFIG_CHECK_FILE_PATH: Check configuration file path\n - CONFIG_CHECK_DEPENDENCY_DEFINITION: Check dependency config definition\n - CONFIG_CHANGE_NAMES: Change config name to avoid duplicates\n - CONFIG_CHECK_FILTER: Check config filter\n - CONFIG_CHECK_PROFILE_DEFINITION: Check profile definition in current config\n - CONFIG_CHECK_DEPENDENCY_PROFILES_SELECTION: Check active profile selection for dependency config\n - CONFIG_CHECK_PROFILE_SELECTION: Check profile selection flag\n - CONFIG_FIX_API_VERSION: Fix config API version or upgrade the skaffold binary\n - CONFIG_ALLOWLIST_VALIDATORS: Only the allow listed validators are acceptable in skaffold-managed mode.\n - CONFIG_ALLOWLIST_transformers: Only the allow listed transformers are acceptable in skaffold-managed mode.\n - CONFIG_FIX_MISSING_MANIFEST_FILE: Check mising manifest file section of config and fix as needed.\n - CONFIG_ENABLE_REMOTE_REPO_SYNC: Enable remote repo sync, or clone manually\n - INSPECT_USE_MODIFY_OR_NEW_PROFILE: Create new build env in a profile instead, or use the 'modify' command\n - INSPECT_USE_ADD_BUILD_ENV: Check profile selection, or use the 'add' command instead\n - INSPECT_CHECK_INPUT_PROFILE: Check profile flag value\n - OPEN_ISSUE: Open an issue so this situation can be diagnosed\n - CHECK_CUSTOM_COMMAND: Test error suggestion codes" + "description": "Enum for Suggestion codes\n- NIL: default nil suggestion.\nThis is usually set when no error happens.\n - ADD_DEFAULT_REPO: Add Default Repo\n - CHECK_DEFAULT_REPO: Verify Default Repo\n - CHECK_DEFAULT_REPO_GLOBAL_CONFIG: Verify default repo in the global config\n - GCLOUD_DOCKER_AUTH_CONFIGURE: run gcloud docker auth configure\n - DOCKER_AUTH_CONFIGURE: Run docker auth configure\n - CHECK_GCLOUD_PROJECT: Verify Gcloud Project\n - CHECK_DOCKER_RUNNING: Check if docker is running\n - FIX_USER_BUILD_ERR: Fix User Build Error\n - DOCKER_BUILD_RETRY: Docker build internal error, try again\n - FIX_CACHE_FROM_ARTIFACT_CONFIG: Fix `cacheFrom` config for given artifact and try again\n - FIX_SKAFFOLD_CONFIG_DOCKERFILE: Fix `dockerfile` config for a given artifact and try again.\n - FIX_JIB_PLUGIN_CONFIGURATION: Use a supported Jib plugin type\n - FIX_DOCKER_NETWORK_CONTAINER_NAME: Docker build network invalid docker container name (or id).\n - CHECK_DOCKER_NETWORK_CONTAINER_RUNNING: Docker build network container not existing in the current context.\n - FIX_DOCKER_NETWORK_MODE_WHEN_EXTRACTING_CONTAINER_NAME: Executing extractContainerNameFromNetworkMode with a non valid mode (only container mode allowed)\n - RUN_DOCKER_PRUNE: Prune Docker image\n - SET_CLEANUP_FLAG: Set Cleanup flag for skaffold command.\n - BUILD_FIX_UNKNOWN_PLATFORM_FLAG: Build platform error suggestion codes\n - CHECK_CLUSTER_CONNECTION: Check cluster connection\n - CHECK_MINIKUBE_STATUS: Check minikube status\n - INSTALL_HELM: Install helm tool\n - UPGRADE_HELM: Upgrade helm tool\n - FIX_SKAFFOLD_CONFIG_HELM_ARTIFACT_OVERRIDES: Fix helm `releases.artifactOverrides` config to match with `build.artifacts` (no longer used in Skaffold v2)\n - UPGRADE_HELM32: Upgrade helm version to v3.2.0 and higher.\n - FIX_SKAFFOLD_CONFIG_HELM_CREATE_NAMESPACE: Set `releases.createNamespace` to false.\n - INVALID_KPT_MANIFESTS: check the Kptfile validation.\n - ALIGN_KPT_INVENTORY: align the inventory info in kpt live apply.\n - INSTALL_KUBECTL: Install kubectl tool\n - CHECK_CONTAINER_LOGS: Container run error\n - CHECK_READINESS_PROBE: Pod Health check error\n - CHECK_CONTAINER_IMAGE: Check Container image\n - ADDRESS_NODE_MEMORY_PRESSURE: Node pressure error\n - ADDRESS_NODE_DISK_PRESSURE: Node disk pressure error\n - ADDRESS_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - ADDRESS_NODE_PID_PRESSURE: Node PID pressure error\n - ADDRESS_NODE_UNSCHEDULABLE: Node unschedulable error\n - ADDRESS_NODE_UNREACHABLE: Node unreachable error\n - ADDRESS_NODE_NOT_READY: Node not ready error\n - ADDRESS_FAILED_SCHEDULING: Scheduler failure error\n - CHECK_HOST_CONNECTION: Cluster Connectivity error\n - START_MINIKUBE: Minikube is stopped: use `minikube start`\n - UNPAUSE_MINIKUBE: Minikube is paused: use `minikube unpause`\n - RUN_DOCKER_PULL: Run Docker pull for the image with v1 manifest and try again.\n - SET_RENDER_FLAG_OFFLINE_FALSE: Rerun with correct offline flag value.\n - KPTFILE_MANUAL_INIT: Manually run `kpt pkg init` or `kpt live init`\n - KPTFILE_CHECK_YAML: Check if the Kptfile is correct.\n - REMOVE_NAMESPACE_FROM_MANIFESTS: Remove namespace from manifests\n - CONFIG_CHECK_FILE_PATH: Check configuration file path\n - CONFIG_CHECK_DEPENDENCY_DEFINITION: Check dependency config definition\n - CONFIG_CHANGE_NAMES: Change config name to avoid duplicates\n - CONFIG_CHECK_FILTER: Check config filter\n - CONFIG_CHECK_PROFILE_DEFINITION: Check profile definition in current config\n - CONFIG_CHECK_DEPENDENCY_PROFILES_SELECTION: Check active profile selection for dependency config\n - CONFIG_CHECK_PROFILE_SELECTION: Check profile selection flag\n - CONFIG_FIX_API_VERSION: Fix config API version or upgrade the skaffold binary\n - CONFIG_ALLOWLIST_VALIDATORS: Only the allow listed validators are acceptable in skaffold-managed mode.\n - CONFIG_ALLOWLIST_transformers: Only the allow listed transformers are acceptable in skaffold-managed mode.\n - CONFIG_FIX_MISSING_MANIFEST_FILE: Check mising manifest file section of config and fix as needed.\n - CONFIG_ENABLE_REMOTE_REPO_SYNC: Enable remote repo sync, or clone manually\n - INSPECT_USE_MODIFY_OR_NEW_PROFILE: Create new build env in a profile instead, or use the 'modify' command\n - INSPECT_USE_ADD_BUILD_ENV: Check profile selection, or use the 'add' command instead\n - INSPECT_CHECK_INPUT_PROFILE: Check profile flag value\n - OPEN_ISSUE: Open an issue so this situation can be diagnosed\n - CHECK_CUSTOM_COMMAND: Test error suggestion codes" }, "enumsTesterType": { "type": "string", diff --git a/docs-v2/content/en/api/skaffold.swagger.json b/docs-v2/content/en/api/skaffold.swagger.json index a6a534532f8..5b9356837fb 100644 --- a/docs-v2/content/en/api/skaffold.swagger.json +++ b/docs-v2/content/en/api/skaffold.swagger.json @@ -151,7 +151,7 @@ }, { "name": "event.buildEvent.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -322,6 +322,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -350,7 +352,7 @@ }, { "name": "event.buildEvent.actionableErr.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -521,6 +523,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -579,7 +583,7 @@ }, { "name": "event.deployEvent.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -750,6 +754,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -778,7 +784,7 @@ }, { "name": "event.deployEvent.actionableErr.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -949,6 +955,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -1077,7 +1085,7 @@ }, { "name": "event.statusCheckEvent.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -1248,6 +1256,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -1276,7 +1286,7 @@ }, { "name": "event.statusCheckEvent.actionableErr.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -1447,6 +1457,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -1505,7 +1517,7 @@ }, { "name": "event.resourceStatusCheckEvent.statusCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -1676,6 +1688,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -1704,7 +1718,7 @@ }, { "name": "event.resourceStatusCheckEvent.actionableErr.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -1875,6 +1889,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -1934,7 +1950,7 @@ }, { "name": "event.fileSyncEvent.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -2105,6 +2121,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -2133,7 +2151,7 @@ }, { "name": "event.fileSyncEvent.actionableErr.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -2304,6 +2322,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -2393,7 +2413,7 @@ }, { "name": "event.devLoopEvent.err.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -2564,6 +2584,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -2604,7 +2626,7 @@ }, { "name": "event.terminationEvent.err.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -2775,6 +2797,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -2815,7 +2839,7 @@ }, { "name": "event.TestEvent.actionableErr.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -2986,6 +3010,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -3401,6 +3427,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -3426,7 +3454,7 @@ "PORT_FORWARD_RUN_PROXY_START_ERROR" ], "default": "OK", - "description": "Enum for Status codes
\nThese error codes are prepended by Phase Name e.g.\nINIT, BUILD, TEST, DEPLOY, STATUSCHECK, DEVINIT
\nFor Success Error codes, use range 200 to 250.
\nFor Unknown error codes, use range 500 to 600.
\nFor Cancelled Error code, use range 800 to 850.
\n- OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist" + "description": "Enum for Status codes
\nThese error codes are prepended by Phase Name e.g.\nINIT, BUILD, TEST, DEPLOY, STATUSCHECK, DEVINIT
\nFor Success Error codes, use range 200 to 250.
\nFor Unknown error codes, use range 500 to 600.
\nFor Cancelled Error code, use range 800 to 850.
\n- OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist" }, "enumsSuggestionCode": { "type": "string", @@ -3478,6 +3506,7 @@ "SET_RENDER_FLAG_OFFLINE_FALSE", "KPTFILE_MANUAL_INIT", "KPTFILE_CHECK_YAML", + "REMOVE_NAMESPACE_FROM_MANIFESTS", "CONFIG_CHECK_FILE_PATH", "CONFIG_CHECK_DEPENDENCY_DEFINITION", "CONFIG_CHANGE_NAMES", @@ -3501,7 +3530,7 @@ "CHECK_TEST_COMMAND_AND_IMAGE_NAME" ], "default": "NIL", - "description": "Enum for Suggestion codes\n- NIL: default nil suggestion.\nThis is usually set when no error happens.\n - ADD_DEFAULT_REPO: Add Default Repo\n - CHECK_DEFAULT_REPO: Verify Default Repo\n - CHECK_DEFAULT_REPO_GLOBAL_CONFIG: Verify default repo in the global config\n - GCLOUD_DOCKER_AUTH_CONFIGURE: run gcloud docker auth configure\n - DOCKER_AUTH_CONFIGURE: Run docker auth configure\n - CHECK_GCLOUD_PROJECT: Verify Gcloud Project\n - CHECK_DOCKER_RUNNING: Check if docker is running\n - FIX_USER_BUILD_ERR: Fix User Build Error\n - DOCKER_BUILD_RETRY: Docker build internal error, try again\n - FIX_CACHE_FROM_ARTIFACT_CONFIG: Fix `cacheFrom` config for given artifact and try again\n - FIX_SKAFFOLD_CONFIG_DOCKERFILE: Fix `dockerfile` config for a given artifact and try again.\n - FIX_JIB_PLUGIN_CONFIGURATION: Use a supported Jib plugin type\n - FIX_DOCKER_NETWORK_CONTAINER_NAME: Docker build network invalid docker container name (or id).\n - CHECK_DOCKER_NETWORK_CONTAINER_RUNNING: Docker build network container not existing in the current context.\n - FIX_DOCKER_NETWORK_MODE_WHEN_EXTRACTING_CONTAINER_NAME: Executing extractContainerNameFromNetworkMode with a non valid mode (only container mode allowed)\n - RUN_DOCKER_PRUNE: Prune Docker image\n - SET_CLEANUP_FLAG: Set Cleanup flag for skaffold command.\n - BUILD_FIX_UNKNOWN_PLATFORM_FLAG: Build platform error suggestion codes\n - CHECK_CLUSTER_CONNECTION: Check cluster connection\n - CHECK_MINIKUBE_STATUS: Check minikube status\n - INSTALL_HELM: Install helm tool\n - UPGRADE_HELM: Upgrade helm tool\n - FIX_SKAFFOLD_CONFIG_HELM_ARTIFACT_OVERRIDES: Fix helm `releases.artifactOverrides` config to match with `build.artifacts` (no longer used in Skaffold v2)\n - UPGRADE_HELM32: Upgrade helm version to v3.2.0 and higher.\n - FIX_SKAFFOLD_CONFIG_HELM_CREATE_NAMESPACE: Set `releases.createNamespace` to false.\n - INVALID_KPT_MANIFESTS: check the Kptfile validation.\n - ALIGN_KPT_INVENTORY: align the inventory info in kpt live apply.\n - INSTALL_KUBECTL: Install kubectl tool\n - CHECK_CONTAINER_LOGS: Container run error\n - CHECK_READINESS_PROBE: Pod Health check error\n - CHECK_CONTAINER_IMAGE: Check Container image\n - ADDRESS_NODE_MEMORY_PRESSURE: Node pressure error\n - ADDRESS_NODE_DISK_PRESSURE: Node disk pressure error\n - ADDRESS_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - ADDRESS_NODE_PID_PRESSURE: Node PID pressure error\n - ADDRESS_NODE_UNSCHEDULABLE: Node unschedulable error\n - ADDRESS_NODE_UNREACHABLE: Node unreachable error\n - ADDRESS_NODE_NOT_READY: Node not ready error\n - ADDRESS_FAILED_SCHEDULING: Scheduler failure error\n - CHECK_HOST_CONNECTION: Cluster Connectivity error\n - START_MINIKUBE: Minikube is stopped: use `minikube start`\n - UNPAUSE_MINIKUBE: Minikube is paused: use `minikube unpause`\n - RUN_DOCKER_PULL: Run Docker pull for the image with v1 manifest and try again.\n - SET_RENDER_FLAG_OFFLINE_FALSE: Rerun with correct offline flag value.\n - KPTFILE_MANUAL_INIT: Manually run `kpt pkg init` or `kpt live init`\n - KPTFILE_CHECK_YAML: Check if the Kptfile is correct.\n - CONFIG_CHECK_FILE_PATH: Check configuration file path\n - CONFIG_CHECK_DEPENDENCY_DEFINITION: Check dependency config definition\n - CONFIG_CHANGE_NAMES: Change config name to avoid duplicates\n - CONFIG_CHECK_FILTER: Check config filter\n - CONFIG_CHECK_PROFILE_DEFINITION: Check profile definition in current config\n - CONFIG_CHECK_DEPENDENCY_PROFILES_SELECTION: Check active profile selection for dependency config\n - CONFIG_CHECK_PROFILE_SELECTION: Check profile selection flag\n - CONFIG_FIX_API_VERSION: Fix config API version or upgrade the skaffold binary\n - CONFIG_ALLOWLIST_VALIDATORS: Only the allow listed validators are acceptable in skaffold-managed mode.\n - CONFIG_ALLOWLIST_transformers: Only the allow listed transformers are acceptable in skaffold-managed mode.\n - CONFIG_FIX_MISSING_MANIFEST_FILE: Check mising manifest file section of config and fix as needed.\n - CONFIG_ENABLE_REMOTE_REPO_SYNC: Enable remote repo sync, or clone manually\n - INSPECT_USE_MODIFY_OR_NEW_PROFILE: Create new build env in a profile instead, or use the 'modify' command\n - INSPECT_USE_ADD_BUILD_ENV: Check profile selection, or use the 'add' command instead\n - INSPECT_CHECK_INPUT_PROFILE: Check profile flag value\n - OPEN_ISSUE: Open an issue so this situation can be diagnosed\n - CHECK_CUSTOM_COMMAND: Test error suggestion codes" + "description": "Enum for Suggestion codes\n- NIL: default nil suggestion.\nThis is usually set when no error happens.\n - ADD_DEFAULT_REPO: Add Default Repo\n - CHECK_DEFAULT_REPO: Verify Default Repo\n - CHECK_DEFAULT_REPO_GLOBAL_CONFIG: Verify default repo in the global config\n - GCLOUD_DOCKER_AUTH_CONFIGURE: run gcloud docker auth configure\n - DOCKER_AUTH_CONFIGURE: Run docker auth configure\n - CHECK_GCLOUD_PROJECT: Verify Gcloud Project\n - CHECK_DOCKER_RUNNING: Check if docker is running\n - FIX_USER_BUILD_ERR: Fix User Build Error\n - DOCKER_BUILD_RETRY: Docker build internal error, try again\n - FIX_CACHE_FROM_ARTIFACT_CONFIG: Fix `cacheFrom` config for given artifact and try again\n - FIX_SKAFFOLD_CONFIG_DOCKERFILE: Fix `dockerfile` config for a given artifact and try again.\n - FIX_JIB_PLUGIN_CONFIGURATION: Use a supported Jib plugin type\n - FIX_DOCKER_NETWORK_CONTAINER_NAME: Docker build network invalid docker container name (or id).\n - CHECK_DOCKER_NETWORK_CONTAINER_RUNNING: Docker build network container not existing in the current context.\n - FIX_DOCKER_NETWORK_MODE_WHEN_EXTRACTING_CONTAINER_NAME: Executing extractContainerNameFromNetworkMode with a non valid mode (only container mode allowed)\n - RUN_DOCKER_PRUNE: Prune Docker image\n - SET_CLEANUP_FLAG: Set Cleanup flag for skaffold command.\n - BUILD_FIX_UNKNOWN_PLATFORM_FLAG: Build platform error suggestion codes\n - CHECK_CLUSTER_CONNECTION: Check cluster connection\n - CHECK_MINIKUBE_STATUS: Check minikube status\n - INSTALL_HELM: Install helm tool\n - UPGRADE_HELM: Upgrade helm tool\n - FIX_SKAFFOLD_CONFIG_HELM_ARTIFACT_OVERRIDES: Fix helm `releases.artifactOverrides` config to match with `build.artifacts` (no longer used in Skaffold v2)\n - UPGRADE_HELM32: Upgrade helm version to v3.2.0 and higher.\n - FIX_SKAFFOLD_CONFIG_HELM_CREATE_NAMESPACE: Set `releases.createNamespace` to false.\n - INVALID_KPT_MANIFESTS: check the Kptfile validation.\n - ALIGN_KPT_INVENTORY: align the inventory info in kpt live apply.\n - INSTALL_KUBECTL: Install kubectl tool\n - CHECK_CONTAINER_LOGS: Container run error\n - CHECK_READINESS_PROBE: Pod Health check error\n - CHECK_CONTAINER_IMAGE: Check Container image\n - ADDRESS_NODE_MEMORY_PRESSURE: Node pressure error\n - ADDRESS_NODE_DISK_PRESSURE: Node disk pressure error\n - ADDRESS_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - ADDRESS_NODE_PID_PRESSURE: Node PID pressure error\n - ADDRESS_NODE_UNSCHEDULABLE: Node unschedulable error\n - ADDRESS_NODE_UNREACHABLE: Node unreachable error\n - ADDRESS_NODE_NOT_READY: Node not ready error\n - ADDRESS_FAILED_SCHEDULING: Scheduler failure error\n - CHECK_HOST_CONNECTION: Cluster Connectivity error\n - START_MINIKUBE: Minikube is stopped: use `minikube start`\n - UNPAUSE_MINIKUBE: Minikube is paused: use `minikube unpause`\n - RUN_DOCKER_PULL: Run Docker pull for the image with v1 manifest and try again.\n - SET_RENDER_FLAG_OFFLINE_FALSE: Rerun with correct offline flag value.\n - KPTFILE_MANUAL_INIT: Manually run `kpt pkg init` or `kpt live init`\n - KPTFILE_CHECK_YAML: Check if the Kptfile is correct.\n - REMOVE_NAMESPACE_FROM_MANIFESTS: Remove namespace from manifests\n - CONFIG_CHECK_FILE_PATH: Check configuration file path\n - CONFIG_CHECK_DEPENDENCY_DEFINITION: Check dependency config definition\n - CONFIG_CHANGE_NAMES: Change config name to avoid duplicates\n - CONFIG_CHECK_FILTER: Check config filter\n - CONFIG_CHECK_PROFILE_DEFINITION: Check profile definition in current config\n - CONFIG_CHECK_DEPENDENCY_PROFILES_SELECTION: Check active profile selection for dependency config\n - CONFIG_CHECK_PROFILE_SELECTION: Check profile selection flag\n - CONFIG_FIX_API_VERSION: Fix config API version or upgrade the skaffold binary\n - CONFIG_ALLOWLIST_VALIDATORS: Only the allow listed validators are acceptable in skaffold-managed mode.\n - CONFIG_ALLOWLIST_transformers: Only the allow listed transformers are acceptable in skaffold-managed mode.\n - CONFIG_FIX_MISSING_MANIFEST_FILE: Check mising manifest file section of config and fix as needed.\n - CONFIG_ENABLE_REMOTE_REPO_SYNC: Enable remote repo sync, or clone manually\n - INSPECT_USE_MODIFY_OR_NEW_PROFILE: Create new build env in a profile instead, or use the 'modify' command\n - INSPECT_USE_ADD_BUILD_ENV: Check profile selection, or use the 'add' command instead\n - INSPECT_CHECK_INPUT_PROFILE: Check profile flag value\n - OPEN_ISSUE: Open an issue so this situation can be diagnosed\n - CHECK_CUSTOM_COMMAND: Test error suggestion codes" }, "enumsTesterType": { "type": "string", diff --git a/docs-v2/content/en/docs/references/api-v2/grpc.md b/docs-v2/content/en/docs/references/api-v2/grpc.md index 9ca6abbaa9f..baf9ed34dd7 100644 --- a/docs-v2/content/en/docs/references/api-v2/grpc.md +++ b/docs-v2/content/en/docs/references/api-v2/grpc.md @@ -1208,6 +1208,8 @@ For Cancelled Error code, use range 800 to 850.
| RENDER_KPTFILE_INIT_ERR | 1501 | Render errors The Kptfile cannot be created via `kpt pkg init`. | | RENDER_KPTFILE_INVALID_YAML_ERR | 1401 | The Kptfile is not a valid yaml file | | RENDER_KPTFILE_INVALID_SCHEMA_ERR | 1402 | The Kptfile is not a valid API schema | +| RENDER_SET_NAMESPACE_ERR | 1403 | Error setting namespace. | +| RENDER_NAMESPACE_ALREADY_SET_ERR | 1404 | Namespace is already set. | | CONFIG_FILE_PARSING_ERR | 1201 | Catch-all configuration file parsing error | | CONFIG_FILE_NOT_FOUND_ERR | 1202 | Main configuration file not found | | CONFIG_DEPENDENCY_NOT_FOUND_ERR | 1203 | Dependency configuration file not found | @@ -1288,6 +1290,7 @@ Enum for Suggestion codes | SET_RENDER_FLAG_OFFLINE_FALSE | 600 | Rerun with correct offline flag value. | | KPTFILE_MANUAL_INIT | 601 | Manually run `kpt pkg init` or `kpt live init` | | KPTFILE_CHECK_YAML | 602 | Check if the Kptfile is correct. | +| REMOVE_NAMESPACE_FROM_MANIFESTS | 603 | Remove namespace from manifests | | CONFIG_CHECK_FILE_PATH | 700 | Check configuration file path | | CONFIG_CHECK_DEPENDENCY_DEFINITION | 701 | Check dependency config definition | | CONFIG_CHANGE_NAMES | 702 | Change config name to avoid duplicates | diff --git a/docs-v2/content/en/docs/references/api/grpc.md b/docs-v2/content/en/docs/references/api/grpc.md index f8f576093b1..7cb31b6d86f 100644 --- a/docs-v2/content/en/docs/references/api/grpc.md +++ b/docs-v2/content/en/docs/references/api/grpc.md @@ -1063,6 +1063,8 @@ For Cancelled Error code, use range 800 to 850.
| RENDER_KPTFILE_INIT_ERR | 1501 | Render errors The Kptfile cannot be created via `kpt pkg init`. | | RENDER_KPTFILE_INVALID_YAML_ERR | 1401 | The Kptfile is not a valid yaml file | | RENDER_KPTFILE_INVALID_SCHEMA_ERR | 1402 | The Kptfile is not a valid API schema | +| RENDER_SET_NAMESPACE_ERR | 1403 | Error setting namespace. | +| RENDER_NAMESPACE_ALREADY_SET_ERR | 1404 | Namespace is already set. | | CONFIG_FILE_PARSING_ERR | 1201 | Catch-all configuration file parsing error | | CONFIG_FILE_NOT_FOUND_ERR | 1202 | Main configuration file not found | | CONFIG_DEPENDENCY_NOT_FOUND_ERR | 1203 | Dependency configuration file not found | @@ -1143,6 +1145,7 @@ Enum for Suggestion codes | SET_RENDER_FLAG_OFFLINE_FALSE | 600 | Rerun with correct offline flag value. | | KPTFILE_MANUAL_INIT | 601 | Manually run `kpt pkg init` or `kpt live init` | | KPTFILE_CHECK_YAML | 602 | Check if the Kptfile is correct. | +| REMOVE_NAMESPACE_FROM_MANIFESTS | 603 | Remove namespace from manifests | | CONFIG_CHECK_FILE_PATH | 700 | Check configuration file path | | CONFIG_CHECK_DEPENDENCY_DEFINITION | 701 | Check dependency config definition | | CONFIG_CHANGE_NAMES | 702 | Change config name to avoid duplicates | diff --git a/docs/content/en/api-v2/skaffold.swagger.json b/docs/content/en/api-v2/skaffold.swagger.json index d15129a66bd..9b919612838 100644 --- a/docs/content/en/api-v2/skaffold.swagger.json +++ b/docs/content/en/api-v2/skaffold.swagger.json @@ -501,6 +501,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -526,7 +528,7 @@ "PORT_FORWARD_RUN_PROXY_START_ERROR" ], "default": "OK", - "description": "Enum for Status codes
\nThese error codes are prepended by Phase Name e.g.\nINIT, BUILD, TEST, DEPLOY, STATUSCHECK, DEVINIT
\nFor Success Error codes, use range 200 to 250.
\nFor Unknown error codes, use range 500 to 600.
\nFor Cancelled Error code, use range 800 to 850.
\n- OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist" + "description": "Enum for Status codes
\nThese error codes are prepended by Phase Name e.g.\nINIT, BUILD, TEST, DEPLOY, STATUSCHECK, DEVINIT
\nFor Success Error codes, use range 200 to 250.
\nFor Unknown error codes, use range 500 to 600.
\nFor Cancelled Error code, use range 800 to 850.
\n- OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist" }, "enumsSuggestionCode": { "type": "string", @@ -578,6 +580,7 @@ "SET_RENDER_FLAG_OFFLINE_FALSE", "KPTFILE_MANUAL_INIT", "KPTFILE_CHECK_YAML", + "REMOVE_NAMESPACE_FROM_MANIFESTS", "CONFIG_CHECK_FILE_PATH", "CONFIG_CHECK_DEPENDENCY_DEFINITION", "CONFIG_CHANGE_NAMES", @@ -601,7 +604,7 @@ "CHECK_TEST_COMMAND_AND_IMAGE_NAME" ], "default": "NIL", - "description": "Enum for Suggestion codes\n- NIL: default nil suggestion.\nThis is usually set when no error happens.\n - ADD_DEFAULT_REPO: Add Default Repo\n - CHECK_DEFAULT_REPO: Verify Default Repo\n - CHECK_DEFAULT_REPO_GLOBAL_CONFIG: Verify default repo in the global config\n - GCLOUD_DOCKER_AUTH_CONFIGURE: run gcloud docker auth configure\n - DOCKER_AUTH_CONFIGURE: Run docker auth configure\n - CHECK_GCLOUD_PROJECT: Verify Gcloud Project\n - CHECK_DOCKER_RUNNING: Check if docker is running\n - FIX_USER_BUILD_ERR: Fix User Build Error\n - DOCKER_BUILD_RETRY: Docker build internal error, try again\n - FIX_CACHE_FROM_ARTIFACT_CONFIG: Fix `cacheFrom` config for given artifact and try again\n - FIX_SKAFFOLD_CONFIG_DOCKERFILE: Fix `dockerfile` config for a given artifact and try again.\n - FIX_JIB_PLUGIN_CONFIGURATION: Use a supported Jib plugin type\n - FIX_DOCKER_NETWORK_CONTAINER_NAME: Docker build network invalid docker container name (or id).\n - CHECK_DOCKER_NETWORK_CONTAINER_RUNNING: Docker build network container not existing in the current context.\n - FIX_DOCKER_NETWORK_MODE_WHEN_EXTRACTING_CONTAINER_NAME: Executing extractContainerNameFromNetworkMode with a non valid mode (only container mode allowed)\n - RUN_DOCKER_PRUNE: Prune Docker image\n - SET_CLEANUP_FLAG: Set Cleanup flag for skaffold command.\n - BUILD_FIX_UNKNOWN_PLATFORM_FLAG: Build platform error suggestion codes\n - CHECK_CLUSTER_CONNECTION: Check cluster connection\n - CHECK_MINIKUBE_STATUS: Check minikube status\n - INSTALL_HELM: Install helm tool\n - UPGRADE_HELM: Upgrade helm tool\n - FIX_SKAFFOLD_CONFIG_HELM_ARTIFACT_OVERRIDES: Fix helm `releases.artifactOverrides` config to match with `build.artifacts` (no longer used in Skaffold v2)\n - UPGRADE_HELM32: Upgrade helm version to v3.2.0 and higher.\n - FIX_SKAFFOLD_CONFIG_HELM_CREATE_NAMESPACE: Set `releases.createNamespace` to false.\n - INVALID_KPT_MANIFESTS: check the Kptfile validation.\n - ALIGN_KPT_INVENTORY: align the inventory info in kpt live apply.\n - INSTALL_KUBECTL: Install kubectl tool\n - CHECK_CONTAINER_LOGS: Container run error\n - CHECK_READINESS_PROBE: Pod Health check error\n - CHECK_CONTAINER_IMAGE: Check Container image\n - ADDRESS_NODE_MEMORY_PRESSURE: Node pressure error\n - ADDRESS_NODE_DISK_PRESSURE: Node disk pressure error\n - ADDRESS_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - ADDRESS_NODE_PID_PRESSURE: Node PID pressure error\n - ADDRESS_NODE_UNSCHEDULABLE: Node unschedulable error\n - ADDRESS_NODE_UNREACHABLE: Node unreachable error\n - ADDRESS_NODE_NOT_READY: Node not ready error\n - ADDRESS_FAILED_SCHEDULING: Scheduler failure error\n - CHECK_HOST_CONNECTION: Cluster Connectivity error\n - START_MINIKUBE: Minikube is stopped: use `minikube start`\n - UNPAUSE_MINIKUBE: Minikube is paused: use `minikube unpause`\n - RUN_DOCKER_PULL: Run Docker pull for the image with v1 manifest and try again.\n - SET_RENDER_FLAG_OFFLINE_FALSE: Rerun with correct offline flag value.\n - KPTFILE_MANUAL_INIT: Manually run `kpt pkg init` or `kpt live init`\n - KPTFILE_CHECK_YAML: Check if the Kptfile is correct.\n - CONFIG_CHECK_FILE_PATH: Check configuration file path\n - CONFIG_CHECK_DEPENDENCY_DEFINITION: Check dependency config definition\n - CONFIG_CHANGE_NAMES: Change config name to avoid duplicates\n - CONFIG_CHECK_FILTER: Check config filter\n - CONFIG_CHECK_PROFILE_DEFINITION: Check profile definition in current config\n - CONFIG_CHECK_DEPENDENCY_PROFILES_SELECTION: Check active profile selection for dependency config\n - CONFIG_CHECK_PROFILE_SELECTION: Check profile selection flag\n - CONFIG_FIX_API_VERSION: Fix config API version or upgrade the skaffold binary\n - CONFIG_ALLOWLIST_VALIDATORS: Only the allow listed validators are acceptable in skaffold-managed mode.\n - CONFIG_ALLOWLIST_transformers: Only the allow listed transformers are acceptable in skaffold-managed mode.\n - CONFIG_FIX_MISSING_MANIFEST_FILE: Check mising manifest file section of config and fix as needed.\n - CONFIG_ENABLE_REMOTE_REPO_SYNC: Enable remote repo sync, or clone manually\n - INSPECT_USE_MODIFY_OR_NEW_PROFILE: Create new build env in a profile instead, or use the 'modify' command\n - INSPECT_USE_ADD_BUILD_ENV: Check profile selection, or use the 'add' command instead\n - INSPECT_CHECK_INPUT_PROFILE: Check profile flag value\n - OPEN_ISSUE: Open an issue so this situation can be diagnosed\n - CHECK_CUSTOM_COMMAND: Test error suggestion codes" + "description": "Enum for Suggestion codes\n- NIL: default nil suggestion.\nThis is usually set when no error happens.\n - ADD_DEFAULT_REPO: Add Default Repo\n - CHECK_DEFAULT_REPO: Verify Default Repo\n - CHECK_DEFAULT_REPO_GLOBAL_CONFIG: Verify default repo in the global config\n - GCLOUD_DOCKER_AUTH_CONFIGURE: run gcloud docker auth configure\n - DOCKER_AUTH_CONFIGURE: Run docker auth configure\n - CHECK_GCLOUD_PROJECT: Verify Gcloud Project\n - CHECK_DOCKER_RUNNING: Check if docker is running\n - FIX_USER_BUILD_ERR: Fix User Build Error\n - DOCKER_BUILD_RETRY: Docker build internal error, try again\n - FIX_CACHE_FROM_ARTIFACT_CONFIG: Fix `cacheFrom` config for given artifact and try again\n - FIX_SKAFFOLD_CONFIG_DOCKERFILE: Fix `dockerfile` config for a given artifact and try again.\n - FIX_JIB_PLUGIN_CONFIGURATION: Use a supported Jib plugin type\n - FIX_DOCKER_NETWORK_CONTAINER_NAME: Docker build network invalid docker container name (or id).\n - CHECK_DOCKER_NETWORK_CONTAINER_RUNNING: Docker build network container not existing in the current context.\n - FIX_DOCKER_NETWORK_MODE_WHEN_EXTRACTING_CONTAINER_NAME: Executing extractContainerNameFromNetworkMode with a non valid mode (only container mode allowed)\n - RUN_DOCKER_PRUNE: Prune Docker image\n - SET_CLEANUP_FLAG: Set Cleanup flag for skaffold command.\n - BUILD_FIX_UNKNOWN_PLATFORM_FLAG: Build platform error suggestion codes\n - CHECK_CLUSTER_CONNECTION: Check cluster connection\n - CHECK_MINIKUBE_STATUS: Check minikube status\n - INSTALL_HELM: Install helm tool\n - UPGRADE_HELM: Upgrade helm tool\n - FIX_SKAFFOLD_CONFIG_HELM_ARTIFACT_OVERRIDES: Fix helm `releases.artifactOverrides` config to match with `build.artifacts` (no longer used in Skaffold v2)\n - UPGRADE_HELM32: Upgrade helm version to v3.2.0 and higher.\n - FIX_SKAFFOLD_CONFIG_HELM_CREATE_NAMESPACE: Set `releases.createNamespace` to false.\n - INVALID_KPT_MANIFESTS: check the Kptfile validation.\n - ALIGN_KPT_INVENTORY: align the inventory info in kpt live apply.\n - INSTALL_KUBECTL: Install kubectl tool\n - CHECK_CONTAINER_LOGS: Container run error\n - CHECK_READINESS_PROBE: Pod Health check error\n - CHECK_CONTAINER_IMAGE: Check Container image\n - ADDRESS_NODE_MEMORY_PRESSURE: Node pressure error\n - ADDRESS_NODE_DISK_PRESSURE: Node disk pressure error\n - ADDRESS_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - ADDRESS_NODE_PID_PRESSURE: Node PID pressure error\n - ADDRESS_NODE_UNSCHEDULABLE: Node unschedulable error\n - ADDRESS_NODE_UNREACHABLE: Node unreachable error\n - ADDRESS_NODE_NOT_READY: Node not ready error\n - ADDRESS_FAILED_SCHEDULING: Scheduler failure error\n - CHECK_HOST_CONNECTION: Cluster Connectivity error\n - START_MINIKUBE: Minikube is stopped: use `minikube start`\n - UNPAUSE_MINIKUBE: Minikube is paused: use `minikube unpause`\n - RUN_DOCKER_PULL: Run Docker pull for the image with v1 manifest and try again.\n - SET_RENDER_FLAG_OFFLINE_FALSE: Rerun with correct offline flag value.\n - KPTFILE_MANUAL_INIT: Manually run `kpt pkg init` or `kpt live init`\n - KPTFILE_CHECK_YAML: Check if the Kptfile is correct.\n - REMOVE_NAMESPACE_FROM_MANIFESTS: Remove namespace from manifests\n - CONFIG_CHECK_FILE_PATH: Check configuration file path\n - CONFIG_CHECK_DEPENDENCY_DEFINITION: Check dependency config definition\n - CONFIG_CHANGE_NAMES: Change config name to avoid duplicates\n - CONFIG_CHECK_FILTER: Check config filter\n - CONFIG_CHECK_PROFILE_DEFINITION: Check profile definition in current config\n - CONFIG_CHECK_DEPENDENCY_PROFILES_SELECTION: Check active profile selection for dependency config\n - CONFIG_CHECK_PROFILE_SELECTION: Check profile selection flag\n - CONFIG_FIX_API_VERSION: Fix config API version or upgrade the skaffold binary\n - CONFIG_ALLOWLIST_VALIDATORS: Only the allow listed validators are acceptable in skaffold-managed mode.\n - CONFIG_ALLOWLIST_transformers: Only the allow listed transformers are acceptable in skaffold-managed mode.\n - CONFIG_FIX_MISSING_MANIFEST_FILE: Check mising manifest file section of config and fix as needed.\n - CONFIG_ENABLE_REMOTE_REPO_SYNC: Enable remote repo sync, or clone manually\n - INSPECT_USE_MODIFY_OR_NEW_PROFILE: Create new build env in a profile instead, or use the 'modify' command\n - INSPECT_USE_ADD_BUILD_ENV: Check profile selection, or use the 'add' command instead\n - INSPECT_CHECK_INPUT_PROFILE: Check profile flag value\n - OPEN_ISSUE: Open an issue so this situation can be diagnosed\n - CHECK_CUSTOM_COMMAND: Test error suggestion codes" }, "enumsTesterType": { "type": "string", diff --git a/docs/content/en/api/skaffold.swagger.json b/docs/content/en/api/skaffold.swagger.json index a6a534532f8..5b9356837fb 100644 --- a/docs/content/en/api/skaffold.swagger.json +++ b/docs/content/en/api/skaffold.swagger.json @@ -151,7 +151,7 @@ }, { "name": "event.buildEvent.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -322,6 +322,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -350,7 +352,7 @@ }, { "name": "event.buildEvent.actionableErr.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -521,6 +523,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -579,7 +583,7 @@ }, { "name": "event.deployEvent.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -750,6 +754,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -778,7 +784,7 @@ }, { "name": "event.deployEvent.actionableErr.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -949,6 +955,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -1077,7 +1085,7 @@ }, { "name": "event.statusCheckEvent.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -1248,6 +1256,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -1276,7 +1286,7 @@ }, { "name": "event.statusCheckEvent.actionableErr.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -1447,6 +1457,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -1505,7 +1517,7 @@ }, { "name": "event.resourceStatusCheckEvent.statusCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -1676,6 +1688,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -1704,7 +1718,7 @@ }, { "name": "event.resourceStatusCheckEvent.actionableErr.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -1875,6 +1889,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -1934,7 +1950,7 @@ }, { "name": "event.fileSyncEvent.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -2105,6 +2121,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -2133,7 +2151,7 @@ }, { "name": "event.fileSyncEvent.actionableErr.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -2304,6 +2322,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -2393,7 +2413,7 @@ }, { "name": "event.devLoopEvent.err.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -2564,6 +2584,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -2604,7 +2626,7 @@ }, { "name": "event.terminationEvent.err.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -2775,6 +2797,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -2815,7 +2839,7 @@ }, { "name": "event.TestEvent.actionableErr.errCode", - "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", + "description": " - OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist", "in": "query", "required": false, "type": "string", @@ -2986,6 +3010,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -3401,6 +3427,8 @@ "RENDER_KPTFILE_INIT_ERR", "RENDER_KPTFILE_INVALID_YAML_ERR", "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + "RENDER_SET_NAMESPACE_ERR", + "RENDER_NAMESPACE_ALREADY_SET_ERR", "CONFIG_FILE_PARSING_ERR", "CONFIG_FILE_NOT_FOUND_ERR", "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -3426,7 +3454,7 @@ "PORT_FORWARD_RUN_PROXY_START_ERROR" ], "default": "OK", - "description": "Enum for Status codes
\nThese error codes are prepended by Phase Name e.g.\nINIT, BUILD, TEST, DEPLOY, STATUSCHECK, DEVINIT
\nFor Success Error codes, use range 200 to 250.
\nFor Unknown error codes, use range 500 to 600.
\nFor Cancelled Error code, use range 800 to 850.
\n- OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist" + "description": "Enum for Status codes
\nThese error codes are prepended by Phase Name e.g.\nINIT, BUILD, TEST, DEPLOY, STATUSCHECK, DEVINIT
\nFor Success Error codes, use range 200 to 250.
\nFor Unknown error codes, use range 500 to 600.
\nFor Cancelled Error code, use range 800 to 850.
\n- OK: A default status code for events that do not have an associated phase.\nTypically seen with the DevEndEvent event on success.\n - STATUSCHECK_SUCCESS: Status Check Success\n - BUILD_SUCCESS: Build Success\n - RENDER_SUCCESS: Render Success\n - DEPLOY_SUCCESS: Deploy Success\n - TEST_SUCCESS: Test Success\n - BUILD_PUSH_ACCESS_DENIED: Build error due to push access denied\n - BUILD_PROJECT_NOT_FOUND: Build error due to GCP project not found.\n - BUILD_DOCKER_DAEMON_NOT_RUNNING: Docker build error due to docker daemon not running\n - BUILD_USER_ERROR: Build error due to user application code, e.g. compilation error, dockerfile error etc\n - BUILD_DOCKER_UNAVAILABLE: Build error due to docker not available\n - BUILD_DOCKER_UNAUTHORIZED: Docker build error due to user not authorized to perform the action\n - BUILD_DOCKER_SYSTEM_ERR: Docker system build error\n - BUILD_DOCKER_NOT_MODIFIED_ERR: Docker build error due to Docker build container is already in the desired state\n - BUILD_DOCKER_NOT_IMPLEMENTED_ERR: Docker build error indicating a feature not supported\n - BUILD_DOCKER_DATA_LOSS_ERR: Docker build error indicates that for given build, data was lost or there is data corruption\n - BUILD_DOCKER_FORBIDDEN_ERR: Docker build error indicates user is forbidden to perform the build or step/action.\n - BUILD_DOCKER_CONFLICT_ERR: Docker build error due to some internal error and docker container state conflicts with the requested action and can't be performed\n - BUILD_DOCKER_ERROR_NOT_FOUND: Docker build error indicates the requested object does not exist\n - BUILD_DOCKER_INVALID_PARAM_ERR: Docker build error indication invalid parameter sent to docker command\n - BUILD_DOCKERFILE_NOT_FOUND: Docker build failed due to dockerfile not found\n - BUILD_DOCKER_CACHE_FROM_PULL_ERR: Docker build failed due `cacheFrom` user config error\n - BUILD_DOCKER_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from docker daemon.\n - BUILD_DOCKER_NO_SPACE_ERR: Build error due no space left in docker.\n - BUILD_REGISTRY_GET_DIGEST_ERR: Build error due to digest for built artifact could not be retrieved from registry.\n - BUILD_UNKNOWN_JIB_PLUGIN_TYPE: Build error indicating unknown Jib plugin type. Should be one of [maven, gradle]\n - BUILD_JIB_GRADLE_DEP_ERR: Build error determining dependency for jib gradle project.\n - BUILD_JIB_MAVEN_DEP_ERR: Build error determining dependency for jib gradle project.\n - INIT_DOCKER_NETWORK_LISTING_CONTAINERS: Docker build error when listing containers.\n - INIT_DOCKER_NETWORK_INVALID_CONTAINER_NAME: Docker build error indicating an invalid container name (or id).\n - INIT_DOCKER_NETWORK_CONTAINER_DOES_NOT_EXIST: Docker build error indicating the container referenced does not exists in the docker context used.\n - INIT_DOCKER_NETWORK_INVALID_MODE: Docker Network invalid mode\n - INIT_DOCKER_NETWORK_PARSE_ERR: Error parsing Docker Network mode\n - BUILD_GCB_CREATE_BUILD_ERR: GCB Create Build Error\n - BUILD_GCB_GET_BUILD_ID_ERR: GCB error indicating an error to fetch build id.\n - BUILD_GCB_GET_BUILD_STATUS_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILD_LOG_ERR: GCB error indicating an error to fetch build logs.\n - BUILD_GCB_COPY_BUILD_LOG_ERR: GCB error indicating an error to fetch build status.\n - BUILD_GCB_GET_BUILT_IMAGE_ERR: GCB error indicating an error retrieving the built image id.\n - BUILD_GCB_BUILD_FAILED: GCB error indicating build failure.\n - BUILD_GCB_BUILD_INTERNAL_ERR: GCB error indicating build failure due to internal errror.\n - BUILD_GCB_BUILD_TIMEOUT: GCB error indicating build failure due to timeout.\n - BUILD_GCB_GENERATE_BUILD_DESCRIPTOR_ERR: GCB error to generate the build descriptor.\n - BUILD_GCB_UPLOAD_TO_GCS_ERR: GCB error to upload to GCS.\n - BUILD_GCB_JIB_DEPENDENCY_ERR: GCB error to fetch jib artifact dependency.\n - BUILD_GCB_GET_DEPENDENCY_ERR: GCB error to fetch artifact dependency.\n - BUILD_GCB_GET_GCS_BUCKET_ERR: GCB error to get GCS bucket.\n - BUILD_GCB_CREATE_BUCKET_ERR: GCB error to create a GCS bucket.\n - BUILD_GCB_EXTRACT_PROJECT_ID: GCB error to extract Project ID.\n - BUILD_GET_CLOUD_STORAGE_CLIENT_ERR: GCB error to get cloud storage client to perform GCS operation.\n - BUILD_GET_CLOUD_BUILD_CLIENT_ERR: GCB error to get cloud build client to perform GCB operations.\n - BUILD_UNKNOWN_PLATFORM_FLAG: Value provided to --platform flag cannot be parsed\n - STATUSCHECK_IMAGE_PULL_ERR: Container image pull error\n - STATUSCHECK_CONTAINER_CREATING: Container creating error\n - STATUSCHECK_RUN_CONTAINER_ERR: Container run error\n - STATUSCHECK_CONTAINER_TERMINATED: Container is already terminated\n - STATUSCHECK_DEPLOYMENT_ROLLOUT_PENDING: Deployment waiting for rollout\n - STATUSCHECK_STANDALONE_PODS_PENDING: Standalone pods pending to stabilize\n - STATUSCHECK_CONTAINER_RESTARTING: Container restarting error\n - STATUSCHECK_UNHEALTHY: Readiness probe failed\n - STATUSCHECK_CONTAINER_EXEC_ERROR: Executable binary format error\n - STATUSCHECK_NODE_MEMORY_PRESSURE: Node memory pressure error\n - STATUSCHECK_NODE_DISK_PRESSURE: Node disk pressure error\n - STATUSCHECK_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - STATUSCHECK_NODE_PID_PRESSURE: Node PID pressure error\n - STATUSCHECK_NODE_UNSCHEDULABLE: Node unschedulable error\n - STATUSCHECK_NODE_UNREACHABLE: Node unreachable error\n - STATUSCHECK_NODE_NOT_READY: Node not ready error\n - STATUSCHECK_FAILED_SCHEDULING: Scheduler failure error\n - STATUSCHECK_KUBECTL_CONNECTION_ERR: Kubectl connection error\n - STATUSCHECK_KUBECTL_PID_KILLED: Kubectl process killed error\n - STATUSCHECK_KUBECTL_CLIENT_FETCH_ERR: Kubectl client fetch err\n - STATUSCHECK_POD_INITIALIZING: Pod Initializing\n - STATUSCHECK_CONFIG_CONNECTOR_IN_PROGRESS: The actual state of the resource has not yet reached the desired state\n - STATUSCHECK_CONFIG_CONNECTOR_FAILED: The process of reconciling the actual state with the desired state has encountered an error\n - STATUSCHECK_CONFIG_CONNECTOR_TERMINATING: The resource is in the process of being deleted\n - STATUSCHECK_CONFIG_CONNECTOR_NOT_FOUND: The resource does not exist\n - UNKNOWN_ERROR: Could not determine error and phase\n - STATUSCHECK_UNKNOWN: Status Check error unknown\n - STATUSCHECK_UNKNOWN_UNSCHEDULABLE: Container is unschedulable due to unknown reasons\n - STATUSCHECK_CONTAINER_WAITING_UNKNOWN: Container is waiting due to unknown reason\n - STATUSCHECK_UNKNOWN_EVENT: Container event reason unknown\n - STATUSCHECK_INTERNAL_ERROR: Status Check internal error\n - DEPLOY_UNKNOWN: Deploy failed due to unknown reason\n - SYNC_UNKNOWN: SYNC failed due to known reason\n - BUILD_UNKNOWN: Build failed due to unknown reason\n - DEVINIT_UNKNOWN: Dev Init failed due to unknown reason\n - CLEANUP_UNKNOWN: Cleanup failed due to unknown reason\n - INIT_UNKNOWN: Initialization of the Skaffold session failed due to unknown reason(s)\n - BUILD_DOCKER_UNKNOWN: Build failed due to docker unknown error\n - TEST_UNKNOWN: Test failed due to unknown reason\n - BUILD_GCB_BUILD_UNKNOWN_STATUS: GCB error indicating build failed due to unknown status.\n - SYNC_INIT_ERROR: File Sync Initialize failure\n - DEVINIT_REGISTER_BUILD_DEPS: Failed to configure watcher for build dependencies in dev loop\n - DEVINIT_REGISTER_TEST_DEPS: Failed to configure watcher for test dependencies in dev loop\n - DEVINIT_REGISTER_DEPLOY_DEPS: Failed to configure watcher for deploy dependencies in dev loop\n - DEVINIT_REGISTER_CONFIG_DEP: Failed to configure watcher for Skaffold configuration file.\n - DEVINIT_UNSUPPORTED_V1_MANIFEST: Failed to configure watcher for build dependencies for a base image with v1 manifest.\n - DEVINIT_REGISTER_RENDER_DEPS: Failed to configure watcher for render dependencies in dev loop\n - STATUSCHECK_USER_CANCELLED: User cancelled the skaffold dev run\n - STATUSCHECK_DEADLINE_EXCEEDED: Deadline for status check exceeded\n - BUILD_CANCELLED: Build Cancelled\n - DEPLOY_CANCELLED: Deploy cancelled due to user cancellation or one or more deployers failed.\n - BUILD_DOCKER_CANCELLED: Docker build cancelled.\n - BUILD_DOCKER_DEADLINE: Build error due to docker deadline was reached before the docker action completed\n - BUILD_GCB_BUILD_CANCELLED: GCB Build cancelled.\n - INIT_CREATE_TAGGER_ERROR: Skaffold was unable to create the configured tagger\n - INIT_MINIKUBE_PAUSED_ERROR: Skaffold was unable to start as Minikube appears to be paused\n - INIT_MINIKUBE_NOT_RUNNING_ERROR: Skaffold was unable to start as Minikube appears to be stopped\n - INIT_CREATE_BUILDER_ERROR: Skaffold was unable to create a configured image builder\n - INIT_CREATE_DEPLOYER_ERROR: Skaffold was unable to create a configured deployer\n - INIT_CREATE_TEST_DEP_ERROR: Skaffold was unable to create a configured test\n - INIT_CACHE_ERROR: Skaffold encountered an error validating the artifact cache\n - INIT_CREATE_WATCH_TRIGGER_ERROR: Skaffold encountered an error when configuring file watching\n - INIT_CREATE_ARTIFACT_DEP_ERROR: Skaffold encountered an error when evaluating artifact dependencies\n - DEPLOY_CLUSTER_CONNECTION_ERR: Unable to connect to cluster\n - DEPLOY_DEBUG_HELPER_RETRIEVE_ERR: Could not retrieve debug helpers.\n - DEPLOY_CLEANUP_ERR: Deploy clean up error\n - DEPLOY_HELM_APPLY_LABELS: Unable to apply helm labels.\n - DEPLOY_HELM_USER_ERR: Deploy error due to user deploy config for helm deployer\n - DEPLOY_NO_MATCHING_BUILD: An image was referenced with no matching build result\n - DEPLOY_HELM_VERSION_ERR: Unable to get helm client version\n - DEPLOY_HELM_MIN_VERSION_ERR: Helm version not supported.\n - DEPLOY_KUBECTL_VERSION_ERR: Unable to retrieve kubectl version\n - DEPLOY_KUBECTL_OFFLINE_MODE_ERR: User specified offline mode for rendering but remote manifests presents.\n - DEPLOY_ERR_WAITING_FOR_DELETION: Error waiting for previous version deletion before next version is active.\n - DEPLOY_READ_MANIFEST_ERR: Error reading manifests\n - DEPLOY_READ_REMOTE_MANIFEST_ERR: Error reading remote manifests\n - DEPLOY_LIST_MANIFEST_ERR: Errors listing manifests\n - DEPLOY_KUBECTL_USER_ERR: Deploy error due to user deploy config for kubectl deployer\n - DEPLOY_KUSTOMIZE_USER_ERR: Deploy error due to user deploy config for kustomize deployer\n - DEPLOY_REPLACE_IMAGE_ERR: Error replacing a built artifact in the manifests\n - DEPLOY_TRANSFORM_MANIFEST_ERR: Error transforming a manifest during skaffold debug\n - DEPLOY_SET_LABEL_ERR: Error setting user specified additional labels.\n - DEPLOY_MANIFEST_WRITE_ERR: Error writing hydrated kubernetes manifests.\n - DEPLOY_PARSE_MANIFEST_IMAGES_ERR: Error getting images from a kubernetes manifest.\n - DEPLOY_HELM_CREATE_NS_NOT_AVAILABLE: Helm config `createNamespace` not available\n - DEPLOY_CLUSTER_INTERNAL_SYSTEM_ERR: Kubernetes cluster reported an internal system error\n - DEPLOY_KPTFILE_INIT_ERR: The Kptfile cannot be created via `kpt live init`.\n - DEPLOY_KPT_SOURCE_ERR: The `kpt fn source` cannot read the given manifests.\n - DEPLOY_KPTFILE_INVALID_YAML_ERR: The Kptfile exists but cannot be opened or parsed.\n - DEPLOY_KPT_APPLY_ERR: kpt fails to live apply the manifests to the cluster.\n - DEPLOY_GET_CLOUD_RUN_CLIENT_ERR: The Cloud Run Client could not be created\n - DEPLOY_CLOUD_RUN_GET_SERVICE_ERR: The Cloud Run Client could not get details about the service.\n - DEPLOY_CLOUD_RUN_UPDATE_SERVICE_ERR: The Cloud Run Client was unable to update the service.\n - DEPLOY_CLOUD_RUN_DELETE_SERVICE_ERR: The Cloud Run Client was unable to delete the service.\n - TEST_USER_CONFIG_ERR: Error expanding paths\n - TEST_CST_USER_ERR: Error running container-structure-test\n - TEST_IMG_PULL_ERR: Unable to docker pull image\n - TEST_CUSTOM_CMD_PARSE_ERR: Unable to parse test command\n - TEST_CUSTOM_CMD_RUN_NON_ZERO_EXIT_ERR: Command returned non-zero exit code\n - TEST_CUSTOM_CMD_RUN_TIMEDOUT_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_CANCELLED_ERR: command cancelled or timed out\n - TEST_CUSTOM_CMD_RUN_EXECUTION_ERR: command context error\n - TEST_CUSTOM_CMD_RUN_EXITED_ERR: command exited\n - TEST_CUSTOM_CMD_RUN_ERR: error running cmd\n - TEST_CUSTOM_DEPENDENCIES_CMD_ERR: Error getting dependencies from command\n - TEST_CUSTOM_DEPENDENCIES_UNMARSHALL_ERR: Unmarshalling dependency output error\n - TEST_CUSTOM_CMD_RETRIEVE_ERR: Error retrieving the command\n - RENDER_KPTFILE_INIT_ERR: Render errors\nThe Kptfile cannot be created via `kpt pkg init`.\n - RENDER_KPTFILE_INVALID_YAML_ERR: The Kptfile is not a valid yaml file\n - RENDER_KPTFILE_INVALID_SCHEMA_ERR: The Kptfile is not a valid API schema\n - RENDER_SET_NAMESPACE_ERR: Error setting namespace.\n - RENDER_NAMESPACE_ALREADY_SET_ERR: Namespace is already set.\n - CONFIG_FILE_PARSING_ERR: Catch-all configuration file parsing error\n - CONFIG_FILE_NOT_FOUND_ERR: Main configuration file not found\n - CONFIG_DEPENDENCY_NOT_FOUND_ERR: Dependency configuration file not found\n - CONFIG_DUPLICATE_NAMES_SAME_FILE_ERR: Duplicate config names in the same configuration file\n - CONFIG_DUPLICATE_NAMES_ACROSS_FILES_ERR: Duplicate config names in two configuration files\n - CONFIG_BAD_FILTER_ERR: No configs matching configs filter\n - CONFIG_ZERO_FOUND_ERR: No configs parsed from current file\n - CONFIG_APPLY_PROFILES_ERR: Failed to apply profiles to config\n - CONFIG_DEFAULT_VALUES_ERR: Failed to set default config values\n - CONFIG_FILE_PATHS_SUBSTITUTION_ERR: Failed to substitute absolute file paths in config\n - CONFIG_MULTI_IMPORT_PROFILE_CONFLICT_ERR: Same config imported at least twice with different set of profiles\n - CONFIG_PROFILES_NOT_FOUND_ERR: Profile selection did not match known profile names\n - CONFIG_UNKNOWN_API_VERSION_ERR: Config API version not found\n - CONFIG_UNKNOWN_VALIDATOR: The validator is not allowed in skaffold-managed mode.\n - CONFIG_UNKNOWN_TRANSFORMER: The transformer is not allowed in skaffold-managed mode.\n - CONFIG_MISSING_MANIFEST_FILE_ERR: Manifest file not found\n - CONFIG_REMOTE_REPO_CACHE_NOT_FOUND_ERR: Remote config repository cache not found and sync disabled\n - INSPECT_UNKNOWN_ERR: Catch-all `skaffold inspect` command error\n - INSPECT_BUILD_ENV_ALREADY_EXISTS_ERR: Trying to add new build environment that already exists\n - INSPECT_BUILD_ENV_INCORRECT_TYPE_ERR: Trying to modify build environment that doesn't exist\n - INSPECT_PROFILE_NOT_FOUND_ERR: Trying to modify a profile that doesn't exist" }, "enumsSuggestionCode": { "type": "string", @@ -3478,6 +3506,7 @@ "SET_RENDER_FLAG_OFFLINE_FALSE", "KPTFILE_MANUAL_INIT", "KPTFILE_CHECK_YAML", + "REMOVE_NAMESPACE_FROM_MANIFESTS", "CONFIG_CHECK_FILE_PATH", "CONFIG_CHECK_DEPENDENCY_DEFINITION", "CONFIG_CHANGE_NAMES", @@ -3501,7 +3530,7 @@ "CHECK_TEST_COMMAND_AND_IMAGE_NAME" ], "default": "NIL", - "description": "Enum for Suggestion codes\n- NIL: default nil suggestion.\nThis is usually set when no error happens.\n - ADD_DEFAULT_REPO: Add Default Repo\n - CHECK_DEFAULT_REPO: Verify Default Repo\n - CHECK_DEFAULT_REPO_GLOBAL_CONFIG: Verify default repo in the global config\n - GCLOUD_DOCKER_AUTH_CONFIGURE: run gcloud docker auth configure\n - DOCKER_AUTH_CONFIGURE: Run docker auth configure\n - CHECK_GCLOUD_PROJECT: Verify Gcloud Project\n - CHECK_DOCKER_RUNNING: Check if docker is running\n - FIX_USER_BUILD_ERR: Fix User Build Error\n - DOCKER_BUILD_RETRY: Docker build internal error, try again\n - FIX_CACHE_FROM_ARTIFACT_CONFIG: Fix `cacheFrom` config for given artifact and try again\n - FIX_SKAFFOLD_CONFIG_DOCKERFILE: Fix `dockerfile` config for a given artifact and try again.\n - FIX_JIB_PLUGIN_CONFIGURATION: Use a supported Jib plugin type\n - FIX_DOCKER_NETWORK_CONTAINER_NAME: Docker build network invalid docker container name (or id).\n - CHECK_DOCKER_NETWORK_CONTAINER_RUNNING: Docker build network container not existing in the current context.\n - FIX_DOCKER_NETWORK_MODE_WHEN_EXTRACTING_CONTAINER_NAME: Executing extractContainerNameFromNetworkMode with a non valid mode (only container mode allowed)\n - RUN_DOCKER_PRUNE: Prune Docker image\n - SET_CLEANUP_FLAG: Set Cleanup flag for skaffold command.\n - BUILD_FIX_UNKNOWN_PLATFORM_FLAG: Build platform error suggestion codes\n - CHECK_CLUSTER_CONNECTION: Check cluster connection\n - CHECK_MINIKUBE_STATUS: Check minikube status\n - INSTALL_HELM: Install helm tool\n - UPGRADE_HELM: Upgrade helm tool\n - FIX_SKAFFOLD_CONFIG_HELM_ARTIFACT_OVERRIDES: Fix helm `releases.artifactOverrides` config to match with `build.artifacts` (no longer used in Skaffold v2)\n - UPGRADE_HELM32: Upgrade helm version to v3.2.0 and higher.\n - FIX_SKAFFOLD_CONFIG_HELM_CREATE_NAMESPACE: Set `releases.createNamespace` to false.\n - INVALID_KPT_MANIFESTS: check the Kptfile validation.\n - ALIGN_KPT_INVENTORY: align the inventory info in kpt live apply.\n - INSTALL_KUBECTL: Install kubectl tool\n - CHECK_CONTAINER_LOGS: Container run error\n - CHECK_READINESS_PROBE: Pod Health check error\n - CHECK_CONTAINER_IMAGE: Check Container image\n - ADDRESS_NODE_MEMORY_PRESSURE: Node pressure error\n - ADDRESS_NODE_DISK_PRESSURE: Node disk pressure error\n - ADDRESS_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - ADDRESS_NODE_PID_PRESSURE: Node PID pressure error\n - ADDRESS_NODE_UNSCHEDULABLE: Node unschedulable error\n - ADDRESS_NODE_UNREACHABLE: Node unreachable error\n - ADDRESS_NODE_NOT_READY: Node not ready error\n - ADDRESS_FAILED_SCHEDULING: Scheduler failure error\n - CHECK_HOST_CONNECTION: Cluster Connectivity error\n - START_MINIKUBE: Minikube is stopped: use `minikube start`\n - UNPAUSE_MINIKUBE: Minikube is paused: use `minikube unpause`\n - RUN_DOCKER_PULL: Run Docker pull for the image with v1 manifest and try again.\n - SET_RENDER_FLAG_OFFLINE_FALSE: Rerun with correct offline flag value.\n - KPTFILE_MANUAL_INIT: Manually run `kpt pkg init` or `kpt live init`\n - KPTFILE_CHECK_YAML: Check if the Kptfile is correct.\n - CONFIG_CHECK_FILE_PATH: Check configuration file path\n - CONFIG_CHECK_DEPENDENCY_DEFINITION: Check dependency config definition\n - CONFIG_CHANGE_NAMES: Change config name to avoid duplicates\n - CONFIG_CHECK_FILTER: Check config filter\n - CONFIG_CHECK_PROFILE_DEFINITION: Check profile definition in current config\n - CONFIG_CHECK_DEPENDENCY_PROFILES_SELECTION: Check active profile selection for dependency config\n - CONFIG_CHECK_PROFILE_SELECTION: Check profile selection flag\n - CONFIG_FIX_API_VERSION: Fix config API version or upgrade the skaffold binary\n - CONFIG_ALLOWLIST_VALIDATORS: Only the allow listed validators are acceptable in skaffold-managed mode.\n - CONFIG_ALLOWLIST_transformers: Only the allow listed transformers are acceptable in skaffold-managed mode.\n - CONFIG_FIX_MISSING_MANIFEST_FILE: Check mising manifest file section of config and fix as needed.\n - CONFIG_ENABLE_REMOTE_REPO_SYNC: Enable remote repo sync, or clone manually\n - INSPECT_USE_MODIFY_OR_NEW_PROFILE: Create new build env in a profile instead, or use the 'modify' command\n - INSPECT_USE_ADD_BUILD_ENV: Check profile selection, or use the 'add' command instead\n - INSPECT_CHECK_INPUT_PROFILE: Check profile flag value\n - OPEN_ISSUE: Open an issue so this situation can be diagnosed\n - CHECK_CUSTOM_COMMAND: Test error suggestion codes" + "description": "Enum for Suggestion codes\n- NIL: default nil suggestion.\nThis is usually set when no error happens.\n - ADD_DEFAULT_REPO: Add Default Repo\n - CHECK_DEFAULT_REPO: Verify Default Repo\n - CHECK_DEFAULT_REPO_GLOBAL_CONFIG: Verify default repo in the global config\n - GCLOUD_DOCKER_AUTH_CONFIGURE: run gcloud docker auth configure\n - DOCKER_AUTH_CONFIGURE: Run docker auth configure\n - CHECK_GCLOUD_PROJECT: Verify Gcloud Project\n - CHECK_DOCKER_RUNNING: Check if docker is running\n - FIX_USER_BUILD_ERR: Fix User Build Error\n - DOCKER_BUILD_RETRY: Docker build internal error, try again\n - FIX_CACHE_FROM_ARTIFACT_CONFIG: Fix `cacheFrom` config for given artifact and try again\n - FIX_SKAFFOLD_CONFIG_DOCKERFILE: Fix `dockerfile` config for a given artifact and try again.\n - FIX_JIB_PLUGIN_CONFIGURATION: Use a supported Jib plugin type\n - FIX_DOCKER_NETWORK_CONTAINER_NAME: Docker build network invalid docker container name (or id).\n - CHECK_DOCKER_NETWORK_CONTAINER_RUNNING: Docker build network container not existing in the current context.\n - FIX_DOCKER_NETWORK_MODE_WHEN_EXTRACTING_CONTAINER_NAME: Executing extractContainerNameFromNetworkMode with a non valid mode (only container mode allowed)\n - RUN_DOCKER_PRUNE: Prune Docker image\n - SET_CLEANUP_FLAG: Set Cleanup flag for skaffold command.\n - BUILD_FIX_UNKNOWN_PLATFORM_FLAG: Build platform error suggestion codes\n - CHECK_CLUSTER_CONNECTION: Check cluster connection\n - CHECK_MINIKUBE_STATUS: Check minikube status\n - INSTALL_HELM: Install helm tool\n - UPGRADE_HELM: Upgrade helm tool\n - FIX_SKAFFOLD_CONFIG_HELM_ARTIFACT_OVERRIDES: Fix helm `releases.artifactOverrides` config to match with `build.artifacts` (no longer used in Skaffold v2)\n - UPGRADE_HELM32: Upgrade helm version to v3.2.0 and higher.\n - FIX_SKAFFOLD_CONFIG_HELM_CREATE_NAMESPACE: Set `releases.createNamespace` to false.\n - INVALID_KPT_MANIFESTS: check the Kptfile validation.\n - ALIGN_KPT_INVENTORY: align the inventory info in kpt live apply.\n - INSTALL_KUBECTL: Install kubectl tool\n - CHECK_CONTAINER_LOGS: Container run error\n - CHECK_READINESS_PROBE: Pod Health check error\n - CHECK_CONTAINER_IMAGE: Check Container image\n - ADDRESS_NODE_MEMORY_PRESSURE: Node pressure error\n - ADDRESS_NODE_DISK_PRESSURE: Node disk pressure error\n - ADDRESS_NODE_NETWORK_UNAVAILABLE: Node network unavailable error\n - ADDRESS_NODE_PID_PRESSURE: Node PID pressure error\n - ADDRESS_NODE_UNSCHEDULABLE: Node unschedulable error\n - ADDRESS_NODE_UNREACHABLE: Node unreachable error\n - ADDRESS_NODE_NOT_READY: Node not ready error\n - ADDRESS_FAILED_SCHEDULING: Scheduler failure error\n - CHECK_HOST_CONNECTION: Cluster Connectivity error\n - START_MINIKUBE: Minikube is stopped: use `minikube start`\n - UNPAUSE_MINIKUBE: Minikube is paused: use `minikube unpause`\n - RUN_DOCKER_PULL: Run Docker pull for the image with v1 manifest and try again.\n - SET_RENDER_FLAG_OFFLINE_FALSE: Rerun with correct offline flag value.\n - KPTFILE_MANUAL_INIT: Manually run `kpt pkg init` or `kpt live init`\n - KPTFILE_CHECK_YAML: Check if the Kptfile is correct.\n - REMOVE_NAMESPACE_FROM_MANIFESTS: Remove namespace from manifests\n - CONFIG_CHECK_FILE_PATH: Check configuration file path\n - CONFIG_CHECK_DEPENDENCY_DEFINITION: Check dependency config definition\n - CONFIG_CHANGE_NAMES: Change config name to avoid duplicates\n - CONFIG_CHECK_FILTER: Check config filter\n - CONFIG_CHECK_PROFILE_DEFINITION: Check profile definition in current config\n - CONFIG_CHECK_DEPENDENCY_PROFILES_SELECTION: Check active profile selection for dependency config\n - CONFIG_CHECK_PROFILE_SELECTION: Check profile selection flag\n - CONFIG_FIX_API_VERSION: Fix config API version or upgrade the skaffold binary\n - CONFIG_ALLOWLIST_VALIDATORS: Only the allow listed validators are acceptable in skaffold-managed mode.\n - CONFIG_ALLOWLIST_transformers: Only the allow listed transformers are acceptable in skaffold-managed mode.\n - CONFIG_FIX_MISSING_MANIFEST_FILE: Check mising manifest file section of config and fix as needed.\n - CONFIG_ENABLE_REMOTE_REPO_SYNC: Enable remote repo sync, or clone manually\n - INSPECT_USE_MODIFY_OR_NEW_PROFILE: Create new build env in a profile instead, or use the 'modify' command\n - INSPECT_USE_ADD_BUILD_ENV: Check profile selection, or use the 'add' command instead\n - INSPECT_CHECK_INPUT_PROFILE: Check profile flag value\n - OPEN_ISSUE: Open an issue so this situation can be diagnosed\n - CHECK_CUSTOM_COMMAND: Test error suggestion codes" }, "enumsTesterType": { "type": "string", diff --git a/docs/content/en/docs/references/api-v2/grpc.md b/docs/content/en/docs/references/api-v2/grpc.md index 9ca6abbaa9f..baf9ed34dd7 100644 --- a/docs/content/en/docs/references/api-v2/grpc.md +++ b/docs/content/en/docs/references/api-v2/grpc.md @@ -1208,6 +1208,8 @@ For Cancelled Error code, use range 800 to 850.
| RENDER_KPTFILE_INIT_ERR | 1501 | Render errors The Kptfile cannot be created via `kpt pkg init`. | | RENDER_KPTFILE_INVALID_YAML_ERR | 1401 | The Kptfile is not a valid yaml file | | RENDER_KPTFILE_INVALID_SCHEMA_ERR | 1402 | The Kptfile is not a valid API schema | +| RENDER_SET_NAMESPACE_ERR | 1403 | Error setting namespace. | +| RENDER_NAMESPACE_ALREADY_SET_ERR | 1404 | Namespace is already set. | | CONFIG_FILE_PARSING_ERR | 1201 | Catch-all configuration file parsing error | | CONFIG_FILE_NOT_FOUND_ERR | 1202 | Main configuration file not found | | CONFIG_DEPENDENCY_NOT_FOUND_ERR | 1203 | Dependency configuration file not found | @@ -1288,6 +1290,7 @@ Enum for Suggestion codes | SET_RENDER_FLAG_OFFLINE_FALSE | 600 | Rerun with correct offline flag value. | | KPTFILE_MANUAL_INIT | 601 | Manually run `kpt pkg init` or `kpt live init` | | KPTFILE_CHECK_YAML | 602 | Check if the Kptfile is correct. | +| REMOVE_NAMESPACE_FROM_MANIFESTS | 603 | Remove namespace from manifests | | CONFIG_CHECK_FILE_PATH | 700 | Check configuration file path | | CONFIG_CHECK_DEPENDENCY_DEFINITION | 701 | Check dependency config definition | | CONFIG_CHANGE_NAMES | 702 | Change config name to avoid duplicates | diff --git a/docs/content/en/docs/references/api/grpc.md b/docs/content/en/docs/references/api/grpc.md index f8f576093b1..7cb31b6d86f 100644 --- a/docs/content/en/docs/references/api/grpc.md +++ b/docs/content/en/docs/references/api/grpc.md @@ -1063,6 +1063,8 @@ For Cancelled Error code, use range 800 to 850.
| RENDER_KPTFILE_INIT_ERR | 1501 | Render errors The Kptfile cannot be created via `kpt pkg init`. | | RENDER_KPTFILE_INVALID_YAML_ERR | 1401 | The Kptfile is not a valid yaml file | | RENDER_KPTFILE_INVALID_SCHEMA_ERR | 1402 | The Kptfile is not a valid API schema | +| RENDER_SET_NAMESPACE_ERR | 1403 | Error setting namespace. | +| RENDER_NAMESPACE_ALREADY_SET_ERR | 1404 | Namespace is already set. | | CONFIG_FILE_PARSING_ERR | 1201 | Catch-all configuration file parsing error | | CONFIG_FILE_NOT_FOUND_ERR | 1202 | Main configuration file not found | | CONFIG_DEPENDENCY_NOT_FOUND_ERR | 1203 | Dependency configuration file not found | @@ -1143,6 +1145,7 @@ Enum for Suggestion codes | SET_RENDER_FLAG_OFFLINE_FALSE | 600 | Rerun with correct offline flag value. | | KPTFILE_MANUAL_INIT | 601 | Manually run `kpt pkg init` or `kpt live init` | | KPTFILE_CHECK_YAML | 602 | Check if the Kptfile is correct. | +| REMOVE_NAMESPACE_FROM_MANIFESTS | 603 | Remove namespace from manifests | | CONFIG_CHECK_FILE_PATH | 700 | Check configuration file path | | CONFIG_CHECK_DEPENDENCY_DEFINITION | 701 | Check dependency config definition | | CONFIG_CHANGE_NAMES | 702 | Change config name to avoid duplicates | diff --git a/docs/content/en/docs/references/cli/_index.md b/docs/content/en/docs/references/cli/_index.md index 0c843957dc3..361cadacb24 100644 --- a/docs/content/en/docs/references/cli/_index.md +++ b/docs/content/en/docs/references/cli/_index.md @@ -131,7 +131,7 @@ Options: --kube-context='': Deploy to this Kubernetes context --kubeconfig='': Path to the kubeconfig file to use for CLI requests. -m, --module=[]: Filter Skaffold configs to only the provided named modules - -n, --namespace='': Run deployments in the specified namespace + -n, --namespace='': Runs deployments in the specified namespace. When used with 'render' command, renders manifests contain the namespace -p, --profile=[]: Activate profiles by name (prefixed with `-` to disable a profile) --remote-cache-dir='': Specify the location of the git repositories cache (default $HOME/.skaffold/repos) --status-check=: Wait for deployed resources to stabilize @@ -209,7 +209,7 @@ Options: --kubeconfig='': Path to the kubeconfig file to use for CLI requests. -m, --module=[]: Filter Skaffold configs to only the provided named modules --mute-logs=[]: mute logs for specified stages in pipeline (build, deploy, status-check, none, all) - -n, --namespace='': Run deployments in the specified namespace + -n, --namespace='': Runs deployments in the specified namespace. When used with 'render' command, renders manifests contain the namespace -o, --output={{json .}}: Used in conjunction with --quiet flag. Format output with go-template. For full struct documentation, see https://godoc.org/github.com/GoogleContainerTools/skaffold/cmd/skaffold/app/flags#BuildOutput --platform=[]: The platform to target for the build artifacts -p, --profile=[]: Activate profiles by name (prefixed with `-` to disable a profile) @@ -425,7 +425,7 @@ Options: -l, --label=[]: Add custom labels to deployed objects. Set multiple times for multiple labels -m, --module=[]: Filter Skaffold configs to only the provided named modules --mute-logs=[]: mute logs for specified stages in pipeline (build, deploy, status-check, none, all) - -n, --namespace='': Run deployments in the specified namespace + -n, --namespace='': Runs deployments in the specified namespace. When used with 'render' command, renders manifests contain the namespace --no-prune=false: Skip removing images and containers built by Skaffold --no-prune-children=false: Skip removing layers reused by Skaffold --platform=[]: The platform to target for the build artifacts @@ -536,7 +536,7 @@ Options: --kube-context='': Deploy to this Kubernetes context --kubeconfig='': Path to the kubeconfig file to use for CLI requests. -m, --module=[]: Filter Skaffold configs to only the provided named modules - -n, --namespace='': Run deployments in the specified namespace + -n, --namespace='': Runs deployments in the specified namespace. When used with 'render' command, renders manifests contain the namespace -p, --profile=[]: Activate profiles by name (prefixed with `-` to disable a profile) --profile-auto-activation=true: Set to false to disable profile auto activation --propagate-profiles=true: Setting '--propagate-profiles=false' disables propagating profiles set by the '--profile' flag across config dependencies. This mean that only profiles defined directly in the target 'skaffold.yaml' file are activated. @@ -608,7 +608,7 @@ Options: --load-images=false: If true, skaffold will force load the container images into the local cluster. -m, --module=[]: Filter Skaffold configs to only the provided named modules --mute-logs=[]: mute logs for specified stages in pipeline (build, deploy, status-check, none, all) - -n, --namespace='': Run deployments in the specified namespace + -n, --namespace='': Runs deployments in the specified namespace. When used with 'render' command, renders manifests contain the namespace --platform=[]: The platform to target for the build artifacts --port-forward=off: Port-forward exposes service ports and container ports within pods and other resources (off, user, services, debug, pods) -p, --profile=[]: Activate profiles by name (prefixed with `-` to disable a profile) @@ -711,7 +711,7 @@ Options: -l, --label=[]: Add custom labels to deployed objects. Set multiple times for multiple labels -m, --module=[]: Filter Skaffold configs to only the provided named modules --mute-logs=[]: mute logs for specified stages in pipeline (build, deploy, status-check, none, all) - -n, --namespace='': Run deployments in the specified namespace + -n, --namespace='': Runs deployments in the specified namespace. When used with 'render' command, renders manifests contain the namespace --no-prune=false: Skip removing images and containers built by Skaffold --no-prune-children=false: Skip removing layers reused by Skaffold --platform=[]: The platform to target for the build artifacts @@ -978,7 +978,7 @@ Options: -l, --label=[]: Add custom labels to deployed objects. Set multiple times for multiple labels --loud=false: Show the build logs and output -m, --module=[]: Filter Skaffold configs to only the provided named modules - -n, --namespace='': Run deployments in the specified namespace + -n, --namespace='': Runs deployments in the specified namespace. When used with 'render' command, renders manifests contain the namespace --offline=false: Do not connect to Kubernetes API server for manifest creation and validation. This is helpful when no Kubernetes cluster is available (e.g. GitOps model). No metadata.namespace attribute is injected in this case - the manifest content does not get changed. -o, --output='': File to write rendered manifests to -p, --profile=[]: Activate profiles by name (prefixed with `-` to disable a profile) @@ -1060,7 +1060,7 @@ Options: -l, --label=[]: Add custom labels to deployed objects. Set multiple times for multiple labels -m, --module=[]: Filter Skaffold configs to only the provided named modules --mute-logs=[]: mute logs for specified stages in pipeline (build, deploy, status-check, none, all) - -n, --namespace='': Run deployments in the specified namespace + -n, --namespace='': Runs deployments in the specified namespace. When used with 'render' command, renders manifests contain the namespace --no-prune=false: Skip removing images and containers built by Skaffold --no-prune-children=false: Skip removing layers reused by Skaffold --platform=[]: The platform to target for the build artifacts diff --git a/examples/getting-started/k8s-pod.yaml b/examples/getting-started/k8s-pod.yaml index 27fdd67998c..9927be92b67 100644 --- a/examples/getting-started/k8s-pod.yaml +++ b/examples/getting-started/k8s-pod.yaml @@ -2,6 +2,7 @@ apiVersion: v1 kind: Pod metadata: name: getting-started + namespace: "" spec: containers: - name: getting-started diff --git a/integration/render_test.go b/integration/render_test.go index 8e84ccbf019..e317aebc81c 100644 --- a/integration/render_test.go +++ b/integration/render_test.go @@ -19,6 +19,7 @@ package integration import ( "bytes" "context" + "fmt" "os" "path" "regexp" @@ -36,7 +37,7 @@ import ( func TestKubectlRenderOutput(t *testing.T) { MarkIntegrationTest(t, CanRunWithoutGcp) - + ns, _ := SetupNamespace(t) test := struct { description string builds []graph.Artifact @@ -57,12 +58,14 @@ spec: - image: gcr.io/k8s-skaffold/skaffold name: skaffold `, - expectedOut: `apiVersion: v1 + expectedOut: fmt.Sprintf(`apiVersion: v1 kind: Pod +metadata: + namespace: %s spec: containers: - image: gcr.io/k8s-skaffold/skaffold:test - name: skaffold`} + name: skaffold`, ns.Name)} testutil.Run(t, test.description, func(t *testutil.T) { tmpDir := t.NewTempDir() @@ -73,7 +76,7 @@ spec: RawK8s: []string{"deployment.yaml"}}, } mockCfg := render.MockConfig{WorkingDir: tmpDir.Root()} - r, err := kubectl.New(mockCfg, rc, map[string]string{}, "default") + r, err := kubectl.New(mockCfg, rc, map[string]string{}, "default", ns.Name) t.RequireNoError(err) var b bytes.Buffer l, err := r.Render(context.Background(), &b, test.builds, false) @@ -86,7 +89,7 @@ spec: func TestKubectlRender(t *testing.T) { MarkIntegrationTest(t, CanRunWithoutGcp) - + ns, _ := SetupNamespace(t) tests := []struct { description string builds []graph.Artifact @@ -110,14 +113,15 @@ spec: - image: gcr.io/k8s-skaffold/skaffold name: skaffold `, - expectedOut: `apiVersion: v1 + expectedOut: fmt.Sprintf(`apiVersion: v1 kind: Pod metadata: name: my-pod-123 + namespace: %s spec: containers: - image: gcr.io/k8s-skaffold/skaffold:test - name: skaffold`, + name: skaffold`, ns.Name), }, { description: "two artifacts", @@ -142,16 +146,17 @@ spec: - image: gcr.io/project/image2 name: image2 `, - expectedOut: `apiVersion: v1 + expectedOut: fmt.Sprintf(`apiVersion: v1 kind: Pod metadata: name: my-pod-123 + namespace: %s spec: containers: - image: gcr.io/project/image1:tag1 name: image1 - image: gcr.io/project/image2:tag2 - name: image2`, + name: image2`, ns.Name), }, { description: "two artifacts, combined manifests", @@ -183,10 +188,11 @@ spec: - image: gcr.io/project/image2 name: image2 `, - expectedOut: `apiVersion: v1 + expectedOut: fmt.Sprintf(`apiVersion: v1 kind: Pod metadata: name: my-pod-123 + namespace: %s spec: containers: - image: gcr.io/project/image1:tag1 @@ -196,10 +202,11 @@ apiVersion: v1 kind: Pod metadata: name: my-pod-456 + namespace: %s spec: containers: - image: gcr.io/project/image2:tag2 - name: image2`, + name: image2`, ns.Name, ns.Name), }, } for _, test := range tests { @@ -212,7 +219,7 @@ spec: RawK8s: []string{"deployment.yaml"}}, } mockCfg := render.MockConfig{WorkingDir: tmpDir.Root()} - r, err := kubectl.New(mockCfg, rc, map[string]string{}, "default") + r, err := kubectl.New(mockCfg, rc, map[string]string{}, "default", ns.Name) t.RequireNoError(err) var b bytes.Buffer l, err := r.Render(context.Background(), &b, test.builds, false) @@ -411,6 +418,7 @@ spec: kind: Pod metadata: name: my-pod-123 + namespace: default spec: containers: - image: 12345.dkr.ecr.eu-central-1.amazonaws.com/my/project-a:4da6a56988057d23f68a4e988f4905dd930ea438-dirty@sha256:d8a33c260c50385ea54077bc7032dba0a860dc8870464f6795fd0aa548d117bf @@ -419,7 +427,6 @@ spec: name: b `, }, - { description: "kubectl render from build output, offline, no labels", config: ` @@ -639,6 +646,7 @@ spec: kind: Pod metadata: name: my-pod-123 + namespace: default spec: containers: - image: 12345.dkr.ecr.eu-central-1.amazonaws.com/my/project-a:4da6a56988057d23f68a4e988f4905dd930ea438-dirty@sha256:d8a33c260c50385ea54077bc7032dba0a860dc8870464f6795fd0aa548d117bf @@ -675,7 +683,7 @@ spec: if test.offline { env := []string{"KUBECONFIG=not-supposed-to-be-used-in-offline-mode"} - args = append(args, "--offline") + args = append(args, "--offline=true") skaffold.Render(args...).WithEnv(env).RunOrFail(t.T) } else { skaffold.Render(args...).RunOrFail(t.T) diff --git a/pkg/skaffold/deploy/helm/helm.go b/pkg/skaffold/deploy/helm/helm.go index be423c7f1b0..2e12f7b3a65 100644 --- a/pkg/skaffold/deploy/helm/helm.go +++ b/pkg/skaffold/deploy/helm/helm.go @@ -126,6 +126,7 @@ type Config interface { kstatus.Config kloader.Config portforward.Config + GetNamespace() string IsMultiConfig() bool JSONParseConfig() latest.JSONParseConfig } diff --git a/pkg/skaffold/deploy/kubectl/cli.go b/pkg/skaffold/deploy/kubectl/cli.go index 9566a35110d..bb593183353 100644 --- a/pkg/skaffold/deploy/kubectl/cli.go +++ b/pkg/skaffold/deploy/kubectl/cli.go @@ -57,6 +57,7 @@ type Config interface { WaitForDeletions() config.WaitForDeletions Mode() config.RunMode HydratedManifests() []string + GetNamespace() string DefaultPipeline() latest.Pipeline Tail() bool PipelineForImage(imageName string) (latest.Pipeline, bool) diff --git a/pkg/skaffold/deploy/kubectl/kubectl_test.go b/pkg/skaffold/deploy/kubectl/kubectl_test.go index 917bd270ca1..c9e977acf05 100644 --- a/pkg/skaffold/deploy/kubectl/kubectl_test.go +++ b/pkg/skaffold/deploy/kubectl/kubectl_test.go @@ -235,7 +235,7 @@ func TestKubectlV1RenderDeploy(t *testing.T) { }, } - r, err := kubectlR.New(mockCfg, rc, map[string]string{}, configName) + r, err := kubectlR.New(mockCfg, rc, map[string]string{}, configName, "") t.CheckNoError(err) var b bytes.Buffer m, errR := r.Render(context.Background(), &b, []graph.Artifact{{ImageName: "leeroy-web", Tag: "leeroy-web:v1"}}, @@ -330,7 +330,7 @@ func TestKubectlCleanup(t *testing.T) { }, } - r, err := kubectlR.New(mockCfg, rc, map[string]string{}, configName) + r, err := kubectlR.New(mockCfg, rc, map[string]string{}, configName, "") t.CheckNoError(err) var b bytes.Buffer m, errR := r.Render(context.Background(), &b, []graph.Artifact{{ImageName: "leeroy-web", Tag: "leeroy-web:v1"}}, @@ -534,7 +534,7 @@ func TestGCSManifests(t *testing.T) { }), }, } - r, err := kubectlR.New(mockCfg, rc, map[string]string{}, configName) + r, err := kubectlR.New(mockCfg, rc, map[string]string{}, configName, "") t.CheckNoError(err) var b bytes.Buffer m, errR := r.Render(context.Background(), &b, []graph.Artifact{{ImageName: "leeroy-web", Tag: "leeroy-web:v1"}}, diff --git a/pkg/skaffold/deploy/kubectl/kustomize_test.go b/pkg/skaffold/deploy/kubectl/kustomize_test.go index ef4303f76eb..859a094d41e 100644 --- a/pkg/skaffold/deploy/kubectl/kustomize_test.go +++ b/pkg/skaffold/deploy/kubectl/kustomize_test.go @@ -142,7 +142,7 @@ func TestKustomizeRenderDeploy(t *testing.T) { mockCfg := &kubectlConfig{ RunContext: runcontext.RunContext{}, } - r, err := kubectlR.New(mockCfg, rc, map[string]string{}, configName) + r, err := kubectlR.New(mockCfg, rc, map[string]string{}, configName, "") t.CheckNoError(err) var b bytes.Buffer m, errR := r.Render(context.Background(), &b, test.builds, true) @@ -224,7 +224,7 @@ func TestKustomizeCleanup(t *testing.T) { workingDir: tmpDir.Root(), RunContext: runcontext.RunContext{}, } - r, err := kubectlR.New(mockCfg, rc, map[string]string{}, configName) + r, err := kubectlR.New(mockCfg, rc, map[string]string{}, configName, "") t.CheckNoError(err) var b bytes.Buffer m, errR := r.Render(context.Background(), &b, []graph.Artifact{{ImageName: "leeroy-web", Tag: "leeroy-web:v1"}}, @@ -444,7 +444,7 @@ func TestDependenciesForKustomization(t *testing.T) { mockCfg := &kubectlConfig{ RunContext: runcontext.RunContext{}, } - r, err := kubectlR.New(mockCfg, rc, map[string]string{}, "default") + r, err := kubectlR.New(mockCfg, rc, map[string]string{}, "default", "") t.CheckNoError(err) deps, err := r.ManifestDeps() diff --git a/pkg/skaffold/kubernetes/manifest/errors.go b/pkg/skaffold/kubernetes/manifest/errors.go index 1b31c529ceb..7a60a3faabb 100644 --- a/pkg/skaffold/kubernetes/manifest/errors.go +++ b/pkg/skaffold/kubernetes/manifest/errors.go @@ -65,3 +65,26 @@ func writeErr(err error) error { ErrCode: proto.StatusCode_DEPLOY_MANIFEST_WRITE_ERR, }) } + +func nsSettingErr(err error) error { + return sErrors.NewError(err, + &proto.ActionableErr{ + Message: fmt.Sprintf("setting namespace in manifests: %s", err), + ErrCode: proto.StatusCode_RENDER_SET_NAMESPACE_ERR, + }) +} + +func nsAlreadySetErr() error { + err := fmt.Errorf("namespace already set in the namesapce") + return sErrors.NewError(err, + &proto.ActionableErr{ + Message: err.Error(), + ErrCode: proto.StatusCode_RENDER_NAMESPACE_ALREADY_SET_ERR, + Suggestions: []*proto.Suggestion{ + { + SuggestionCode: proto.SuggestionCode_REMOVE_NAMESPACE_FROM_MANIFESTS, + Action: "remove/unset 'namespace' field in manifests and try again", + }, + }, + }) +} diff --git a/pkg/skaffold/kubernetes/manifest/namespace_test.go b/pkg/skaffold/kubernetes/manifest/namespace_test.go index 4d42c15b0b2..5d5f96e4373 100644 --- a/pkg/skaffold/kubernetes/manifest/namespace_test.go +++ b/pkg/skaffold/kubernetes/manifest/namespace_test.go @@ -173,3 +173,236 @@ spec: }) } } + +func TestSetNamespaces(t *testing.T) { + tests := []struct { + description string + manifests ManifestList + expected ManifestList + namespace string + shouldErr bool + }{ + { + description: "single Pod manifest in the list", + namespace: "test", + manifests: ManifestList{[]byte(` +apiVersion: v1 +kind: Pod +metadata: + name: getting-started +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example +`)}, + expected: ManifestList{[]byte(` +apiVersion: v1 +kind: Pod +metadata: + name: getting-started + namespace: test +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example +`)}, + }, { + description: "multiple manifest in the list with no namespace set", + namespace: "test", + manifests: ManifestList{[]byte(` +apiVersion: v1 +kind: Pod +metadata: + name: foo +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example`), []byte(` +apiVersion: v1 +kind: Pod +metadata: + name: bar +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example +`)}, + expected: ManifestList{[]byte(` +apiVersion: v1 +kind: Pod +metadata: + name: foo + namespace: test +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example`), []byte(` +apiVersion: v1 +kind: Pod +metadata: + name: bar + namespace: test +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example +`)}, + }, { + description: "single Pod manifest with nil namespace", + namespace: "test", + manifests: ManifestList{[]byte(` +apiVersion: v1 +kind: Pod +metadata: + name: getting-started + namespace: +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example +`)}, + expected: ManifestList{[]byte(` +apiVersion: v1 +kind: Pod +metadata: + name: getting-started + namespace: test +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example +`)}, + }, { + description: "single Pod manifest with empty namespace", + namespace: "test", + manifests: ManifestList{[]byte(` +apiVersion: v1 +kind: Pod +metadata: + name: getting-started + namespace: "" +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example +`)}, + expected: ManifestList{[]byte(` +apiVersion: v1 +kind: Pod +metadata: + name: getting-started + namespace: test +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example +`)}, + }, { + description: "empty manifest", + namespace: "test", + manifests: ManifestList{[]byte(``)}, + expected: ManifestList{[]byte(``)}, + }, { + description: "unexpected metadata type", + namespace: "test", + manifests: ManifestList{[]byte(`metadata: []`)}, + expected: ManifestList{[]byte(`metadata: []`)}, + }, + { + description: "empty metadata", + namespace: "test", + manifests: ManifestList{[]byte(``)}, + expected: ManifestList{[]byte(``)}, + }, + { + description: "single Pod manifest in the list with same namespace as set", + namespace: "test", + manifests: ManifestList{[]byte(` +apiVersion: v1 +kind: Pod +metadata: + name: getting-started + namespace: test +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example +`)}, + expected: ManifestList{[]byte(` +apiVersion: v1 +kind: Pod +metadata: + name: getting-started + namespace: test +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example +`)}, + }, + { + description: "single Pod manifest in the list with same namespace set to other", + namespace: "test", + manifests: ManifestList{[]byte(` +apiVersion: v1 +kind: Pod +metadata: + name: getting-started + namespace: other +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example +`)}, + expected: nil, + shouldErr: true, + }, + { + description: "empty namespace", + namespace: "", + manifests: ManifestList{[]byte(` +apiVersion: v1 +kind: Pod +metadata: + name: getting-started +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example +`)}, + expected: ManifestList{[]byte(` +apiVersion: v1 +kind: Pod +metadata: + name: getting-started + namespace: default +spec: + containers: + - image: gcr.io/k8s-skaffold/example + name: example +`)}, + }, + { + description: "should not add namespace to any resource", + namespace: "test", + manifests: ManifestList{[]byte(` +apiVersion: v1 +kind: ConfigMap +metadata: + name: getting-started +`)}, + expected: ManifestList{[]byte(` +apiVersion: v1 +kind: ConfigMap +metadata: + name: getting-started +`)}}, + } + for _, test := range tests { + testutil.Run(t, test.description, func(t *testutil.T) { + actual, err := test.manifests.SetNamespace(test.namespace, + NewResourceSelectorLabels(TransformAllowlist, TransformDenylist)) + t.CheckErrorAndDeepEqual(test.shouldErr, err, test.expected.String(), actual.String()) + }) + } +} diff --git a/pkg/skaffold/kubernetes/manifest/namespaces.go b/pkg/skaffold/kubernetes/manifest/namespaces.go index 682898f9553..7ffc47027f1 100644 --- a/pkg/skaffold/kubernetes/manifest/namespaces.go +++ b/pkg/skaffold/kubernetes/manifest/namespaces.go @@ -17,13 +17,19 @@ limitations under the License. package manifest import ( + "context" "fmt" "sort" "strings" "k8s.io/apimachinery/pkg/runtime/schema" + + "github.com/GoogleContainerTools/skaffold/pkg/skaffold/output/log" + "github.com/GoogleContainerTools/skaffold/pkg/skaffold/yaml" ) +const namespaceField = "namespace" + // CollectNamespaces returns all the namespaces in the manifests. func (l *ManifestList) CollectNamespaces() ([]string, error) { replacer := newNamespaceCollector() @@ -63,7 +69,7 @@ func (r *namespaceCollector) Visit(gk schema.GroupKind, navpath string, o map[st if !ok { return true } - if nsValue, present := metadata["namespace"]; present { + if nsValue, present := metadata[namespaceField]; present { nsString, ok := nsValue.(string) if !ok || nsString == "" { return true @@ -74,3 +80,65 @@ func (r *namespaceCollector) Visit(gk schema.GroupKind, navpath string, o map[st } return false } + +// SetNamespace sets labels to a list of Kubernetes manifests if they are not set. +// Returns error if any manifest in the list has namespace set. +func (l *ManifestList) SetNamespace(namespace string, rs ResourceSelector) (ManifestList, error) { + if namespace == "" { + namespace = "default" + } + var updated ManifestList + for _, item := range *l { + updatedManifest := item + m := make(map[string]interface{}) + if err := yaml.Unmarshal(item, &m); err != nil { + return nil, fmt.Errorf("reading Kubernetes YAML: %w", err) + } + if shouldTransformManifest(m, rs) { + var errU error + if errU = addOrUpdateNamespace(m, namespace); errU != nil { + return nil, errU + } + updatedManifest, errU = yaml.Marshal(m) + if errU != nil { + return nil, nsSettingErr(errU) + } + } + updated = append(updated, updatedManifest) + } + + log.Entry(context.TODO()).Debugln("manifests set with namespace", updated.String()) + return updated, nil +} + +func addOrUpdateNamespace(manifest map[string]interface{}, ns string) error { + originalMetadata, ok := manifest[metadataField] + if !ok { + metadataAdded := make(map[string]interface{}) + metadataAdded[namespaceField] = ns + manifest[metadataField] = metadataAdded + return nil + } + metadata, ok := originalMetadata.(map[string]interface{}) + if !ok { + return nsSettingErr(fmt.Errorf("error converting %s to map[string]interface{}", originalMetadata)) + } + nsValue, present := metadata[namespaceField] + if !present || isEmptyOrEqual(nsValue, ns) { + metadata[namespaceField] = ns + return nil + } + return nsAlreadySetErr() +} + +func isEmptyOrEqual(v interface{}, s string) bool { + // check if namespace is set to empty string + if v == nil { + return true + } + nsString, ok := v.(string) + if !ok { + return false + } + return nsString == "" || nsString == s +} diff --git a/pkg/skaffold/render/config.go b/pkg/skaffold/render/config.go index 6e6b363a948..4eeeb6f3681 100644 --- a/pkg/skaffold/render/config.go +++ b/pkg/skaffold/render/config.go @@ -29,12 +29,14 @@ type Config interface { GetKubeConfig() string TransformAllowList() []latest.ResourceFilter TransformDenyList() []latest.ResourceFilter + GetNamespace() string Mode() config.RunMode EnablePlatformNodeAffinityInRenderedManifests() bool } type MockConfig struct { WorkingDir string + Namespace string } func (mc MockConfig) GetWorkingDir() string { return mc.WorkingDir } @@ -46,3 +48,4 @@ func (mc MockConfig) GetKubeConfig() string { retu func (mc MockConfig) GetKubeContext() string { return "" } func (mc MockConfig) Mode() config.RunMode { return "" } func (mc MockConfig) EnablePlatformNodeAffinityInRenderedManifests() bool { return true } +func (mc MockConfig) GetNamespace() string { return mc.Namespace } diff --git a/pkg/skaffold/render/generate/generate_test.go b/pkg/skaffold/render/generate/generate_test.go index 9ef83d80062..1d204bd6470 100644 --- a/pkg/skaffold/render/generate/generate_test.go +++ b/pkg/skaffold/render/generate/generate_test.go @@ -41,8 +41,7 @@ metadata: spec: containers: - name: leeroy-web - image: leeroy-web -` + image: leeroy-web` // Test file under /pods.yaml. This file contains multiple config object. podsYaml = `apiVersion: v1 diff --git a/pkg/skaffold/render/renderer/kpt/kpt.go b/pkg/skaffold/render/renderer/kpt/kpt.go index ba0ec104246..68ec3866aa0 100644 --- a/pkg/skaffold/render/renderer/kpt/kpt.go +++ b/pkg/skaffold/render/renderer/kpt/kpt.go @@ -52,6 +52,7 @@ type Kpt struct { transform.Transformer hydrationDir string labels map[string]string + namespace string transformAllowlist map[apimachinery.GroupKind]latest.ResourceFilter transformDenylist map[apimachinery.GroupKind]latest.ResourceFilter @@ -61,7 +62,7 @@ const ( DryFileName = "manifests.yaml" ) -func New(cfg render.Config, rCfg latest.RenderConfig, hydrationDir string, labels map[string]string, configName string) (*Kpt, error) { +func New(cfg render.Config, rCfg latest.RenderConfig, hydrationDir string, labels map[string]string, configName string, ns string) (*Kpt, error) { generator := generate.NewGenerator(cfg.GetWorkingDir(), rCfg.Generate) transformAllowlist, transformDenylist, err := rUtil.ConsolidateTransformConfiguration(cfg) if err != nil { @@ -98,6 +99,7 @@ func New(cfg render.Config, rCfg latest.RenderConfig, hydrationDir string, label labels: labels, transformAllowlist: transformAllowlist, transformDenylist: transformDenylist, + namespace: ns, }, nil } @@ -152,9 +154,10 @@ func (r *Kpt) Render(ctx context.Context, out io.Writer, builds []graph.Artifact TransformAllowList: r.transformAllowlist, TransformDenylist: r.transformDenylist, EnablePlatformNodeAffinity: r.cfg.EnablePlatformNodeAffinityInRenderedManifests(), + Offline: offline, } - manifests, errH := rUtil.GenerateHydratedManifests(ctx, out, builds, r.Generator, r.labels, opts) - if err != nil { + manifests, errH := rUtil.GenerateHydratedManifests(ctx, out, builds, r.Generator, r.labels, r.namespace, opts) + if errH != nil { return ml, errH } // Write generated dry manifests. diff --git a/pkg/skaffold/render/renderer/kpt/kpt_test.go b/pkg/skaffold/render/renderer/kpt/kpt_test.go index d2ea1e4e407..afe8433bd3b 100644 --- a/pkg/skaffold/render/renderer/kpt/kpt_test.go +++ b/pkg/skaffold/render/renderer/kpt/kpt_test.go @@ -48,6 +48,7 @@ spec: kind: Pod metadata: name: leeroy-web + namespace: default spec: containers: - image: leeroy-web:v1 @@ -174,7 +175,7 @@ pipeline: mockCfg := render.MockConfig{ WorkingDir: tmpDirObj.Root(), } - r, err := New(mockCfg, test.renderConfig, filepath.Join(tmpDirObj.Root(), constants.DefaultHydrationDir), map[string]string{}, "default") + r, err := New(mockCfg, test.renderConfig, filepath.Join(tmpDirObj.Root(), constants.DefaultHydrationDir), map[string]string{}, "default", "") t.CheckNoError(err) t.Override(&util.DefaultExecCommand, testutil.CmdRun(fmt.Sprintf("kpt fn render %v", @@ -183,7 +184,7 @@ pipeline: filepath.Join(tmpDirObj.Root(), ".kpt-pipeline")), "")) var b bytes.Buffer _, err = r.Render(context.Background(), &b, []graph.Artifact{{ImageName: "leeroy-web", Tag: "leeroy-web:v1"}}, - true) + false) t.CheckNoError(err) t.CheckFileExistAndContent(filepath.Join(tmpDirObj.Root(), constants.DefaultHydrationDir, DryFileName), []byte(labeledPodYaml)) t.CheckFileExistAndContent(filepath.Join(tmpDirObj.Root(), constants.DefaultHydrationDir, kptfile.KptFileName), []byte(test.updatedKptfile)) @@ -245,7 +246,7 @@ inventory: mockCfg := render.MockConfig{ WorkingDir: tmpDirObj.Root(), } - r, err := New(mockCfg, renderConfig, filepath.Join(tmpDirObj.Root(), constants.DefaultHydrationDir), map[string]string{}, "default") + r, err := New(mockCfg, renderConfig, filepath.Join(tmpDirObj.Root(), constants.DefaultHydrationDir), map[string]string{}, "default", "") t.CheckNoError(err) t.Override(&util.DefaultExecCommand, testutil.CmdRun(fmt.Sprintf("kpt fn render %v", diff --git a/pkg/skaffold/render/renderer/kubectl/kubectl.go b/pkg/skaffold/render/renderer/kubectl/kubectl.go index 34e2c4ff6ac..99598dec077 100644 --- a/pkg/skaffold/render/renderer/kubectl/kubectl.go +++ b/pkg/skaffold/render/renderer/kubectl/kubectl.go @@ -36,6 +36,7 @@ type Kubectl struct { cfg render.Config configName string + namespace string generate.Generator labels map[string]string @@ -44,7 +45,7 @@ type Kubectl struct { transformDenylist map[apimachinery.GroupKind]latest.ResourceFilter } -func New(cfg render.Config, rCfg latest.RenderConfig, labels map[string]string, configName string) (Kubectl, error) { +func New(cfg render.Config, rCfg latest.RenderConfig, labels map[string]string, configName string, ns string) (Kubectl, error) { generator := generate.NewGenerator(cfg.GetWorkingDir(), rCfg.Generate) transformAllowlist, transformDenylist, err := util.ConsolidateTransformConfiguration(cfg) if err != nil { @@ -54,6 +55,7 @@ func New(cfg render.Config, rCfg latest.RenderConfig, labels map[string]string, cfg: cfg, configName: configName, Generator: generator, + namespace: ns, labels: labels, transformAllowlist: transformAllowlist, @@ -71,8 +73,9 @@ func (r Kubectl) Render(ctx context.Context, out io.Writer, builds []graph.Artif TransformAllowList: r.transformAllowlist, TransformDenylist: r.transformDenylist, EnablePlatformNodeAffinity: r.cfg.EnablePlatformNodeAffinityInRenderedManifests(), + Offline: offline, } - manifests, err := util.GenerateHydratedManifests(ctx, out, builds, r.Generator, r.labels, opts) + manifests, err := util.GenerateHydratedManifests(ctx, out, builds, r.Generator, r.labels, r.namespace, opts) endTrace() manifestListByConfig := manifest.NewManifestListByConfig() manifestListByConfig.Add(r.configName, manifests) diff --git a/pkg/skaffold/render/renderer/kubectl/kubectl_test.go b/pkg/skaffold/render/renderer/kubectl/kubectl_test.go index 56b8607c656..ee71ae04073 100644 --- a/pkg/skaffold/render/renderer/kubectl/kubectl_test.go +++ b/pkg/skaffold/render/renderer/kubectl/kubectl_test.go @@ -44,6 +44,7 @@ metadata: labels: run.id: test name: leeroy-web + namespace: default spec: containers: - image: leeroy-web:v1 @@ -53,6 +54,7 @@ spec: kind: Pod metadata: name: leeroy-web + namespace: default spec: containers: - image: leeroy-web:v1 @@ -89,11 +91,11 @@ func TestRender(t *testing.T) { Touch("empty.ignored"). Chdir() mockCfg := render.MockConfig{WorkingDir: tmpDirObj.Root()} - r, err := New(mockCfg, test.renderConfig, test.labels, "default") + r, err := New(mockCfg, test.renderConfig, test.labels, "default", "") t.CheckNoError(err) var b bytes.Buffer manifestList, errR := r.Render(context.Background(), &b, []graph.Artifact{{ImageName: "leeroy-web", Tag: "leeroy-web:v1"}}, - true) + false) t.CheckNoError(errR) t.CheckDeepEqual(test.expected, manifestList.String()) }) @@ -154,7 +156,7 @@ func TestDependencies(t *testing.T) { rCfg := latest.RenderConfig{ Generate: latest.Generate{RawK8s: test.manifests}, } - r, err := New(mockCfg, rCfg, map[string]string{}, "default") + r, err := New(mockCfg, rCfg, map[string]string{}, "default", "") t.CheckNoError(err) dependencies, err := r.ManifestDeps() diff --git a/pkg/skaffold/render/renderer/renderer.go b/pkg/skaffold/render/renderer/renderer.go index 720c2b602c7..f0926f1ce74 100644 --- a/pkg/skaffold/render/renderer/renderer.go +++ b/pkg/skaffold/render/renderer/renderer.go @@ -44,18 +44,18 @@ func New(ctx context.Context, cfg render.Config, renderCfg latest.RenderConfig, return GroupRenderer{noop.New(renderCfg, cfg.GetWorkingDir(), hydrationDir, labels)}, nil } if renderCfg.Validate != nil || renderCfg.Transform != nil || renderCfg.Kpt != nil { - r, err := kpt.New(cfg, renderCfg, hydrationDir, labels, configName) + r, err := kpt.New(cfg, renderCfg, hydrationDir, labels, configName, cfg.GetNamespace()) if err != nil { return nil, err } - log.Entry(context.TODO()).Infof("setting up kpt renderer") + log.Entry(ctx).Infof("setting up kpt renderer") return []Renderer{r}, nil } var rs GroupRenderer if renderCfg.RawK8s != nil || renderCfg.Kustomize != nil { - r, err := kubectl.New(cfg, renderCfg, labels, configName) + r, err := kubectl.New(cfg, renderCfg, labels, configName, cfg.GetNamespace()) if err != nil { return nil, err } diff --git a/pkg/skaffold/render/renderer/util/util.go b/pkg/skaffold/render/renderer/util/util.go index 03aead69c0e..75a1594904d 100644 --- a/pkg/skaffold/render/renderer/util/util.go +++ b/pkg/skaffold/render/renderer/util/util.go @@ -37,9 +37,10 @@ type GenerateHydratedManifestsOptions struct { TransformAllowList map[apim.GroupKind]latest.ResourceFilter TransformDenylist map[apim.GroupKind]latest.ResourceFilter EnablePlatformNodeAffinity bool + Offline bool } -func GenerateHydratedManifests(ctx context.Context, out io.Writer, builds []graph.Artifact, g generate.Generator, labels map[string]string, opts GenerateHydratedManifestsOptions) (manifest.ManifestList, error) { +func GenerateHydratedManifests(ctx context.Context, out io.Writer, builds []graph.Artifact, g generate.Generator, labels map[string]string, ns string, opts GenerateHydratedManifestsOptions) (manifest.ManifestList, error) { // Generate manifests. rCtx, endTrace := instrumentation.StartTrace(ctx, "Render_generateManifest") manifests, err := g.Generate(rCtx, out) @@ -55,11 +56,19 @@ func GenerateHydratedManifests(ctx context.Context, out io.Writer, builds []grap if err != nil { return nil, err } + rs := manifest.NewResourceSelectorLabels(opts.TransformAllowList, opts.TransformDenylist) // TODO(aaron-prindle) wire proper transform allow/deny list args when going to V2 if manifests, err = manifests.SetLabels(labels, manifest.NewResourceSelectorLabels(opts.TransformAllowList, opts.TransformDenylist)); err != nil { return nil, err } - endTrace() + // TODO(tejaldesai) consult with cloud deploy team if namespaces can be set in offline mode + // in case namespace is set on the skaffold render cli command. + if !opts.Offline { + if manifests, err = manifests.SetNamespace(ns, rs); err != nil { + return nil, err + } + endTrace() + } if !opts.EnablePlatformNodeAffinity { return manifests, nil diff --git a/proto/enums/enums.pb.go b/proto/enums/enums.pb.go index 279455e5322..6df3cd0d34c 100644 --- a/proto/enums/enums.pb.go +++ b/proto/enums/enums.pb.go @@ -796,6 +796,10 @@ const ( StatusCode_RENDER_KPTFILE_INVALID_YAML_ERR StatusCode = 1401 // The Kptfile is not a valid API schema StatusCode_RENDER_KPTFILE_INVALID_SCHEMA_ERR StatusCode = 1402 + // Error setting namespace. + StatusCode_RENDER_SET_NAMESPACE_ERR StatusCode = 1403 + // Namespace is already set. + StatusCode_RENDER_NAMESPACE_ALREADY_SET_ERR StatusCode = 1404 // Catch-all configuration file parsing error StatusCode_CONFIG_FILE_PARSING_ERR StatusCode = 1201 // Main configuration file not found @@ -1011,6 +1015,8 @@ var ( 1501: "RENDER_KPTFILE_INIT_ERR", 1401: "RENDER_KPTFILE_INVALID_YAML_ERR", 1402: "RENDER_KPTFILE_INVALID_SCHEMA_ERR", + 1403: "RENDER_SET_NAMESPACE_ERR", + 1404: "RENDER_NAMESPACE_ALREADY_SET_ERR", 1201: "CONFIG_FILE_PARSING_ERR", 1202: "CONFIG_FILE_NOT_FOUND_ERR", 1203: "CONFIG_DEPENDENCY_NOT_FOUND_ERR", @@ -1202,6 +1208,8 @@ var ( "RENDER_KPTFILE_INIT_ERR": 1501, "RENDER_KPTFILE_INVALID_YAML_ERR": 1401, "RENDER_KPTFILE_INVALID_SCHEMA_ERR": 1402, + "RENDER_SET_NAMESPACE_ERR": 1403, + "RENDER_NAMESPACE_ALREADY_SET_ERR": 1404, "CONFIG_FILE_PARSING_ERR": 1201, "CONFIG_FILE_NOT_FOUND_ERR": 1202, "CONFIG_DEPENDENCY_NOT_FOUND_ERR": 1203, @@ -1354,6 +1362,8 @@ const ( SuggestionCode_KPTFILE_MANUAL_INIT SuggestionCode = 601 // Check if the Kptfile is correct. SuggestionCode_KPTFILE_CHECK_YAML SuggestionCode = 602 + // Remove namespace from manifests + SuggestionCode_REMOVE_NAMESPACE_FROM_MANIFESTS SuggestionCode = 603 // Check configuration file path SuggestionCode_CONFIG_CHECK_FILE_PATH SuggestionCode = 700 // Check dependency config definition @@ -1444,6 +1454,7 @@ var ( 600: "SET_RENDER_FLAG_OFFLINE_FALSE", 601: "KPTFILE_MANUAL_INIT", 602: "KPTFILE_CHECK_YAML", + 603: "REMOVE_NAMESPACE_FROM_MANIFESTS", 700: "CONFIG_CHECK_FILE_PATH", 701: "CONFIG_CHECK_DEPENDENCY_DEFINITION", 702: "CONFIG_CHANGE_NAMES", @@ -1514,6 +1525,7 @@ var ( "SET_RENDER_FLAG_OFFLINE_FALSE": 600, "KPTFILE_MANUAL_INIT": 601, "KPTFILE_CHECK_YAML": 602, + "REMOVE_NAMESPACE_FROM_MANIFESTS": 603, "CONFIG_CHECK_FILE_PATH": 700, "CONFIG_CHECK_DEPENDENCY_DEFINITION": 701, "CONFIG_CHANGE_NAMES": 702, @@ -1610,7 +1622,7 @@ var file_enums_proto_rawDesc = []byte{ 0x10, 0x03, 0x12, 0x09, 0x0a, 0x05, 0x46, 0x41, 0x54, 0x41, 0x4c, 0x10, 0x04, 0x12, 0x09, 0x0a, 0x05, 0x50, 0x41, 0x4e, 0x49, 0x43, 0x10, 0x05, 0x12, 0x09, 0x0a, 0x05, 0x54, 0x52, 0x41, 0x43, 0x45, 0x10, 0x06, 0x12, 0x0c, 0x0a, 0x08, 0x53, 0x54, 0x41, 0x4e, 0x44, 0x41, 0x52, 0x44, 0x10, - 0x07, 0x2a, 0xc7, 0x32, 0x0a, 0x0a, 0x53, 0x74, 0x61, 0x74, 0x75, 0x73, 0x43, 0x6f, 0x64, 0x65, + 0x07, 0x2a, 0x8d, 0x33, 0x0a, 0x0a, 0x53, 0x74, 0x61, 0x74, 0x75, 0x73, 0x43, 0x6f, 0x64, 0x65, 0x12, 0x06, 0x0a, 0x02, 0x4f, 0x4b, 0x10, 0x00, 0x12, 0x18, 0x0a, 0x13, 0x53, 0x54, 0x41, 0x54, 0x55, 0x53, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x53, 0x55, 0x43, 0x43, 0x45, 0x53, 0x53, 0x10, 0xc8, 0x01, 0x12, 0x12, 0x0a, 0x0d, 0x42, 0x55, 0x49, 0x4c, 0x44, 0x5f, 0x53, 0x55, 0x43, 0x43, @@ -1961,199 +1973,206 @@ var file_enums_proto_rawDesc = []byte{ 0x5f, 0x49, 0x4e, 0x56, 0x41, 0x4c, 0x49, 0x44, 0x5f, 0x59, 0x41, 0x4d, 0x4c, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xf9, 0x0a, 0x12, 0x26, 0x0a, 0x21, 0x52, 0x45, 0x4e, 0x44, 0x45, 0x52, 0x5f, 0x4b, 0x50, 0x54, 0x46, 0x49, 0x4c, 0x45, 0x5f, 0x49, 0x4e, 0x56, 0x41, 0x4c, 0x49, 0x44, 0x5f, 0x53, - 0x43, 0x48, 0x45, 0x4d, 0x41, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xfa, 0x0a, 0x12, 0x1c, 0x0a, 0x17, - 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x46, 0x49, 0x4c, 0x45, 0x5f, 0x50, 0x41, 0x52, 0x53, - 0x49, 0x4e, 0x47, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb1, 0x09, 0x12, 0x1e, 0x0a, 0x19, 0x43, 0x4f, - 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x46, 0x49, 0x4c, 0x45, 0x5f, 0x4e, 0x4f, 0x54, 0x5f, 0x46, 0x4f, - 0x55, 0x4e, 0x44, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb2, 0x09, 0x12, 0x24, 0x0a, 0x1f, 0x43, 0x4f, - 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x44, 0x45, 0x50, 0x45, 0x4e, 0x44, 0x45, 0x4e, 0x43, 0x59, 0x5f, - 0x4e, 0x4f, 0x54, 0x5f, 0x46, 0x4f, 0x55, 0x4e, 0x44, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb3, 0x09, - 0x12, 0x29, 0x0a, 0x24, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x44, 0x55, 0x50, 0x4c, 0x49, - 0x43, 0x41, 0x54, 0x45, 0x5f, 0x4e, 0x41, 0x4d, 0x45, 0x53, 0x5f, 0x53, 0x41, 0x4d, 0x45, 0x5f, - 0x46, 0x49, 0x4c, 0x45, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb4, 0x09, 0x12, 0x2c, 0x0a, 0x27, 0x43, - 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x44, 0x55, 0x50, 0x4c, 0x49, 0x43, 0x41, 0x54, 0x45, 0x5f, - 0x4e, 0x41, 0x4d, 0x45, 0x53, 0x5f, 0x41, 0x43, 0x52, 0x4f, 0x53, 0x53, 0x5f, 0x46, 0x49, 0x4c, - 0x45, 0x53, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb5, 0x09, 0x12, 0x1a, 0x0a, 0x15, 0x43, 0x4f, 0x4e, - 0x46, 0x49, 0x47, 0x5f, 0x42, 0x41, 0x44, 0x5f, 0x46, 0x49, 0x4c, 0x54, 0x45, 0x52, 0x5f, 0x45, - 0x52, 0x52, 0x10, 0xb6, 0x09, 0x12, 0x1a, 0x0a, 0x15, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, - 0x5a, 0x45, 0x52, 0x4f, 0x5f, 0x46, 0x4f, 0x55, 0x4e, 0x44, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb7, - 0x09, 0x12, 0x1e, 0x0a, 0x19, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x41, 0x50, 0x50, 0x4c, - 0x59, 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, 0x4c, 0x45, 0x53, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb8, - 0x09, 0x12, 0x1e, 0x0a, 0x19, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x44, 0x45, 0x46, 0x41, - 0x55, 0x4c, 0x54, 0x5f, 0x56, 0x41, 0x4c, 0x55, 0x45, 0x53, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb9, - 0x09, 0x12, 0x27, 0x0a, 0x22, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x46, 0x49, 0x4c, 0x45, - 0x5f, 0x50, 0x41, 0x54, 0x48, 0x53, 0x5f, 0x53, 0x55, 0x42, 0x53, 0x54, 0x49, 0x54, 0x55, 0x54, - 0x49, 0x4f, 0x4e, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xba, 0x09, 0x12, 0x2d, 0x0a, 0x28, 0x43, 0x4f, - 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x4d, 0x55, 0x4c, 0x54, 0x49, 0x5f, 0x49, 0x4d, 0x50, 0x4f, 0x52, - 0x54, 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, 0x4c, 0x45, 0x5f, 0x43, 0x4f, 0x4e, 0x46, 0x4c, 0x49, - 0x43, 0x54, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xbb, 0x09, 0x12, 0x22, 0x0a, 0x1d, 0x43, 0x4f, 0x4e, - 0x46, 0x49, 0x47, 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, 0x4c, 0x45, 0x53, 0x5f, 0x4e, 0x4f, 0x54, - 0x5f, 0x46, 0x4f, 0x55, 0x4e, 0x44, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xbc, 0x09, 0x12, 0x23, 0x0a, - 0x1e, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x55, 0x4e, 0x4b, 0x4e, 0x4f, 0x57, 0x4e, 0x5f, - 0x41, 0x50, 0x49, 0x5f, 0x56, 0x45, 0x52, 0x53, 0x49, 0x4f, 0x4e, 0x5f, 0x45, 0x52, 0x52, 0x10, - 0xbd, 0x09, 0x12, 0x1d, 0x0a, 0x18, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x55, 0x4e, 0x4b, - 0x4e, 0x4f, 0x57, 0x4e, 0x5f, 0x56, 0x41, 0x4c, 0x49, 0x44, 0x41, 0x54, 0x4f, 0x52, 0x10, 0xbe, - 0x09, 0x12, 0x1f, 0x0a, 0x1a, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x55, 0x4e, 0x4b, 0x4e, - 0x4f, 0x57, 0x4e, 0x5f, 0x54, 0x52, 0x41, 0x4e, 0x53, 0x46, 0x4f, 0x52, 0x4d, 0x45, 0x52, 0x10, - 0xbf, 0x09, 0x12, 0x25, 0x0a, 0x20, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x4d, 0x49, 0x53, - 0x53, 0x49, 0x4e, 0x47, 0x5f, 0x4d, 0x41, 0x4e, 0x49, 0x46, 0x45, 0x53, 0x54, 0x5f, 0x46, 0x49, - 0x4c, 0x45, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xc0, 0x09, 0x12, 0x2b, 0x0a, 0x26, 0x43, 0x4f, 0x4e, - 0x46, 0x49, 0x47, 0x5f, 0x52, 0x45, 0x4d, 0x4f, 0x54, 0x45, 0x5f, 0x52, 0x45, 0x50, 0x4f, 0x5f, - 0x43, 0x41, 0x43, 0x48, 0x45, 0x5f, 0x4e, 0x4f, 0x54, 0x5f, 0x46, 0x4f, 0x55, 0x4e, 0x44, 0x5f, - 0x45, 0x52, 0x52, 0x10, 0xc1, 0x09, 0x12, 0x18, 0x0a, 0x13, 0x49, 0x4e, 0x53, 0x50, 0x45, 0x43, - 0x54, 0x5f, 0x55, 0x4e, 0x4b, 0x4e, 0x4f, 0x57, 0x4e, 0x5f, 0x45, 0x52, 0x52, 0x10, 0x95, 0x0a, - 0x12, 0x29, 0x0a, 0x24, 0x49, 0x4e, 0x53, 0x50, 0x45, 0x43, 0x54, 0x5f, 0x42, 0x55, 0x49, 0x4c, - 0x44, 0x5f, 0x45, 0x4e, 0x56, 0x5f, 0x41, 0x4c, 0x52, 0x45, 0x41, 0x44, 0x59, 0x5f, 0x45, 0x58, - 0x49, 0x53, 0x54, 0x53, 0x5f, 0x45, 0x52, 0x52, 0x10, 0x96, 0x0a, 0x12, 0x29, 0x0a, 0x24, 0x49, - 0x4e, 0x53, 0x50, 0x45, 0x43, 0x54, 0x5f, 0x42, 0x55, 0x49, 0x4c, 0x44, 0x5f, 0x45, 0x4e, 0x56, - 0x5f, 0x49, 0x4e, 0x43, 0x4f, 0x52, 0x52, 0x45, 0x43, 0x54, 0x5f, 0x54, 0x59, 0x50, 0x45, 0x5f, - 0x45, 0x52, 0x52, 0x10, 0x97, 0x0a, 0x12, 0x22, 0x0a, 0x1d, 0x49, 0x4e, 0x53, 0x50, 0x45, 0x43, - 0x54, 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, 0x4c, 0x45, 0x5f, 0x4e, 0x4f, 0x54, 0x5f, 0x46, 0x4f, - 0x55, 0x4e, 0x44, 0x5f, 0x45, 0x52, 0x52, 0x10, 0x98, 0x0a, 0x12, 0x26, 0x0a, 0x21, 0x50, 0x4f, - 0x52, 0x54, 0x5f, 0x46, 0x4f, 0x52, 0x57, 0x41, 0x52, 0x44, 0x5f, 0x52, 0x55, 0x4e, 0x5f, 0x47, - 0x43, 0x4c, 0x4f, 0x55, 0x44, 0x5f, 0x4e, 0x4f, 0x54, 0x5f, 0x46, 0x4f, 0x55, 0x4e, 0x44, 0x10, - 0xc1, 0x0c, 0x12, 0x27, 0x0a, 0x22, 0x50, 0x4f, 0x52, 0x54, 0x5f, 0x46, 0x4f, 0x52, 0x57, 0x41, - 0x52, 0x44, 0x5f, 0x52, 0x55, 0x4e, 0x5f, 0x50, 0x52, 0x4f, 0x58, 0x59, 0x5f, 0x53, 0x54, 0x41, - 0x52, 0x54, 0x5f, 0x45, 0x52, 0x52, 0x4f, 0x52, 0x10, 0xc2, 0x0c, 0x2a, 0xea, 0x10, 0x0a, 0x0e, - 0x53, 0x75, 0x67, 0x67, 0x65, 0x73, 0x74, 0x69, 0x6f, 0x6e, 0x43, 0x6f, 0x64, 0x65, 0x12, 0x07, - 0x0a, 0x03, 0x4e, 0x49, 0x4c, 0x10, 0x00, 0x12, 0x14, 0x0a, 0x10, 0x41, 0x44, 0x44, 0x5f, 0x44, - 0x45, 0x46, 0x41, 0x55, 0x4c, 0x54, 0x5f, 0x52, 0x45, 0x50, 0x4f, 0x10, 0x64, 0x12, 0x16, 0x0a, - 0x12, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x44, 0x45, 0x46, 0x41, 0x55, 0x4c, 0x54, 0x5f, 0x52, - 0x45, 0x50, 0x4f, 0x10, 0x65, 0x12, 0x24, 0x0a, 0x20, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x44, - 0x45, 0x46, 0x41, 0x55, 0x4c, 0x54, 0x5f, 0x52, 0x45, 0x50, 0x4f, 0x5f, 0x47, 0x4c, 0x4f, 0x42, - 0x41, 0x4c, 0x5f, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x10, 0x66, 0x12, 0x20, 0x0a, 0x1c, 0x47, - 0x43, 0x4c, 0x4f, 0x55, 0x44, 0x5f, 0x44, 0x4f, 0x43, 0x4b, 0x45, 0x52, 0x5f, 0x41, 0x55, 0x54, - 0x48, 0x5f, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x55, 0x52, 0x45, 0x10, 0x67, 0x12, 0x19, 0x0a, - 0x15, 0x44, 0x4f, 0x43, 0x4b, 0x45, 0x52, 0x5f, 0x41, 0x55, 0x54, 0x48, 0x5f, 0x43, 0x4f, 0x4e, - 0x46, 0x49, 0x47, 0x55, 0x52, 0x45, 0x10, 0x68, 0x12, 0x18, 0x0a, 0x14, 0x43, 0x48, 0x45, 0x43, - 0x4b, 0x5f, 0x47, 0x43, 0x4c, 0x4f, 0x55, 0x44, 0x5f, 0x50, 0x52, 0x4f, 0x4a, 0x45, 0x43, 0x54, - 0x10, 0x69, 0x12, 0x18, 0x0a, 0x14, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x44, 0x4f, 0x43, 0x4b, - 0x45, 0x52, 0x5f, 0x52, 0x55, 0x4e, 0x4e, 0x49, 0x4e, 0x47, 0x10, 0x6a, 0x12, 0x16, 0x0a, 0x12, - 0x46, 0x49, 0x58, 0x5f, 0x55, 0x53, 0x45, 0x52, 0x5f, 0x42, 0x55, 0x49, 0x4c, 0x44, 0x5f, 0x45, - 0x52, 0x52, 0x10, 0x6b, 0x12, 0x16, 0x0a, 0x12, 0x44, 0x4f, 0x43, 0x4b, 0x45, 0x52, 0x5f, 0x42, - 0x55, 0x49, 0x4c, 0x44, 0x5f, 0x52, 0x45, 0x54, 0x52, 0x59, 0x10, 0x6c, 0x12, 0x22, 0x0a, 0x1e, - 0x46, 0x49, 0x58, 0x5f, 0x43, 0x41, 0x43, 0x48, 0x45, 0x5f, 0x46, 0x52, 0x4f, 0x4d, 0x5f, 0x41, - 0x52, 0x54, 0x49, 0x46, 0x41, 0x43, 0x54, 0x5f, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x10, 0x6d, - 0x12, 0x22, 0x0a, 0x1e, 0x46, 0x49, 0x58, 0x5f, 0x53, 0x4b, 0x41, 0x46, 0x46, 0x4f, 0x4c, 0x44, - 0x5f, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x44, 0x4f, 0x43, 0x4b, 0x45, 0x52, 0x46, 0x49, - 0x4c, 0x45, 0x10, 0x6e, 0x12, 0x20, 0x0a, 0x1c, 0x46, 0x49, 0x58, 0x5f, 0x4a, 0x49, 0x42, 0x5f, - 0x50, 0x4c, 0x55, 0x47, 0x49, 0x4e, 0x5f, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x55, 0x52, 0x41, - 0x54, 0x49, 0x4f, 0x4e, 0x10, 0x6f, 0x12, 0x25, 0x0a, 0x21, 0x46, 0x49, 0x58, 0x5f, 0x44, 0x4f, - 0x43, 0x4b, 0x45, 0x52, 0x5f, 0x4e, 0x45, 0x54, 0x57, 0x4f, 0x52, 0x4b, 0x5f, 0x43, 0x4f, 0x4e, - 0x54, 0x41, 0x49, 0x4e, 0x45, 0x52, 0x5f, 0x4e, 0x41, 0x4d, 0x45, 0x10, 0x70, 0x12, 0x2a, 0x0a, - 0x26, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x44, 0x4f, 0x43, 0x4b, 0x45, 0x52, 0x5f, 0x4e, 0x45, - 0x54, 0x57, 0x4f, 0x52, 0x4b, 0x5f, 0x43, 0x4f, 0x4e, 0x54, 0x41, 0x49, 0x4e, 0x45, 0x52, 0x5f, - 0x52, 0x55, 0x4e, 0x4e, 0x49, 0x4e, 0x47, 0x10, 0x71, 0x12, 0x3a, 0x0a, 0x36, 0x46, 0x49, 0x58, - 0x5f, 0x44, 0x4f, 0x43, 0x4b, 0x45, 0x52, 0x5f, 0x4e, 0x45, 0x54, 0x57, 0x4f, 0x52, 0x4b, 0x5f, - 0x4d, 0x4f, 0x44, 0x45, 0x5f, 0x57, 0x48, 0x45, 0x4e, 0x5f, 0x45, 0x58, 0x54, 0x52, 0x41, 0x43, - 0x54, 0x49, 0x4e, 0x47, 0x5f, 0x43, 0x4f, 0x4e, 0x54, 0x41, 0x49, 0x4e, 0x45, 0x52, 0x5f, 0x4e, - 0x41, 0x4d, 0x45, 0x10, 0x72, 0x12, 0x14, 0x0a, 0x10, 0x52, 0x55, 0x4e, 0x5f, 0x44, 0x4f, 0x43, - 0x4b, 0x45, 0x52, 0x5f, 0x50, 0x52, 0x55, 0x4e, 0x45, 0x10, 0x73, 0x12, 0x14, 0x0a, 0x10, 0x53, - 0x45, 0x54, 0x5f, 0x43, 0x4c, 0x45, 0x41, 0x4e, 0x55, 0x50, 0x5f, 0x46, 0x4c, 0x41, 0x47, 0x10, - 0x74, 0x12, 0x23, 0x0a, 0x1f, 0x42, 0x55, 0x49, 0x4c, 0x44, 0x5f, 0x46, 0x49, 0x58, 0x5f, 0x55, - 0x4e, 0x4b, 0x4e, 0x4f, 0x57, 0x4e, 0x5f, 0x50, 0x4c, 0x41, 0x54, 0x46, 0x4f, 0x52, 0x4d, 0x5f, - 0x46, 0x4c, 0x41, 0x47, 0x10, 0x75, 0x12, 0x1d, 0x0a, 0x18, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, - 0x43, 0x4c, 0x55, 0x53, 0x54, 0x45, 0x52, 0x5f, 0x43, 0x4f, 0x4e, 0x4e, 0x45, 0x43, 0x54, 0x49, - 0x4f, 0x4e, 0x10, 0xc9, 0x01, 0x12, 0x1a, 0x0a, 0x15, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x4d, - 0x49, 0x4e, 0x49, 0x4b, 0x55, 0x42, 0x45, 0x5f, 0x53, 0x54, 0x41, 0x54, 0x55, 0x53, 0x10, 0xca, - 0x01, 0x12, 0x11, 0x0a, 0x0c, 0x49, 0x4e, 0x53, 0x54, 0x41, 0x4c, 0x4c, 0x5f, 0x48, 0x45, 0x4c, - 0x4d, 0x10, 0xcb, 0x01, 0x12, 0x11, 0x0a, 0x0c, 0x55, 0x50, 0x47, 0x52, 0x41, 0x44, 0x45, 0x5f, - 0x48, 0x45, 0x4c, 0x4d, 0x10, 0xcc, 0x01, 0x12, 0x30, 0x0a, 0x2b, 0x46, 0x49, 0x58, 0x5f, 0x53, - 0x4b, 0x41, 0x46, 0x46, 0x4f, 0x4c, 0x44, 0x5f, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x48, - 0x45, 0x4c, 0x4d, 0x5f, 0x41, 0x52, 0x54, 0x49, 0x46, 0x41, 0x43, 0x54, 0x5f, 0x4f, 0x56, 0x45, - 0x52, 0x52, 0x49, 0x44, 0x45, 0x53, 0x10, 0xcd, 0x01, 0x12, 0x13, 0x0a, 0x0e, 0x55, 0x50, 0x47, - 0x52, 0x41, 0x44, 0x45, 0x5f, 0x48, 0x45, 0x4c, 0x4d, 0x33, 0x32, 0x10, 0xce, 0x01, 0x12, 0x2e, - 0x0a, 0x29, 0x46, 0x49, 0x58, 0x5f, 0x53, 0x4b, 0x41, 0x46, 0x46, 0x4f, 0x4c, 0x44, 0x5f, 0x43, - 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x48, 0x45, 0x4c, 0x4d, 0x5f, 0x43, 0x52, 0x45, 0x41, 0x54, - 0x45, 0x5f, 0x4e, 0x41, 0x4d, 0x45, 0x53, 0x50, 0x41, 0x43, 0x45, 0x10, 0xcf, 0x01, 0x12, 0x1a, - 0x0a, 0x15, 0x49, 0x4e, 0x56, 0x41, 0x4c, 0x49, 0x44, 0x5f, 0x4b, 0x50, 0x54, 0x5f, 0x4d, 0x41, - 0x4e, 0x49, 0x46, 0x45, 0x53, 0x54, 0x53, 0x10, 0xd0, 0x01, 0x12, 0x18, 0x0a, 0x13, 0x41, 0x4c, - 0x49, 0x47, 0x4e, 0x5f, 0x4b, 0x50, 0x54, 0x5f, 0x49, 0x4e, 0x56, 0x45, 0x4e, 0x54, 0x4f, 0x52, - 0x59, 0x10, 0xd1, 0x01, 0x12, 0x14, 0x0a, 0x0f, 0x49, 0x4e, 0x53, 0x54, 0x41, 0x4c, 0x4c, 0x5f, - 0x4b, 0x55, 0x42, 0x45, 0x43, 0x54, 0x4c, 0x10, 0xdc, 0x01, 0x12, 0x19, 0x0a, 0x14, 0x43, 0x48, - 0x45, 0x43, 0x4b, 0x5f, 0x43, 0x4f, 0x4e, 0x54, 0x41, 0x49, 0x4e, 0x45, 0x52, 0x5f, 0x4c, 0x4f, - 0x47, 0x53, 0x10, 0xad, 0x02, 0x12, 0x1a, 0x0a, 0x15, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x52, - 0x45, 0x41, 0x44, 0x49, 0x4e, 0x45, 0x53, 0x53, 0x5f, 0x50, 0x52, 0x4f, 0x42, 0x45, 0x10, 0xae, - 0x02, 0x12, 0x1a, 0x0a, 0x15, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x43, 0x4f, 0x4e, 0x54, 0x41, - 0x49, 0x4e, 0x45, 0x52, 0x5f, 0x49, 0x4d, 0x41, 0x47, 0x45, 0x10, 0xaf, 0x02, 0x12, 0x21, 0x0a, - 0x1c, 0x41, 0x44, 0x44, 0x52, 0x45, 0x53, 0x53, 0x5f, 0x4e, 0x4f, 0x44, 0x45, 0x5f, 0x4d, 0x45, - 0x4d, 0x4f, 0x52, 0x59, 0x5f, 0x50, 0x52, 0x45, 0x53, 0x53, 0x55, 0x52, 0x45, 0x10, 0x90, 0x03, - 0x12, 0x1f, 0x0a, 0x1a, 0x41, 0x44, 0x44, 0x52, 0x45, 0x53, 0x53, 0x5f, 0x4e, 0x4f, 0x44, 0x45, - 0x5f, 0x44, 0x49, 0x53, 0x4b, 0x5f, 0x50, 0x52, 0x45, 0x53, 0x53, 0x55, 0x52, 0x45, 0x10, 0x91, - 0x03, 0x12, 0x25, 0x0a, 0x20, 0x41, 0x44, 0x44, 0x52, 0x45, 0x53, 0x53, 0x5f, 0x4e, 0x4f, 0x44, - 0x45, 0x5f, 0x4e, 0x45, 0x54, 0x57, 0x4f, 0x52, 0x4b, 0x5f, 0x55, 0x4e, 0x41, 0x56, 0x41, 0x49, - 0x4c, 0x41, 0x42, 0x4c, 0x45, 0x10, 0x92, 0x03, 0x12, 0x1e, 0x0a, 0x19, 0x41, 0x44, 0x44, 0x52, - 0x45, 0x53, 0x53, 0x5f, 0x4e, 0x4f, 0x44, 0x45, 0x5f, 0x50, 0x49, 0x44, 0x5f, 0x50, 0x52, 0x45, - 0x53, 0x53, 0x55, 0x52, 0x45, 0x10, 0x93, 0x03, 0x12, 0x1f, 0x0a, 0x1a, 0x41, 0x44, 0x44, 0x52, - 0x45, 0x53, 0x53, 0x5f, 0x4e, 0x4f, 0x44, 0x45, 0x5f, 0x55, 0x4e, 0x53, 0x43, 0x48, 0x45, 0x44, - 0x55, 0x4c, 0x41, 0x42, 0x4c, 0x45, 0x10, 0x94, 0x03, 0x12, 0x1d, 0x0a, 0x18, 0x41, 0x44, 0x44, - 0x52, 0x45, 0x53, 0x53, 0x5f, 0x4e, 0x4f, 0x44, 0x45, 0x5f, 0x55, 0x4e, 0x52, 0x45, 0x41, 0x43, - 0x48, 0x41, 0x42, 0x4c, 0x45, 0x10, 0x95, 0x03, 0x12, 0x1b, 0x0a, 0x16, 0x41, 0x44, 0x44, 0x52, - 0x45, 0x53, 0x53, 0x5f, 0x4e, 0x4f, 0x44, 0x45, 0x5f, 0x4e, 0x4f, 0x54, 0x5f, 0x52, 0x45, 0x41, - 0x44, 0x59, 0x10, 0x96, 0x03, 0x12, 0x1e, 0x0a, 0x19, 0x41, 0x44, 0x44, 0x52, 0x45, 0x53, 0x53, - 0x5f, 0x46, 0x41, 0x49, 0x4c, 0x45, 0x44, 0x5f, 0x53, 0x43, 0x48, 0x45, 0x44, 0x55, 0x4c, 0x49, - 0x4e, 0x47, 0x10, 0x97, 0x03, 0x12, 0x1a, 0x0a, 0x15, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x48, - 0x4f, 0x53, 0x54, 0x5f, 0x43, 0x4f, 0x4e, 0x4e, 0x45, 0x43, 0x54, 0x49, 0x4f, 0x4e, 0x10, 0x98, - 0x03, 0x12, 0x13, 0x0a, 0x0e, 0x53, 0x54, 0x41, 0x52, 0x54, 0x5f, 0x4d, 0x49, 0x4e, 0x49, 0x4b, - 0x55, 0x42, 0x45, 0x10, 0xf5, 0x03, 0x12, 0x15, 0x0a, 0x10, 0x55, 0x4e, 0x50, 0x41, 0x55, 0x53, - 0x45, 0x5f, 0x4d, 0x49, 0x4e, 0x49, 0x4b, 0x55, 0x42, 0x45, 0x10, 0xf6, 0x03, 0x12, 0x14, 0x0a, - 0x0f, 0x52, 0x55, 0x4e, 0x5f, 0x44, 0x4f, 0x43, 0x4b, 0x45, 0x52, 0x5f, 0x50, 0x55, 0x4c, 0x4c, - 0x10, 0xa7, 0x04, 0x12, 0x22, 0x0a, 0x1d, 0x53, 0x45, 0x54, 0x5f, 0x52, 0x45, 0x4e, 0x44, 0x45, - 0x52, 0x5f, 0x46, 0x4c, 0x41, 0x47, 0x5f, 0x4f, 0x46, 0x46, 0x4c, 0x49, 0x4e, 0x45, 0x5f, 0x46, - 0x41, 0x4c, 0x53, 0x45, 0x10, 0xd8, 0x04, 0x12, 0x18, 0x0a, 0x13, 0x4b, 0x50, 0x54, 0x46, 0x49, - 0x4c, 0x45, 0x5f, 0x4d, 0x41, 0x4e, 0x55, 0x41, 0x4c, 0x5f, 0x49, 0x4e, 0x49, 0x54, 0x10, 0xd9, - 0x04, 0x12, 0x17, 0x0a, 0x12, 0x4b, 0x50, 0x54, 0x46, 0x49, 0x4c, 0x45, 0x5f, 0x43, 0x48, 0x45, - 0x43, 0x4b, 0x5f, 0x59, 0x41, 0x4d, 0x4c, 0x10, 0xda, 0x04, 0x12, 0x1b, 0x0a, 0x16, 0x43, 0x4f, - 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x46, 0x49, 0x4c, 0x45, 0x5f, - 0x50, 0x41, 0x54, 0x48, 0x10, 0xbc, 0x05, 0x12, 0x27, 0x0a, 0x22, 0x43, 0x4f, 0x4e, 0x46, 0x49, - 0x47, 0x5f, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x44, 0x45, 0x50, 0x45, 0x4e, 0x44, 0x45, 0x4e, - 0x43, 0x59, 0x5f, 0x44, 0x45, 0x46, 0x49, 0x4e, 0x49, 0x54, 0x49, 0x4f, 0x4e, 0x10, 0xbd, 0x05, - 0x12, 0x18, 0x0a, 0x13, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x43, 0x48, 0x41, 0x4e, 0x47, - 0x45, 0x5f, 0x4e, 0x41, 0x4d, 0x45, 0x53, 0x10, 0xbe, 0x05, 0x12, 0x18, 0x0a, 0x13, 0x43, 0x4f, - 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x46, 0x49, 0x4c, 0x54, 0x45, - 0x52, 0x10, 0xbf, 0x05, 0x12, 0x24, 0x0a, 0x1f, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x43, - 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, 0x4c, 0x45, 0x5f, 0x44, 0x45, 0x46, - 0x49, 0x4e, 0x49, 0x54, 0x49, 0x4f, 0x4e, 0x10, 0xc0, 0x05, 0x12, 0x2f, 0x0a, 0x2a, 0x43, 0x4f, - 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x44, 0x45, 0x50, 0x45, 0x4e, - 0x44, 0x45, 0x4e, 0x43, 0x59, 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, 0x4c, 0x45, 0x53, 0x5f, 0x53, - 0x45, 0x4c, 0x45, 0x43, 0x54, 0x49, 0x4f, 0x4e, 0x10, 0xc1, 0x05, 0x12, 0x23, 0x0a, 0x1e, 0x43, - 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x50, 0x52, 0x4f, 0x46, - 0x49, 0x4c, 0x45, 0x5f, 0x53, 0x45, 0x4c, 0x45, 0x43, 0x54, 0x49, 0x4f, 0x4e, 0x10, 0xc2, 0x05, - 0x12, 0x1b, 0x0a, 0x16, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x46, 0x49, 0x58, 0x5f, 0x41, - 0x50, 0x49, 0x5f, 0x56, 0x45, 0x52, 0x53, 0x49, 0x4f, 0x4e, 0x10, 0xc3, 0x05, 0x12, 0x20, 0x0a, - 0x1b, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x41, 0x4c, 0x4c, 0x4f, 0x57, 0x4c, 0x49, 0x53, - 0x54, 0x5f, 0x56, 0x41, 0x4c, 0x49, 0x44, 0x41, 0x54, 0x4f, 0x52, 0x53, 0x10, 0xc4, 0x05, 0x12, - 0x22, 0x0a, 0x1d, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x41, 0x4c, 0x4c, 0x4f, 0x57, 0x4c, - 0x49, 0x53, 0x54, 0x5f, 0x74, 0x72, 0x61, 0x6e, 0x73, 0x66, 0x6f, 0x72, 0x6d, 0x65, 0x72, 0x73, - 0x10, 0xc5, 0x05, 0x12, 0x25, 0x0a, 0x20, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x46, 0x49, - 0x58, 0x5f, 0x4d, 0x49, 0x53, 0x53, 0x49, 0x4e, 0x47, 0x5f, 0x4d, 0x41, 0x4e, 0x49, 0x46, 0x45, - 0x53, 0x54, 0x5f, 0x46, 0x49, 0x4c, 0x45, 0x10, 0xc6, 0x05, 0x12, 0x23, 0x0a, 0x1e, 0x43, 0x4f, - 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x45, 0x4e, 0x41, 0x42, 0x4c, 0x45, 0x5f, 0x52, 0x45, 0x4d, 0x4f, - 0x54, 0x45, 0x5f, 0x52, 0x45, 0x50, 0x4f, 0x5f, 0x53, 0x59, 0x4e, 0x43, 0x10, 0xc7, 0x05, 0x12, - 0x26, 0x0a, 0x21, 0x49, 0x4e, 0x53, 0x50, 0x45, 0x43, 0x54, 0x5f, 0x55, 0x53, 0x45, 0x5f, 0x4d, - 0x4f, 0x44, 0x49, 0x46, 0x59, 0x5f, 0x4f, 0x52, 0x5f, 0x4e, 0x45, 0x57, 0x5f, 0x50, 0x52, 0x4f, - 0x46, 0x49, 0x4c, 0x45, 0x10, 0xa0, 0x06, 0x12, 0x1e, 0x0a, 0x19, 0x49, 0x4e, 0x53, 0x50, 0x45, - 0x43, 0x54, 0x5f, 0x55, 0x53, 0x45, 0x5f, 0x41, 0x44, 0x44, 0x5f, 0x42, 0x55, 0x49, 0x4c, 0x44, - 0x5f, 0x45, 0x4e, 0x56, 0x10, 0xa1, 0x06, 0x12, 0x20, 0x0a, 0x1b, 0x49, 0x4e, 0x53, 0x50, 0x45, - 0x43, 0x54, 0x5f, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x49, 0x4e, 0x50, 0x55, 0x54, 0x5f, 0x50, - 0x52, 0x4f, 0x46, 0x49, 0x4c, 0x45, 0x10, 0xa2, 0x06, 0x12, 0x0f, 0x0a, 0x0a, 0x4f, 0x50, 0x45, - 0x4e, 0x5f, 0x49, 0x53, 0x53, 0x55, 0x45, 0x10, 0x84, 0x07, 0x12, 0x19, 0x0a, 0x14, 0x43, 0x48, - 0x45, 0x43, 0x4b, 0x5f, 0x43, 0x55, 0x53, 0x54, 0x4f, 0x4d, 0x5f, 0x43, 0x4f, 0x4d, 0x4d, 0x41, - 0x4e, 0x44, 0x10, 0xe8, 0x07, 0x12, 0x1f, 0x0a, 0x1a, 0x46, 0x49, 0x58, 0x5f, 0x43, 0x55, 0x53, - 0x54, 0x4f, 0x4d, 0x5f, 0x43, 0x4f, 0x4d, 0x4d, 0x41, 0x4e, 0x44, 0x5f, 0x54, 0x49, 0x4d, 0x45, - 0x4f, 0x55, 0x54, 0x10, 0xe9, 0x07, 0x12, 0x2a, 0x0a, 0x25, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, - 0x43, 0x55, 0x53, 0x54, 0x4f, 0x4d, 0x5f, 0x43, 0x4f, 0x4d, 0x4d, 0x41, 0x4e, 0x44, 0x5f, 0x44, - 0x45, 0x50, 0x45, 0x4e, 0x44, 0x45, 0x4e, 0x43, 0x49, 0x45, 0x53, 0x5f, 0x43, 0x4d, 0x44, 0x10, - 0xea, 0x07, 0x12, 0x2c, 0x0a, 0x27, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x43, 0x55, 0x53, 0x54, + 0x43, 0x48, 0x45, 0x4d, 0x41, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xfa, 0x0a, 0x12, 0x1d, 0x0a, 0x18, + 0x52, 0x45, 0x4e, 0x44, 0x45, 0x52, 0x5f, 0x53, 0x45, 0x54, 0x5f, 0x4e, 0x41, 0x4d, 0x45, 0x53, + 0x50, 0x41, 0x43, 0x45, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xfb, 0x0a, 0x12, 0x25, 0x0a, 0x20, 0x52, + 0x45, 0x4e, 0x44, 0x45, 0x52, 0x5f, 0x4e, 0x41, 0x4d, 0x45, 0x53, 0x50, 0x41, 0x43, 0x45, 0x5f, + 0x41, 0x4c, 0x52, 0x45, 0x41, 0x44, 0x59, 0x5f, 0x53, 0x45, 0x54, 0x5f, 0x45, 0x52, 0x52, 0x10, + 0xfc, 0x0a, 0x12, 0x1c, 0x0a, 0x17, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x46, 0x49, 0x4c, + 0x45, 0x5f, 0x50, 0x41, 0x52, 0x53, 0x49, 0x4e, 0x47, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb1, 0x09, + 0x12, 0x1e, 0x0a, 0x19, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x46, 0x49, 0x4c, 0x45, 0x5f, + 0x4e, 0x4f, 0x54, 0x5f, 0x46, 0x4f, 0x55, 0x4e, 0x44, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb2, 0x09, + 0x12, 0x24, 0x0a, 0x1f, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x44, 0x45, 0x50, 0x45, 0x4e, + 0x44, 0x45, 0x4e, 0x43, 0x59, 0x5f, 0x4e, 0x4f, 0x54, 0x5f, 0x46, 0x4f, 0x55, 0x4e, 0x44, 0x5f, + 0x45, 0x52, 0x52, 0x10, 0xb3, 0x09, 0x12, 0x29, 0x0a, 0x24, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, + 0x5f, 0x44, 0x55, 0x50, 0x4c, 0x49, 0x43, 0x41, 0x54, 0x45, 0x5f, 0x4e, 0x41, 0x4d, 0x45, 0x53, + 0x5f, 0x53, 0x41, 0x4d, 0x45, 0x5f, 0x46, 0x49, 0x4c, 0x45, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb4, + 0x09, 0x12, 0x2c, 0x0a, 0x27, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x44, 0x55, 0x50, 0x4c, + 0x49, 0x43, 0x41, 0x54, 0x45, 0x5f, 0x4e, 0x41, 0x4d, 0x45, 0x53, 0x5f, 0x41, 0x43, 0x52, 0x4f, + 0x53, 0x53, 0x5f, 0x46, 0x49, 0x4c, 0x45, 0x53, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb5, 0x09, 0x12, + 0x1a, 0x0a, 0x15, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x42, 0x41, 0x44, 0x5f, 0x46, 0x49, + 0x4c, 0x54, 0x45, 0x52, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb6, 0x09, 0x12, 0x1a, 0x0a, 0x15, 0x43, + 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x5a, 0x45, 0x52, 0x4f, 0x5f, 0x46, 0x4f, 0x55, 0x4e, 0x44, + 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb7, 0x09, 0x12, 0x1e, 0x0a, 0x19, 0x43, 0x4f, 0x4e, 0x46, 0x49, + 0x47, 0x5f, 0x41, 0x50, 0x50, 0x4c, 0x59, 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, 0x4c, 0x45, 0x53, + 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb8, 0x09, 0x12, 0x1e, 0x0a, 0x19, 0x43, 0x4f, 0x4e, 0x46, 0x49, + 0x47, 0x5f, 0x44, 0x45, 0x46, 0x41, 0x55, 0x4c, 0x54, 0x5f, 0x56, 0x41, 0x4c, 0x55, 0x45, 0x53, + 0x5f, 0x45, 0x52, 0x52, 0x10, 0xb9, 0x09, 0x12, 0x27, 0x0a, 0x22, 0x43, 0x4f, 0x4e, 0x46, 0x49, + 0x47, 0x5f, 0x46, 0x49, 0x4c, 0x45, 0x5f, 0x50, 0x41, 0x54, 0x48, 0x53, 0x5f, 0x53, 0x55, 0x42, + 0x53, 0x54, 0x49, 0x54, 0x55, 0x54, 0x49, 0x4f, 0x4e, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xba, 0x09, + 0x12, 0x2d, 0x0a, 0x28, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x4d, 0x55, 0x4c, 0x54, 0x49, + 0x5f, 0x49, 0x4d, 0x50, 0x4f, 0x52, 0x54, 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, 0x4c, 0x45, 0x5f, + 0x43, 0x4f, 0x4e, 0x46, 0x4c, 0x49, 0x43, 0x54, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xbb, 0x09, 0x12, + 0x22, 0x0a, 0x1d, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, 0x4c, + 0x45, 0x53, 0x5f, 0x4e, 0x4f, 0x54, 0x5f, 0x46, 0x4f, 0x55, 0x4e, 0x44, 0x5f, 0x45, 0x52, 0x52, + 0x10, 0xbc, 0x09, 0x12, 0x23, 0x0a, 0x1e, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x55, 0x4e, + 0x4b, 0x4e, 0x4f, 0x57, 0x4e, 0x5f, 0x41, 0x50, 0x49, 0x5f, 0x56, 0x45, 0x52, 0x53, 0x49, 0x4f, + 0x4e, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xbd, 0x09, 0x12, 0x1d, 0x0a, 0x18, 0x43, 0x4f, 0x4e, 0x46, + 0x49, 0x47, 0x5f, 0x55, 0x4e, 0x4b, 0x4e, 0x4f, 0x57, 0x4e, 0x5f, 0x56, 0x41, 0x4c, 0x49, 0x44, + 0x41, 0x54, 0x4f, 0x52, 0x10, 0xbe, 0x09, 0x12, 0x1f, 0x0a, 0x1a, 0x43, 0x4f, 0x4e, 0x46, 0x49, + 0x47, 0x5f, 0x55, 0x4e, 0x4b, 0x4e, 0x4f, 0x57, 0x4e, 0x5f, 0x54, 0x52, 0x41, 0x4e, 0x53, 0x46, + 0x4f, 0x52, 0x4d, 0x45, 0x52, 0x10, 0xbf, 0x09, 0x12, 0x25, 0x0a, 0x20, 0x43, 0x4f, 0x4e, 0x46, + 0x49, 0x47, 0x5f, 0x4d, 0x49, 0x53, 0x53, 0x49, 0x4e, 0x47, 0x5f, 0x4d, 0x41, 0x4e, 0x49, 0x46, + 0x45, 0x53, 0x54, 0x5f, 0x46, 0x49, 0x4c, 0x45, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xc0, 0x09, 0x12, + 0x2b, 0x0a, 0x26, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x52, 0x45, 0x4d, 0x4f, 0x54, 0x45, + 0x5f, 0x52, 0x45, 0x50, 0x4f, 0x5f, 0x43, 0x41, 0x43, 0x48, 0x45, 0x5f, 0x4e, 0x4f, 0x54, 0x5f, + 0x46, 0x4f, 0x55, 0x4e, 0x44, 0x5f, 0x45, 0x52, 0x52, 0x10, 0xc1, 0x09, 0x12, 0x18, 0x0a, 0x13, + 0x49, 0x4e, 0x53, 0x50, 0x45, 0x43, 0x54, 0x5f, 0x55, 0x4e, 0x4b, 0x4e, 0x4f, 0x57, 0x4e, 0x5f, + 0x45, 0x52, 0x52, 0x10, 0x95, 0x0a, 0x12, 0x29, 0x0a, 0x24, 0x49, 0x4e, 0x53, 0x50, 0x45, 0x43, + 0x54, 0x5f, 0x42, 0x55, 0x49, 0x4c, 0x44, 0x5f, 0x45, 0x4e, 0x56, 0x5f, 0x41, 0x4c, 0x52, 0x45, + 0x41, 0x44, 0x59, 0x5f, 0x45, 0x58, 0x49, 0x53, 0x54, 0x53, 0x5f, 0x45, 0x52, 0x52, 0x10, 0x96, + 0x0a, 0x12, 0x29, 0x0a, 0x24, 0x49, 0x4e, 0x53, 0x50, 0x45, 0x43, 0x54, 0x5f, 0x42, 0x55, 0x49, + 0x4c, 0x44, 0x5f, 0x45, 0x4e, 0x56, 0x5f, 0x49, 0x4e, 0x43, 0x4f, 0x52, 0x52, 0x45, 0x43, 0x54, + 0x5f, 0x54, 0x59, 0x50, 0x45, 0x5f, 0x45, 0x52, 0x52, 0x10, 0x97, 0x0a, 0x12, 0x22, 0x0a, 0x1d, + 0x49, 0x4e, 0x53, 0x50, 0x45, 0x43, 0x54, 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, 0x4c, 0x45, 0x5f, + 0x4e, 0x4f, 0x54, 0x5f, 0x46, 0x4f, 0x55, 0x4e, 0x44, 0x5f, 0x45, 0x52, 0x52, 0x10, 0x98, 0x0a, + 0x12, 0x26, 0x0a, 0x21, 0x50, 0x4f, 0x52, 0x54, 0x5f, 0x46, 0x4f, 0x52, 0x57, 0x41, 0x52, 0x44, + 0x5f, 0x52, 0x55, 0x4e, 0x5f, 0x47, 0x43, 0x4c, 0x4f, 0x55, 0x44, 0x5f, 0x4e, 0x4f, 0x54, 0x5f, + 0x46, 0x4f, 0x55, 0x4e, 0x44, 0x10, 0xc1, 0x0c, 0x12, 0x27, 0x0a, 0x22, 0x50, 0x4f, 0x52, 0x54, + 0x5f, 0x46, 0x4f, 0x52, 0x57, 0x41, 0x52, 0x44, 0x5f, 0x52, 0x55, 0x4e, 0x5f, 0x50, 0x52, 0x4f, + 0x58, 0x59, 0x5f, 0x53, 0x54, 0x41, 0x52, 0x54, 0x5f, 0x45, 0x52, 0x52, 0x4f, 0x52, 0x10, 0xc2, + 0x0c, 0x2a, 0x90, 0x11, 0x0a, 0x0e, 0x53, 0x75, 0x67, 0x67, 0x65, 0x73, 0x74, 0x69, 0x6f, 0x6e, + 0x43, 0x6f, 0x64, 0x65, 0x12, 0x07, 0x0a, 0x03, 0x4e, 0x49, 0x4c, 0x10, 0x00, 0x12, 0x14, 0x0a, + 0x10, 0x41, 0x44, 0x44, 0x5f, 0x44, 0x45, 0x46, 0x41, 0x55, 0x4c, 0x54, 0x5f, 0x52, 0x45, 0x50, + 0x4f, 0x10, 0x64, 0x12, 0x16, 0x0a, 0x12, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x44, 0x45, 0x46, + 0x41, 0x55, 0x4c, 0x54, 0x5f, 0x52, 0x45, 0x50, 0x4f, 0x10, 0x65, 0x12, 0x24, 0x0a, 0x20, 0x43, + 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x44, 0x45, 0x46, 0x41, 0x55, 0x4c, 0x54, 0x5f, 0x52, 0x45, 0x50, + 0x4f, 0x5f, 0x47, 0x4c, 0x4f, 0x42, 0x41, 0x4c, 0x5f, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x10, + 0x66, 0x12, 0x20, 0x0a, 0x1c, 0x47, 0x43, 0x4c, 0x4f, 0x55, 0x44, 0x5f, 0x44, 0x4f, 0x43, 0x4b, + 0x45, 0x52, 0x5f, 0x41, 0x55, 0x54, 0x48, 0x5f, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x55, 0x52, + 0x45, 0x10, 0x67, 0x12, 0x19, 0x0a, 0x15, 0x44, 0x4f, 0x43, 0x4b, 0x45, 0x52, 0x5f, 0x41, 0x55, + 0x54, 0x48, 0x5f, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x55, 0x52, 0x45, 0x10, 0x68, 0x12, 0x18, + 0x0a, 0x14, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x47, 0x43, 0x4c, 0x4f, 0x55, 0x44, 0x5f, 0x50, + 0x52, 0x4f, 0x4a, 0x45, 0x43, 0x54, 0x10, 0x69, 0x12, 0x18, 0x0a, 0x14, 0x43, 0x48, 0x45, 0x43, + 0x4b, 0x5f, 0x44, 0x4f, 0x43, 0x4b, 0x45, 0x52, 0x5f, 0x52, 0x55, 0x4e, 0x4e, 0x49, 0x4e, 0x47, + 0x10, 0x6a, 0x12, 0x16, 0x0a, 0x12, 0x46, 0x49, 0x58, 0x5f, 0x55, 0x53, 0x45, 0x52, 0x5f, 0x42, + 0x55, 0x49, 0x4c, 0x44, 0x5f, 0x45, 0x52, 0x52, 0x10, 0x6b, 0x12, 0x16, 0x0a, 0x12, 0x44, 0x4f, + 0x43, 0x4b, 0x45, 0x52, 0x5f, 0x42, 0x55, 0x49, 0x4c, 0x44, 0x5f, 0x52, 0x45, 0x54, 0x52, 0x59, + 0x10, 0x6c, 0x12, 0x22, 0x0a, 0x1e, 0x46, 0x49, 0x58, 0x5f, 0x43, 0x41, 0x43, 0x48, 0x45, 0x5f, + 0x46, 0x52, 0x4f, 0x4d, 0x5f, 0x41, 0x52, 0x54, 0x49, 0x46, 0x41, 0x43, 0x54, 0x5f, 0x43, 0x4f, + 0x4e, 0x46, 0x49, 0x47, 0x10, 0x6d, 0x12, 0x22, 0x0a, 0x1e, 0x46, 0x49, 0x58, 0x5f, 0x53, 0x4b, + 0x41, 0x46, 0x46, 0x4f, 0x4c, 0x44, 0x5f, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x44, 0x4f, + 0x43, 0x4b, 0x45, 0x52, 0x46, 0x49, 0x4c, 0x45, 0x10, 0x6e, 0x12, 0x20, 0x0a, 0x1c, 0x46, 0x49, + 0x58, 0x5f, 0x4a, 0x49, 0x42, 0x5f, 0x50, 0x4c, 0x55, 0x47, 0x49, 0x4e, 0x5f, 0x43, 0x4f, 0x4e, + 0x46, 0x49, 0x47, 0x55, 0x52, 0x41, 0x54, 0x49, 0x4f, 0x4e, 0x10, 0x6f, 0x12, 0x25, 0x0a, 0x21, + 0x46, 0x49, 0x58, 0x5f, 0x44, 0x4f, 0x43, 0x4b, 0x45, 0x52, 0x5f, 0x4e, 0x45, 0x54, 0x57, 0x4f, + 0x52, 0x4b, 0x5f, 0x43, 0x4f, 0x4e, 0x54, 0x41, 0x49, 0x4e, 0x45, 0x52, 0x5f, 0x4e, 0x41, 0x4d, + 0x45, 0x10, 0x70, 0x12, 0x2a, 0x0a, 0x26, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x44, 0x4f, 0x43, + 0x4b, 0x45, 0x52, 0x5f, 0x4e, 0x45, 0x54, 0x57, 0x4f, 0x52, 0x4b, 0x5f, 0x43, 0x4f, 0x4e, 0x54, + 0x41, 0x49, 0x4e, 0x45, 0x52, 0x5f, 0x52, 0x55, 0x4e, 0x4e, 0x49, 0x4e, 0x47, 0x10, 0x71, 0x12, + 0x3a, 0x0a, 0x36, 0x46, 0x49, 0x58, 0x5f, 0x44, 0x4f, 0x43, 0x4b, 0x45, 0x52, 0x5f, 0x4e, 0x45, + 0x54, 0x57, 0x4f, 0x52, 0x4b, 0x5f, 0x4d, 0x4f, 0x44, 0x45, 0x5f, 0x57, 0x48, 0x45, 0x4e, 0x5f, + 0x45, 0x58, 0x54, 0x52, 0x41, 0x43, 0x54, 0x49, 0x4e, 0x47, 0x5f, 0x43, 0x4f, 0x4e, 0x54, 0x41, + 0x49, 0x4e, 0x45, 0x52, 0x5f, 0x4e, 0x41, 0x4d, 0x45, 0x10, 0x72, 0x12, 0x14, 0x0a, 0x10, 0x52, + 0x55, 0x4e, 0x5f, 0x44, 0x4f, 0x43, 0x4b, 0x45, 0x52, 0x5f, 0x50, 0x52, 0x55, 0x4e, 0x45, 0x10, + 0x73, 0x12, 0x14, 0x0a, 0x10, 0x53, 0x45, 0x54, 0x5f, 0x43, 0x4c, 0x45, 0x41, 0x4e, 0x55, 0x50, + 0x5f, 0x46, 0x4c, 0x41, 0x47, 0x10, 0x74, 0x12, 0x23, 0x0a, 0x1f, 0x42, 0x55, 0x49, 0x4c, 0x44, + 0x5f, 0x46, 0x49, 0x58, 0x5f, 0x55, 0x4e, 0x4b, 0x4e, 0x4f, 0x57, 0x4e, 0x5f, 0x50, 0x4c, 0x41, + 0x54, 0x46, 0x4f, 0x52, 0x4d, 0x5f, 0x46, 0x4c, 0x41, 0x47, 0x10, 0x75, 0x12, 0x1d, 0x0a, 0x18, + 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x43, 0x4c, 0x55, 0x53, 0x54, 0x45, 0x52, 0x5f, 0x43, 0x4f, + 0x4e, 0x4e, 0x45, 0x43, 0x54, 0x49, 0x4f, 0x4e, 0x10, 0xc9, 0x01, 0x12, 0x1a, 0x0a, 0x15, 0x43, + 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x4d, 0x49, 0x4e, 0x49, 0x4b, 0x55, 0x42, 0x45, 0x5f, 0x53, 0x54, + 0x41, 0x54, 0x55, 0x53, 0x10, 0xca, 0x01, 0x12, 0x11, 0x0a, 0x0c, 0x49, 0x4e, 0x53, 0x54, 0x41, + 0x4c, 0x4c, 0x5f, 0x48, 0x45, 0x4c, 0x4d, 0x10, 0xcb, 0x01, 0x12, 0x11, 0x0a, 0x0c, 0x55, 0x50, + 0x47, 0x52, 0x41, 0x44, 0x45, 0x5f, 0x48, 0x45, 0x4c, 0x4d, 0x10, 0xcc, 0x01, 0x12, 0x30, 0x0a, + 0x2b, 0x46, 0x49, 0x58, 0x5f, 0x53, 0x4b, 0x41, 0x46, 0x46, 0x4f, 0x4c, 0x44, 0x5f, 0x43, 0x4f, + 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x48, 0x45, 0x4c, 0x4d, 0x5f, 0x41, 0x52, 0x54, 0x49, 0x46, 0x41, + 0x43, 0x54, 0x5f, 0x4f, 0x56, 0x45, 0x52, 0x52, 0x49, 0x44, 0x45, 0x53, 0x10, 0xcd, 0x01, 0x12, + 0x13, 0x0a, 0x0e, 0x55, 0x50, 0x47, 0x52, 0x41, 0x44, 0x45, 0x5f, 0x48, 0x45, 0x4c, 0x4d, 0x33, + 0x32, 0x10, 0xce, 0x01, 0x12, 0x2e, 0x0a, 0x29, 0x46, 0x49, 0x58, 0x5f, 0x53, 0x4b, 0x41, 0x46, + 0x46, 0x4f, 0x4c, 0x44, 0x5f, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x48, 0x45, 0x4c, 0x4d, + 0x5f, 0x43, 0x52, 0x45, 0x41, 0x54, 0x45, 0x5f, 0x4e, 0x41, 0x4d, 0x45, 0x53, 0x50, 0x41, 0x43, + 0x45, 0x10, 0xcf, 0x01, 0x12, 0x1a, 0x0a, 0x15, 0x49, 0x4e, 0x56, 0x41, 0x4c, 0x49, 0x44, 0x5f, + 0x4b, 0x50, 0x54, 0x5f, 0x4d, 0x41, 0x4e, 0x49, 0x46, 0x45, 0x53, 0x54, 0x53, 0x10, 0xd0, 0x01, + 0x12, 0x18, 0x0a, 0x13, 0x41, 0x4c, 0x49, 0x47, 0x4e, 0x5f, 0x4b, 0x50, 0x54, 0x5f, 0x49, 0x4e, + 0x56, 0x45, 0x4e, 0x54, 0x4f, 0x52, 0x59, 0x10, 0xd1, 0x01, 0x12, 0x14, 0x0a, 0x0f, 0x49, 0x4e, + 0x53, 0x54, 0x41, 0x4c, 0x4c, 0x5f, 0x4b, 0x55, 0x42, 0x45, 0x43, 0x54, 0x4c, 0x10, 0xdc, 0x01, + 0x12, 0x19, 0x0a, 0x14, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x43, 0x4f, 0x4e, 0x54, 0x41, 0x49, + 0x4e, 0x45, 0x52, 0x5f, 0x4c, 0x4f, 0x47, 0x53, 0x10, 0xad, 0x02, 0x12, 0x1a, 0x0a, 0x15, 0x43, + 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x52, 0x45, 0x41, 0x44, 0x49, 0x4e, 0x45, 0x53, 0x53, 0x5f, 0x50, + 0x52, 0x4f, 0x42, 0x45, 0x10, 0xae, 0x02, 0x12, 0x1a, 0x0a, 0x15, 0x43, 0x48, 0x45, 0x43, 0x4b, + 0x5f, 0x43, 0x4f, 0x4e, 0x54, 0x41, 0x49, 0x4e, 0x45, 0x52, 0x5f, 0x49, 0x4d, 0x41, 0x47, 0x45, + 0x10, 0xaf, 0x02, 0x12, 0x21, 0x0a, 0x1c, 0x41, 0x44, 0x44, 0x52, 0x45, 0x53, 0x53, 0x5f, 0x4e, + 0x4f, 0x44, 0x45, 0x5f, 0x4d, 0x45, 0x4d, 0x4f, 0x52, 0x59, 0x5f, 0x50, 0x52, 0x45, 0x53, 0x53, + 0x55, 0x52, 0x45, 0x10, 0x90, 0x03, 0x12, 0x1f, 0x0a, 0x1a, 0x41, 0x44, 0x44, 0x52, 0x45, 0x53, + 0x53, 0x5f, 0x4e, 0x4f, 0x44, 0x45, 0x5f, 0x44, 0x49, 0x53, 0x4b, 0x5f, 0x50, 0x52, 0x45, 0x53, + 0x53, 0x55, 0x52, 0x45, 0x10, 0x91, 0x03, 0x12, 0x25, 0x0a, 0x20, 0x41, 0x44, 0x44, 0x52, 0x45, + 0x53, 0x53, 0x5f, 0x4e, 0x4f, 0x44, 0x45, 0x5f, 0x4e, 0x45, 0x54, 0x57, 0x4f, 0x52, 0x4b, 0x5f, + 0x55, 0x4e, 0x41, 0x56, 0x41, 0x49, 0x4c, 0x41, 0x42, 0x4c, 0x45, 0x10, 0x92, 0x03, 0x12, 0x1e, + 0x0a, 0x19, 0x41, 0x44, 0x44, 0x52, 0x45, 0x53, 0x53, 0x5f, 0x4e, 0x4f, 0x44, 0x45, 0x5f, 0x50, + 0x49, 0x44, 0x5f, 0x50, 0x52, 0x45, 0x53, 0x53, 0x55, 0x52, 0x45, 0x10, 0x93, 0x03, 0x12, 0x1f, + 0x0a, 0x1a, 0x41, 0x44, 0x44, 0x52, 0x45, 0x53, 0x53, 0x5f, 0x4e, 0x4f, 0x44, 0x45, 0x5f, 0x55, + 0x4e, 0x53, 0x43, 0x48, 0x45, 0x44, 0x55, 0x4c, 0x41, 0x42, 0x4c, 0x45, 0x10, 0x94, 0x03, 0x12, + 0x1d, 0x0a, 0x18, 0x41, 0x44, 0x44, 0x52, 0x45, 0x53, 0x53, 0x5f, 0x4e, 0x4f, 0x44, 0x45, 0x5f, + 0x55, 0x4e, 0x52, 0x45, 0x41, 0x43, 0x48, 0x41, 0x42, 0x4c, 0x45, 0x10, 0x95, 0x03, 0x12, 0x1b, + 0x0a, 0x16, 0x41, 0x44, 0x44, 0x52, 0x45, 0x53, 0x53, 0x5f, 0x4e, 0x4f, 0x44, 0x45, 0x5f, 0x4e, + 0x4f, 0x54, 0x5f, 0x52, 0x45, 0x41, 0x44, 0x59, 0x10, 0x96, 0x03, 0x12, 0x1e, 0x0a, 0x19, 0x41, + 0x44, 0x44, 0x52, 0x45, 0x53, 0x53, 0x5f, 0x46, 0x41, 0x49, 0x4c, 0x45, 0x44, 0x5f, 0x53, 0x43, + 0x48, 0x45, 0x44, 0x55, 0x4c, 0x49, 0x4e, 0x47, 0x10, 0x97, 0x03, 0x12, 0x1a, 0x0a, 0x15, 0x43, + 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x48, 0x4f, 0x53, 0x54, 0x5f, 0x43, 0x4f, 0x4e, 0x4e, 0x45, 0x43, + 0x54, 0x49, 0x4f, 0x4e, 0x10, 0x98, 0x03, 0x12, 0x13, 0x0a, 0x0e, 0x53, 0x54, 0x41, 0x52, 0x54, + 0x5f, 0x4d, 0x49, 0x4e, 0x49, 0x4b, 0x55, 0x42, 0x45, 0x10, 0xf5, 0x03, 0x12, 0x15, 0x0a, 0x10, + 0x55, 0x4e, 0x50, 0x41, 0x55, 0x53, 0x45, 0x5f, 0x4d, 0x49, 0x4e, 0x49, 0x4b, 0x55, 0x42, 0x45, + 0x10, 0xf6, 0x03, 0x12, 0x14, 0x0a, 0x0f, 0x52, 0x55, 0x4e, 0x5f, 0x44, 0x4f, 0x43, 0x4b, 0x45, + 0x52, 0x5f, 0x50, 0x55, 0x4c, 0x4c, 0x10, 0xa7, 0x04, 0x12, 0x22, 0x0a, 0x1d, 0x53, 0x45, 0x54, + 0x5f, 0x52, 0x45, 0x4e, 0x44, 0x45, 0x52, 0x5f, 0x46, 0x4c, 0x41, 0x47, 0x5f, 0x4f, 0x46, 0x46, + 0x4c, 0x49, 0x4e, 0x45, 0x5f, 0x46, 0x41, 0x4c, 0x53, 0x45, 0x10, 0xd8, 0x04, 0x12, 0x18, 0x0a, + 0x13, 0x4b, 0x50, 0x54, 0x46, 0x49, 0x4c, 0x45, 0x5f, 0x4d, 0x41, 0x4e, 0x55, 0x41, 0x4c, 0x5f, + 0x49, 0x4e, 0x49, 0x54, 0x10, 0xd9, 0x04, 0x12, 0x17, 0x0a, 0x12, 0x4b, 0x50, 0x54, 0x46, 0x49, + 0x4c, 0x45, 0x5f, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x59, 0x41, 0x4d, 0x4c, 0x10, 0xda, 0x04, + 0x12, 0x24, 0x0a, 0x1f, 0x52, 0x45, 0x4d, 0x4f, 0x56, 0x45, 0x5f, 0x4e, 0x41, 0x4d, 0x45, 0x53, + 0x50, 0x41, 0x43, 0x45, 0x5f, 0x46, 0x52, 0x4f, 0x4d, 0x5f, 0x4d, 0x41, 0x4e, 0x49, 0x46, 0x45, + 0x53, 0x54, 0x53, 0x10, 0xdb, 0x04, 0x12, 0x1b, 0x0a, 0x16, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, + 0x5f, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x46, 0x49, 0x4c, 0x45, 0x5f, 0x50, 0x41, 0x54, 0x48, + 0x10, 0xbc, 0x05, 0x12, 0x27, 0x0a, 0x22, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x43, 0x48, + 0x45, 0x43, 0x4b, 0x5f, 0x44, 0x45, 0x50, 0x45, 0x4e, 0x44, 0x45, 0x4e, 0x43, 0x59, 0x5f, 0x44, + 0x45, 0x46, 0x49, 0x4e, 0x49, 0x54, 0x49, 0x4f, 0x4e, 0x10, 0xbd, 0x05, 0x12, 0x18, 0x0a, 0x13, + 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x43, 0x48, 0x41, 0x4e, 0x47, 0x45, 0x5f, 0x4e, 0x41, + 0x4d, 0x45, 0x53, 0x10, 0xbe, 0x05, 0x12, 0x18, 0x0a, 0x13, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, + 0x5f, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x46, 0x49, 0x4c, 0x54, 0x45, 0x52, 0x10, 0xbf, 0x05, + 0x12, 0x24, 0x0a, 0x1f, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x43, 0x48, 0x45, 0x43, 0x4b, + 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, 0x4c, 0x45, 0x5f, 0x44, 0x45, 0x46, 0x49, 0x4e, 0x49, 0x54, + 0x49, 0x4f, 0x4e, 0x10, 0xc0, 0x05, 0x12, 0x2f, 0x0a, 0x2a, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, + 0x5f, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x44, 0x45, 0x50, 0x45, 0x4e, 0x44, 0x45, 0x4e, 0x43, + 0x59, 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, 0x4c, 0x45, 0x53, 0x5f, 0x53, 0x45, 0x4c, 0x45, 0x43, + 0x54, 0x49, 0x4f, 0x4e, 0x10, 0xc1, 0x05, 0x12, 0x23, 0x0a, 0x1e, 0x43, 0x4f, 0x4e, 0x46, 0x49, + 0x47, 0x5f, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, 0x4c, 0x45, 0x5f, + 0x53, 0x45, 0x4c, 0x45, 0x43, 0x54, 0x49, 0x4f, 0x4e, 0x10, 0xc2, 0x05, 0x12, 0x1b, 0x0a, 0x16, + 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x46, 0x49, 0x58, 0x5f, 0x41, 0x50, 0x49, 0x5f, 0x56, + 0x45, 0x52, 0x53, 0x49, 0x4f, 0x4e, 0x10, 0xc3, 0x05, 0x12, 0x20, 0x0a, 0x1b, 0x43, 0x4f, 0x4e, + 0x46, 0x49, 0x47, 0x5f, 0x41, 0x4c, 0x4c, 0x4f, 0x57, 0x4c, 0x49, 0x53, 0x54, 0x5f, 0x56, 0x41, + 0x4c, 0x49, 0x44, 0x41, 0x54, 0x4f, 0x52, 0x53, 0x10, 0xc4, 0x05, 0x12, 0x22, 0x0a, 0x1d, 0x43, + 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x41, 0x4c, 0x4c, 0x4f, 0x57, 0x4c, 0x49, 0x53, 0x54, 0x5f, + 0x74, 0x72, 0x61, 0x6e, 0x73, 0x66, 0x6f, 0x72, 0x6d, 0x65, 0x72, 0x73, 0x10, 0xc5, 0x05, 0x12, + 0x25, 0x0a, 0x20, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, 0x5f, 0x46, 0x49, 0x58, 0x5f, 0x4d, 0x49, + 0x53, 0x53, 0x49, 0x4e, 0x47, 0x5f, 0x4d, 0x41, 0x4e, 0x49, 0x46, 0x45, 0x53, 0x54, 0x5f, 0x46, + 0x49, 0x4c, 0x45, 0x10, 0xc6, 0x05, 0x12, 0x23, 0x0a, 0x1e, 0x43, 0x4f, 0x4e, 0x46, 0x49, 0x47, + 0x5f, 0x45, 0x4e, 0x41, 0x42, 0x4c, 0x45, 0x5f, 0x52, 0x45, 0x4d, 0x4f, 0x54, 0x45, 0x5f, 0x52, + 0x45, 0x50, 0x4f, 0x5f, 0x53, 0x59, 0x4e, 0x43, 0x10, 0xc7, 0x05, 0x12, 0x26, 0x0a, 0x21, 0x49, + 0x4e, 0x53, 0x50, 0x45, 0x43, 0x54, 0x5f, 0x55, 0x53, 0x45, 0x5f, 0x4d, 0x4f, 0x44, 0x49, 0x46, + 0x59, 0x5f, 0x4f, 0x52, 0x5f, 0x4e, 0x45, 0x57, 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, 0x4c, 0x45, + 0x10, 0xa0, 0x06, 0x12, 0x1e, 0x0a, 0x19, 0x49, 0x4e, 0x53, 0x50, 0x45, 0x43, 0x54, 0x5f, 0x55, + 0x53, 0x45, 0x5f, 0x41, 0x44, 0x44, 0x5f, 0x42, 0x55, 0x49, 0x4c, 0x44, 0x5f, 0x45, 0x4e, 0x56, + 0x10, 0xa1, 0x06, 0x12, 0x20, 0x0a, 0x1b, 0x49, 0x4e, 0x53, 0x50, 0x45, 0x43, 0x54, 0x5f, 0x43, + 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x49, 0x4e, 0x50, 0x55, 0x54, 0x5f, 0x50, 0x52, 0x4f, 0x46, 0x49, + 0x4c, 0x45, 0x10, 0xa2, 0x06, 0x12, 0x0f, 0x0a, 0x0a, 0x4f, 0x50, 0x45, 0x4e, 0x5f, 0x49, 0x53, + 0x53, 0x55, 0x45, 0x10, 0x84, 0x07, 0x12, 0x19, 0x0a, 0x14, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, + 0x43, 0x55, 0x53, 0x54, 0x4f, 0x4d, 0x5f, 0x43, 0x4f, 0x4d, 0x4d, 0x41, 0x4e, 0x44, 0x10, 0xe8, + 0x07, 0x12, 0x1f, 0x0a, 0x1a, 0x46, 0x49, 0x58, 0x5f, 0x43, 0x55, 0x53, 0x54, 0x4f, 0x4d, 0x5f, + 0x43, 0x4f, 0x4d, 0x4d, 0x41, 0x4e, 0x44, 0x5f, 0x54, 0x49, 0x4d, 0x45, 0x4f, 0x55, 0x54, 0x10, + 0xe9, 0x07, 0x12, 0x2a, 0x0a, 0x25, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x43, 0x55, 0x53, 0x54, 0x4f, 0x4d, 0x5f, 0x43, 0x4f, 0x4d, 0x4d, 0x41, 0x4e, 0x44, 0x5f, 0x44, 0x45, 0x50, 0x45, 0x4e, - 0x44, 0x45, 0x4e, 0x43, 0x49, 0x45, 0x53, 0x5f, 0x50, 0x41, 0x54, 0x48, 0x53, 0x10, 0xeb, 0x07, - 0x12, 0x26, 0x0a, 0x21, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x54, 0x45, 0x53, 0x54, 0x5f, 0x43, - 0x4f, 0x4d, 0x4d, 0x41, 0x4e, 0x44, 0x5f, 0x41, 0x4e, 0x44, 0x5f, 0x49, 0x4d, 0x41, 0x47, 0x45, - 0x5f, 0x4e, 0x41, 0x4d, 0x45, 0x10, 0xec, 0x07, 0x42, 0x36, 0x5a, 0x34, 0x67, 0x69, 0x74, 0x68, - 0x75, 0x62, 0x2e, 0x63, 0x6f, 0x6d, 0x2f, 0x47, 0x6f, 0x6f, 0x67, 0x6c, 0x65, 0x43, 0x6f, 0x6e, - 0x74, 0x61, 0x69, 0x6e, 0x65, 0x72, 0x54, 0x6f, 0x6f, 0x6c, 0x73, 0x2f, 0x73, 0x6b, 0x61, 0x66, - 0x66, 0x6f, 0x6c, 0x64, 0x2f, 0x70, 0x72, 0x6f, 0x74, 0x6f, 0x2f, 0x65, 0x6e, 0x75, 0x6d, 0x73, - 0x62, 0x06, 0x70, 0x72, 0x6f, 0x74, 0x6f, 0x33, + 0x44, 0x45, 0x4e, 0x43, 0x49, 0x45, 0x53, 0x5f, 0x43, 0x4d, 0x44, 0x10, 0xea, 0x07, 0x12, 0x2c, + 0x0a, 0x27, 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x43, 0x55, 0x53, 0x54, 0x4f, 0x4d, 0x5f, 0x43, + 0x4f, 0x4d, 0x4d, 0x41, 0x4e, 0x44, 0x5f, 0x44, 0x45, 0x50, 0x45, 0x4e, 0x44, 0x45, 0x4e, 0x43, + 0x49, 0x45, 0x53, 0x5f, 0x50, 0x41, 0x54, 0x48, 0x53, 0x10, 0xeb, 0x07, 0x12, 0x26, 0x0a, 0x21, + 0x43, 0x48, 0x45, 0x43, 0x4b, 0x5f, 0x54, 0x45, 0x53, 0x54, 0x5f, 0x43, 0x4f, 0x4d, 0x4d, 0x41, + 0x4e, 0x44, 0x5f, 0x41, 0x4e, 0x44, 0x5f, 0x49, 0x4d, 0x41, 0x47, 0x45, 0x5f, 0x4e, 0x41, 0x4d, + 0x45, 0x10, 0xec, 0x07, 0x42, 0x36, 0x5a, 0x34, 0x67, 0x69, 0x74, 0x68, 0x75, 0x62, 0x2e, 0x63, + 0x6f, 0x6d, 0x2f, 0x47, 0x6f, 0x6f, 0x67, 0x6c, 0x65, 0x43, 0x6f, 0x6e, 0x74, 0x61, 0x69, 0x6e, + 0x65, 0x72, 0x54, 0x6f, 0x6f, 0x6c, 0x73, 0x2f, 0x73, 0x6b, 0x61, 0x66, 0x66, 0x6f, 0x6c, 0x64, + 0x2f, 0x70, 0x72, 0x6f, 0x74, 0x6f, 0x2f, 0x65, 0x6e, 0x75, 0x6d, 0x73, 0x62, 0x06, 0x70, 0x72, + 0x6f, 0x74, 0x6f, 0x33, } var ( diff --git a/proto/enums/enums.proto b/proto/enums/enums.proto index 537799d1332..b450afdd840 100644 --- a/proto/enums/enums.proto +++ b/proto/enums/enums.proto @@ -495,6 +495,10 @@ enum StatusCode { RENDER_KPTFILE_INVALID_YAML_ERR = 1401; // The Kptfile is not a valid API schema RENDER_KPTFILE_INVALID_SCHEMA_ERR = 1402; + // Error setting namespace. + RENDER_SET_NAMESPACE_ERR = 1403; + // Namespace is already set. + RENDER_NAMESPACE_ALREADY_SET_ERR = 1404; // Configuration errors @@ -673,6 +677,8 @@ enum SuggestionCode { KPTFILE_MANUAL_INIT = 601; // Check if the Kptfile is correct. KPTFILE_CHECK_YAML = 602; + // Remove namespace from manifests + REMOVE_NAMESPACE_FROM_MANIFESTS = 603; // Configuration error suggestion codes diff --git a/proto/v1/skaffold.pb.go b/proto/v1/skaffold.pb.go index 2b8c04cb8e0..00bdfd42ad4 100644 --- a/proto/v1/skaffold.pb.go +++ b/proto/v1/skaffold.pb.go @@ -273,6 +273,8 @@ const StatusCode_TEST_CUSTOM_CMD_RETRIEVE_ERR = enums.StatusCode_TEST_CUSTOM_CMD const StatusCode_RENDER_KPTFILE_INIT_ERR = enums.StatusCode_RENDER_KPTFILE_INIT_ERR const StatusCode_RENDER_KPTFILE_INVALID_YAML_ERR = enums.StatusCode_RENDER_KPTFILE_INVALID_YAML_ERR const StatusCode_RENDER_KPTFILE_INVALID_SCHEMA_ERR = enums.StatusCode_RENDER_KPTFILE_INVALID_SCHEMA_ERR +const StatusCode_RENDER_SET_NAMESPACE_ERR = enums.StatusCode_RENDER_SET_NAMESPACE_ERR +const StatusCode_RENDER_NAMESPACE_ALREADY_SET_ERR = enums.StatusCode_RENDER_NAMESPACE_ALREADY_SET_ERR const StatusCode_CONFIG_FILE_PARSING_ERR = enums.StatusCode_CONFIG_FILE_PARSING_ERR const StatusCode_CONFIG_FILE_NOT_FOUND_ERR = enums.StatusCode_CONFIG_FILE_NOT_FOUND_ERR const StatusCode_CONFIG_DEPENDENCY_NOT_FOUND_ERR = enums.StatusCode_CONFIG_DEPENDENCY_NOT_FOUND_ERR @@ -349,6 +351,7 @@ const SuggestionCode_RUN_DOCKER_PULL = enums.SuggestionCode_RUN_DOCKER_PULL const SuggestionCode_SET_RENDER_FLAG_OFFLINE_FALSE = enums.SuggestionCode_SET_RENDER_FLAG_OFFLINE_FALSE const SuggestionCode_KPTFILE_MANUAL_INIT = enums.SuggestionCode_KPTFILE_MANUAL_INIT const SuggestionCode_KPTFILE_CHECK_YAML = enums.SuggestionCode_KPTFILE_CHECK_YAML +const SuggestionCode_REMOVE_NAMESPACE_FROM_MANIFESTS = enums.SuggestionCode_REMOVE_NAMESPACE_FROM_MANIFESTS const SuggestionCode_CONFIG_CHECK_FILE_PATH = enums.SuggestionCode_CONFIG_CHECK_FILE_PATH const SuggestionCode_CONFIG_CHECK_DEPENDENCY_DEFINITION = enums.SuggestionCode_CONFIG_CHECK_DEPENDENCY_DEFINITION const SuggestionCode_CONFIG_CHANGE_NAMES = enums.SuggestionCode_CONFIG_CHANGE_NAMES diff --git a/proto/v2/skaffold.pb.go b/proto/v2/skaffold.pb.go index 7faa8b4a9ff..036dee8632e 100644 --- a/proto/v2/skaffold.pb.go +++ b/proto/v2/skaffold.pb.go @@ -273,6 +273,8 @@ const StatusCode_TEST_CUSTOM_CMD_RETRIEVE_ERR = enums.StatusCode_TEST_CUSTOM_CMD const StatusCode_RENDER_KPTFILE_INIT_ERR = enums.StatusCode_RENDER_KPTFILE_INIT_ERR const StatusCode_RENDER_KPTFILE_INVALID_YAML_ERR = enums.StatusCode_RENDER_KPTFILE_INVALID_YAML_ERR const StatusCode_RENDER_KPTFILE_INVALID_SCHEMA_ERR = enums.StatusCode_RENDER_KPTFILE_INVALID_SCHEMA_ERR +const StatusCode_RENDER_SET_NAMESPACE_ERR = enums.StatusCode_RENDER_SET_NAMESPACE_ERR +const StatusCode_RENDER_NAMESPACE_ALREADY_SET_ERR = enums.StatusCode_RENDER_NAMESPACE_ALREADY_SET_ERR const StatusCode_CONFIG_FILE_PARSING_ERR = enums.StatusCode_CONFIG_FILE_PARSING_ERR const StatusCode_CONFIG_FILE_NOT_FOUND_ERR = enums.StatusCode_CONFIG_FILE_NOT_FOUND_ERR const StatusCode_CONFIG_DEPENDENCY_NOT_FOUND_ERR = enums.StatusCode_CONFIG_DEPENDENCY_NOT_FOUND_ERR @@ -349,6 +351,7 @@ const SuggestionCode_RUN_DOCKER_PULL = enums.SuggestionCode_RUN_DOCKER_PULL const SuggestionCode_SET_RENDER_FLAG_OFFLINE_FALSE = enums.SuggestionCode_SET_RENDER_FLAG_OFFLINE_FALSE const SuggestionCode_KPTFILE_MANUAL_INIT = enums.SuggestionCode_KPTFILE_MANUAL_INIT const SuggestionCode_KPTFILE_CHECK_YAML = enums.SuggestionCode_KPTFILE_CHECK_YAML +const SuggestionCode_REMOVE_NAMESPACE_FROM_MANIFESTS = enums.SuggestionCode_REMOVE_NAMESPACE_FROM_MANIFESTS const SuggestionCode_CONFIG_CHECK_FILE_PATH = enums.SuggestionCode_CONFIG_CHECK_FILE_PATH const SuggestionCode_CONFIG_CHECK_DEPENDENCY_DEFINITION = enums.SuggestionCode_CONFIG_CHECK_DEPENDENCY_DEFINITION const SuggestionCode_CONFIG_CHANGE_NAMES = enums.SuggestionCode_CONFIG_CHANGE_NAMES