Inter-Actief/Beheer_Issues

Migrate wiki-sync permission script to Kubernetes Job

Open

#132 opened on Apr 7, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees) (0 forks)auto 404
Prioritygood first issuekubernetes

Repository metrics

Stars
 (2 stars)
PR merge metrics
 (PR metrics pending)

Description

Currently wiki permissions are managed by a script that is running on the old salt infrastructure, but the wiki itself is already running in Kubernetes.

We should add this script to the Kubernetes config. It should ideally be run as a post-sync job so it runs after each new deployment, but it could also be a periodic cronjob.

The script can be found in the old salt-config repo.

It is run in the following way:

python3 /opt/wiki/wiki-sync.py /opt/wiki/mappings.json

It requires a configuration file and two environment variables:

WIKI_TOKEN="secret"
WIKI_URL="https://wiki.ia.utwente.nl/graphql"

The configuration file is a JSON version of this file.

I believe the script only uses the python 3 standard library, so we could simply use a py3 base image in the job, mount the script and config file from a configmap, set the env vars from a secret, and run it, no custom docker image required.

Contributor guide

Research direction
Create a Kubernetes Job manifest that runs the Python script using a base image like python:3 slim. Mount the script and config file from a ConfigMap, and set environment variables from a Secret. Optionally configure as a post sync hook in ArgoCD or as a CronJob. Test in a non production namespace first.
Tech stack
pythonkubernetesdocker
Domain
devopsinfrastructureci cd
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KubernetesPythonYAML
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60