From 4246c1e62fd9c8013ee7b1ea8a92467504fbd82e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?St=C3=A9phane=20Tailland?= <stephane@sttlab.eu>
Date: Mon, 31 Aug 2026 08:33:14 +0200
Subject: [PATCH] Delete the unreferenced cache manifest

---
 kong/rest/proxy-cache.yaml | 34 ----------------------------------
 1 file changed, 34 deletions(-)
 delete mode 100644 kong/rest/proxy-cache.yaml

diff --git a/kong/rest/proxy-cache.yaml b/kong/rest/proxy-cache.yaml
deleted file mode 100644
index ce8fe51..0000000
--- a/kong/rest/proxy-cache.yaml
+++ /dev/null
@@ -1,34 +0,0 @@
-# NOT APPLIED — deliberately unreferenced by kustomization.yaml.
-#
-# This cached every GET on the whole service for 60 seconds, and these are
-# read-write APIs. Kong's proxy cache has **no invalidation on write**: a POST
-# that changes a product passes through the same gateway, and the gateway goes
-# on serving the value it captured before, for up to a minute, with nothing in
-# the response saying so.
-#
-# It produced a real wrong answer. An agent woken by a stock event read the
-# figure from before that event and reported, in one sentence, "68 in stock,
-# above the threshold" and "it crossed the threshold, from 68".
-#
-# Kept here rather than deleted so that reinstating it is a decision, not a
-# rediscovery. If it comes back, it belongs on reference data that is not
-# written through this gateway, bound per route — or with `cache_control: true`
-# so the API declares what is cacheable, which is the owner's call and not the
-# gateway's.
-#
-apiVersion: configuration.konghq.com/v1
-kind: KongPlugin
-metadata:
-  name: ${NAME}-catalog-api-proxy-cache
-  namespace: ${NAMESPACE}
-plugin: proxy-cache-advanced
-config:
-  strategy: memory
-  request_method:
-    - GET
-    - HEAD
-  response_code:
-    - 200
-  content_type:
-    - application/json
-  cache_ttl: 60