Due to an unforeseen network event and lack of vigilence Today, dozens of custom domains on #noticeable were disrupted. Fortunately, I was able to find a quick workaround.

Fix a pod anti affinity configuration issue on #noticeable k3s cluster

Send announcement email about new parent company to all #noticeable users

Prepare email and script to announce new parent company to #noticeable users this time

Manually test Cloudflare for SaaS on #noticeable staging environment

Complete deployment of changes to use Cloudflare tunnels on #noticeable staging and production environments

Fix broken HTTPS serving for #noticeable custom domains

Consider switching from Caddy to Cloudflare for handling custom domains managed by #noticeable

Start updating #noticeable production to use Cloudflare tunnels

Rework #noticeable services deployment scripts

Handle user request to delete #noticeable account

Create #noticeable micro service to extract image from video

Prepare email to announce #noticeable transition to a new legal company

Fix a bug with #noticeable upcoming invoices

Fix Stripe webhook handling for #noticeable

Start integrating Stripe customer portal with #noticeable

Create one small free Redis cluster for internal usage with #noticeable

Answer questions from 2 new leads for #noticeable

Extend #noticeable .io domain for 3 more years (following @cacho) due to upcoming price increase

Answer support email #noticeable