Getting started with kOps on Scaleway

• kops
• kubernetes

kOps is a tool that helps you set up and manage Kubernetes clusters for production use. It is like a version of kubectl specifically designed for managing clusters.

With kOps, you can easily create, upgrade, and maintain highly available clusters. The tool also takes care of setting up the required cloud infrastructure.

Before you startLink to this anchor

To complete the actions presented below, you must have:

• A Scaleway account logged into the console
• Owner status or IAM permissions allowing you to perform actions in the intended Organization
• An SSH key
• Installed kOps version >= 1.26 on your local computer
• Installed kubectl on your local computer
• An Object Storage bucket and its credentials

Configuring environment variablesLink to this anchor

Before working on the tutorial, it is important to set the following environment variables on your local computer.

export SCW_ACCESS_KEY="my-access-key"
export SCW_SECRET_KEY="my-secret-key"
export SCW_DEFAULT_PROJECT_ID="my-project-id"
# Configure the bucket name to store kops state
export KOPS_STATE_STORE=scw://<bucket-name> # where <bucket-name> is the name of the bucket you set earlier
# Scaleway Object Storage is Amazon S3-compatible so we just override some configurations to talk to our bucket
export S3_REGION=fr-par                     # or another scaleway region providing Object Storage
export S3_ENDPOINT=s3.$S3_REGION.scw.cloud  # define provider endpoint
export S3_ACCESS_KEY_ID="my-access-key"     # where <my-access-key> is the API access key for your bucket
export S3_SECRET_ACCESS_KEY="my-secret-key" # where <my-secret-key> is the API secret key for your bucket
# this is required since Scaleway support is currently in alpha so it is feature gated
export KOPS_FEATURE_FLAGS="Scaleway"

Creating a single master cluster using kOpsLink to this anchor

• Create a cluster in the fr-par-1 Availability Zone, by running the following command:

  kops create cluster --cloud=scaleway --name=mycluster.k8s.local --zones=fr-par-1 --yes
  

  Note

  The default cluster uses Ubuntu images on DEV1-M machines with cilium as Container Network Interface.

Editing a cluster using kOpsLink to this anchor

Update a clusterLink to this anchor

• Run the following command to update your cluster using kOps:

  kops update cluster mycluster.k8s.local --yes
  

Delete a clusterLink to this anchor

• Run the following command to delete your cluster using kOps:

  kops delete cluster mycluster.k8s.local --yes
  

Going furtherLink to this anchor

Now that you have a working kops cluster, read through the recommendations for production setups guide to learn more about how to configure kOps for production workloads.

For more information about kOps, refer to the official kOps documentation.