utilities/auto-blog-link-preserver#13: Create Kubernetes Deployment Example

Issue Information

Issue Type: issue
Status: closed
Reported By: btasker
Assigned To: btasker

Milestone: v0.1
Created: 11-Aug-24 08:21



Description

The intention is that I'll be running this as a k8s CronJob, so it'd probably make sense to provide an example manifest at the same time.



Toggle State Changes

Activity


11-Aug-24 08:21

assigned to @btasker


11-Aug-24 09:55

I've pushed an image build to my private registry to use whilst doing this registry.bentasker.co.uk/utilities/auto-blog-link-preserver:0.1


11-Aug-24 10:38

There's some secret pre-creation needed

kubectl create secret generic linkwarden-info \
--from-literal=url="<redacted>" \
--from-literal=token="<redacted>"

If InfluxDB is going to be used a secret needs to be defined for that (I already have a secret, hence the naming)

kubectl create secret generic influxdbv2 \
--from-literal=influxdb_org=<redacted> \
--from-literal=influxdb_token=<redacted> \
--from-literal=influxdb_token=<redacted>

11-Aug-24 10:59
verified

mentioned in commit 8dc694526cde681415213aaa3d757bbe77b32ad7

Commit: 8dc694526cde681415213aaa3d757bbe77b32ad7 
Author: B Tasker                            
                            
Date: 2024-08-11T11:59:00.000+01:00

Message

docs: add example kubernetes manifest (utilities/auto-blog-link-preserver#13)

+105 -0 (105 lines changed)

11-Aug-24 11:01

The committed example will run the job once every 2 hours.

Currently it refers to an image that doesn't exist: ghcr.io/bentasker/auto-blog-link-preserver:0.1. I'll push an image there once I've made a release.

With the exception of the image name, I've used that manifest to create my CronJob - forcing a manual run shows it all working.

Because I'm running Linkwarden in the same cluster, I've ignored the URL in the secret and used the cluster.local name instead