Export from Kubernetes to Snowflake

CloudQuery is an open-source data integration platform that allows you to export data from any source to any destination.

The CloudQuery Kubernetes plugin allows you to sync data from Kubernetes to any destination, including Snowflake. It's free, open source, requires no account, and takes only minutes to get started.

Ready? Let's dive right in!

Step 1. Install the CloudQuery CLI

The CloudQuery CLI is a command-line tool that runs the sync. It supports MacOS, Linux and Windows.

brew install cloudquery/tap/cloudquery

Step 2. Configure the Kubernetes source plugin

Create a configuration file for the Kubernetes plugin and set up authentication.

Configuration

Create a file called k8s.yaml and add the following contents:

kind: source
spec:
  # Source spec section
  name: k8s
  path: cloudquery/k8s
  version: "v5.1.0"
  tables: ["*"]
  destinations: ["snowflake"]

  spec:
    contexts: ["context"]

Fine-tune this configuration to match your needs. For more information, see the Kubernetes Plugin ↗ page in the docs.

Authentication

Similar to how kubectl works, cloudquery depends on a Kubernetes configuration file to connect to a Kubernetes cluster and sync its information. By default, cloudquery uses the default Kubernetes configuration file (~/.kube/config). You can also specify a different configuration by setting the KUBECONFIG environment variable before running cloudquery sync.

export KUBECONFIG="<PATH_TO_YOUR_CONFIG_FILE>"

Kubernetes Service Account

If cloudquery is running in a pod of the Kubernetes cluster, the Kubernetes Service Account can be used for direct authentication. To use the Kubernetes Service Account for direct authentication, a cluster role with all get and list privileges will need to be used.

The below command creates a new cluster role with get and list privileges.

kubectl apply -f - <<EOF
apiVersion: rbac.authorization.k8s.io/v1
kind:       ClusterRole
metadata:
  name: cloudquery-cluster-read
rules:
- apiGroups:
  - '*'
  resources:
  - '*'
  verbs:
  - get
  - list
- nonResourceURLs:
  - '*'
  verbs:
  - get
  - list
EOF

Next, the cluster role and service account will need to be linked via a cluster role binding. The following creates a cluster role binding for the role we created above and the service account for the cloudquery pod.

kubectl apply -f - <<EOF
apiVersion: rbac.authorization.k8s.io/v1
kind:       ClusterRoleBinding
metadata:
  name: cloudquery-cluster-read-binding
subjects:
- kind: ServiceAccount
  name: cloudquery-sa
roleRef:
  kind: ClusterRole
  name: cloudquery-cluster-read
EOF

Step 3. Configure the Snowflake destination plugin

Create a configuration file for the Snowflake plugin and set up authentication.

Configuration

Create a file called snowflake.yaml and add the following contents:

This example sets the connection string to a value read from the SNOWFLAKE_CONNECTION_STRING environment variable:

kind: destination
spec:
  name: snowflake
  path: cloudquery/snowflake
  version: "v3.2.10"
  write_mode: "append"
  spec:
    connection_string: "${SNOWFLAKE_CONNECTION_STRING}"
    # Optional parameters
    # migrate_concurrency: 1
    # batch_size: 1000 # 1K entries
    # batch_size_bytes: 4194304 # 4 MiB

Fine-tune this configuration to match your needs. For more information, see the Snowflake Plugin ↗ page in the docs.

Step 4. Start the Sync

Run the following command in your terminal to start the sync

cloudquery sync k8s.yaml snowflake.yaml

And away we go! 🚀 The sync will run until completion, fetching all selected tables from Kubernetes. Any errors will be logged to a file called cloudquery.log.

Export from Kubernetes to Snowflake

Step 1. Install the CloudQuery CLI

Step 2. Configure the Kubernetes source plugin

Configuration

Authentication

Kubernetes Service Account

Step 3. Configure the Snowflake destination plugin

Configuration

Step 4. Start the Sync

Further Reading

Kubernetes Service Account