Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add Scaleway as a supported provider

Open
  • Is something wrong?
#336 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
kubernetes, postgresql, python, terraform
Domain
backend, cloud, infrastructure

Research direction

Start by reading the provider profile schema and the existing cloud foundation modules to see how deployments are structured. The issue names infra/terraform/foundations/scaleway-kapsule and depends on #338 for node sizing, with environment resources tracked in #334 and #335. Done means deploy and destroy work end to end, the full e2e, #182 walkthrough and olf bench pass, and dated list prices are recorded for each size.

Written by the indexing model from the issue text.

Description

priority: P0 roadmap track: cloud

Milestone: v0.9-beta — Cloud Beta (AWS, Scaleway, OVH)
Roadmap sequence: #183 (revised 2026-10-05)

Context

European teams want control over where their data platform runs. Scaleway offers managed Kubernetes (Kapsule), S3-compatible object storage, managed PostgreSQL and a container registry, but no managed Iceberg catalog, so it reuses Polaris like local. Most of the work is a foundation module, not new adapters.

Scope

  • Provider type scaleway in the profile schema.
  • infra/terraform/foundations/scaleway-kapsule: Kapsule cluster, private network, node pool from the size mapping (#338), Container Registry.
  • Environment root: #334 (Object Storage), #335 (Managed Database for PostgreSQL), Polaris catalog.
  • Ingress: Traefik behind a LoadBalancer Service, cert-manager DNS-01 through the Scaleway webhook.
  • Kubernetes Secrets for credentials (external secrets backends are post-v1, #27).
  • State data location (region) precisely; make no certification claim that has not been verified for the specific products used.

Acceptance criteria

  • olf deploy/olf destroy work end to end.
  • Full e2e, the #182 walkthrough and olf bench pass.
  • Monthly cost of each size at list price is recorded with its date.
Dominant language
Python
Stars
26
Forks
6
Avg merge
11h 46m
Merged PRs (30d)
176

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenLakeForge/openlakeforge

All issues in OpenLakeForge/openlakeforge

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.