Deploy [UPDATED] on Skaffold

Kubectl

Mon, 01 Jan 0001 00:00:00 +0000

Deploying with kubectl

kubectl is Kubernetes command-line tool for deploying and managing applications on Kubernetes clusters.

Skaffold can work with kubectl to deploy artifacts on any Kubernetes cluster, including Google Kubernetes Engine clusters and local Minikube clusters.

Configuration

To use kubectl, add deploy type kubectl to the deploy section of skaffold.yaml.

The kubectl type offers the following options:

Option	Description	Default
`flags`	additional flags passed to `kubectl`.
`remoteManifests`	Kubernetes manifests in remote clusters.	`[]`
`defaultNamespace`	default namespace passed to kubectl on deployment if no other override is given.
`hooks`	describes a set of lifecycle hooks that are executed before and after every deploy.

flags section offers the following options:

Kpt [UPDATED]

Mon, 01 Jan 0001 00:00:00 +0000

Rendering with kpt

kpt allows Kubernetes developers to customize raw, template-free YAML files for multiple purposes. Skaffold can work with kpt by calling its command-line interface.

Configuration

To use kpt with Skaffold, add deploy type kpt to the deploy section of skaffold.yaml.

The kpt type offers the following options:

Option	Description	Default
`dir`	equivalent to the dir in `kpt live apply <dir>`. If not provided, skaffold deploys from the default hydrated path `<WORKDIR>/.kpt-pipeline`.
`applyFlags`	additional flags passed to `kpt live apply`.	`[]`
`flags`	kpt global flags.	`[]`
`name`	alpha inventory object name.
`inventoryID`	alpha inventory ID which annotates the resources being lively applied by kpt.
`namespace`	alpha sets the inventory namespace.
`force`	used in `kpt live init`, which forces the inventory values to be updated, even if they are already set.	`false`
`defaultNamespace`	default namespace passed to kpt on deployment if no other override is given.

Each entry in paths should point to a folder with a kustomization file.

Helm [UPDATED]

Mon, 01 Jan 0001 00:00:00 +0000

helm is a package manager for Kubernetes that helps you manage Kubernetes applications. Skaffold natively supports iterative development for projects configured to use helm.

Note

To use helm with Skaffold, the helm binary must be installed on your machine. Skaffold will not install it for you.

Configuring your Helm Project with Skaffold

Skaffold supports projects set up to render and/or deploy with Helm, but certain aspects of the project need to be configured correctly in order for Skaffold to work properly. This guide should demystify some of the nuance around using Skaffold with Helm to help you get started quickly.

Docker

Mon, 01 Jan 0001 00:00:00 +0000

Note

This feature is currently experimental and subject to change.

Deploying applications to a local Docker daemon

For simple container-based applications that don’t rely on Kubernetes resource types, Skaffold can “deploy” these applications by running application containers directly in your local Docker daemon. This enables application developers who are not yet ready to make the jump to Kubernetes to take advantage of the streamlined development experience Skaffold provides.

Additionally, deploying to Docker bypasses the overhead of pushing images to a remote registry, and provides a faster time to running application than traditional Kubernetes deployments.

Google Cloud Run [NEW]

Mon, 01 Jan 0001 00:00:00 +0000

Note

This feature is currently experimental and subject to change. Not all Skaffold features are supported, for example debug is currently not supported in Cloud Run (but is on our roadmap).

Cloud Run is a managed compute platform on Google Cloud that allows you to run containers on Google’s infrastructure. With Skaffold, now you are able to configure your dev loop to build, test, sync and use Cloud Run as the deployer for your images.