Category
Operations
Everyday Kubernetes on Scaleway: deployments, databases, upgrades, alerts.
← Clear filter
OperationsWordPress on Kubernetes: seven traps between the chart and the first page
WordPress runs well on Kubernetes if a few things are right from the start. Seven traps almost everyone hits once during their first setup, and how to avoid them.
- Kubernetes
- Volumes
- Databases
OperationsLogs, usage and uptime without your own monitoring stack
During an incident, three questions matter: What is the application writing, how heavily was it used, and can it be reached from outside? Not every team needs its own monitoring stack for that.
- Monitoring
- Kubernetes
- Kapsule
OperationsRollbacks on Kubernetes: why a tag is not a version
A rollback that pulls the same tag again brings back the broken version. If you want to roll back reliably, you need the digest of every deployment, and a plan for the database.
- CI/CD
- Kubernetes
- Backups
OperationsBus factor 1: when the cluster belongs to a single colleague
In many small teams, the cluster belongs to one colleague. That works fine until they go on vacation. Six steps to make sure operations no longer hinge on one person.
- Kubernetes
- SaaS
- Costs
OperationsFrom AWS to Scaleway: what becomes of RDS, S3 and Route 53
Almost every AWS service has a counterpart at Scaleway. The move rarely fails because of Kubernetes – it fails on the database cutover, egress costs and DNS.
- Migration
- Scaleway
- Kubernetes
OperationsKubernetes upgrades on Kapsule without the fear
Kubernetes ships three minor versions a year, and Kapsule supports only a limited number of them. Wait two years and you have four upgrades ahead of you. Better: one per quarter, boring.
- Kapsule
- Kubernetes
- Scaleway
OperationsOne database per service: roles, privileges and the read-only user who sees nothing
The BI user has read access and still can’t see the new table. That’s not a bug, that’s PostgreSQL. And it’s the reason privileges have to be granted in a fixed order.
- Databases
- Scaleway
- SaaS
OperationsKaniko or GitHub Actions: where should the image be built?
Kaniko builds where the application runs. GitHub Actions builds where the code lives. Neither needs a Docker daemon, and both have a catch you only notice in production.
- CI/CD
- Kubernetes
- Costs
OperationsWhy your app sees the wrong IP behind the load balancer
Every visitor comes from the same IP, the login limit locks out all customers at once, and the allowlist lets nobody in. That’s not an attack, that’s the load balancer.
- Ingress
- Scaleway
- Kubernetes
OperationsWhat does Kubernetes on Scaleway really cost?
Node prices are the smallest part. Budgeting Kubernetes on Scaleway takes five line items, and the most expensive one is on no price list.
- Costs
- Scaleway
- Kapsule