instagram-poster: disable ig-ingest-stories CronJob until /ig-ingest ships

The endpoint exists in the working copy of instagram_poster/app.py
but isn't committed/built/deployed, so every cron fire returned 404
and triggered JobFailed alerts every 30 min.

Set count = 0 to leave the resource declaration in place — re-enable
by removing that line once the endpoint is in a built image.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Viktor Barzin 2026-05-10 18:49:25 +00:00
parent d2be0921e8
commit 88e57fdddb

View file

@ -396,7 +396,7 @@ module "ingress_image_public" {
name = "instagram-poster-image"
host = "instagram-poster"
tls_secret_name = var.tls_secret_name
protected = false
auth = "none"
ingress_path = ["/image", "/original"]
port = 80
service_name = "instagram-poster"
@ -409,7 +409,7 @@ module "ingress_protected" {
name = "instagram-poster"
host = "instagram-poster"
tls_secret_name = var.tls_secret_name
protected = true
auth = "required"
ingress_path = ["/"]
port = 80
service_name = "instagram-poster"
@ -433,6 +433,12 @@ locals {
}
resource "kubernetes_cron_job_v1" "ig_ingest_stories" {
# Temporarily disabled: the /ig-ingest endpoint exists in working-copy
# changes to instagram_poster/app.py but hasn't been committed/built/
# deployed yet, so every fire returns 404 and JobFailed alerts fire.
# Re-enable by removing `count = 0` once the endpoint is shipped.
count = 0
metadata {
name = "ig-ingest-stories"
namespace = kubernetes_namespace.instagram_poster.metadata[0].name