Skip to content

docs: fix stale kong:2.8.1 references - #25

Draft
STRRL wants to merge 1 commit into
masterfrom
claude/hungry-perlman-b4ac04
Draft

docs: fix stale kong:2.8.1 references#25
STRRL wants to merge 1 commit into
masterfrom
claude/hungry-perlman-b4ac04

Conversation

@STRRL

@STRRL STRRL commented Aug 23, 2026

Copy link
Copy Markdown
Owner

Problem

DefaultKongImage is kong/kong:3.9.1, but several docs and code comments still showed kong:2.8.1, which no longer matches the real default and misleads readers.

Solution

Update the places that describe the current behavior, and leave the historical snapshots and test fixtures alone.

Major Changes

  • Docs describing current behavior
    • README.md: the architecture list and the sample status now show kong/kong:3.9.1
    • docs/api-reference.md: the KongConfig.image default column now shows kong/kong:3.9.1
    • docs/architecture.md: the sample status now shows kong/kong:3.9.1
  • Code comments
    • internal/webhook/doc.go: the defaulting example now uses kong/kong:3.9.1
  • Historical spec snapshot
    • specs/001-selfhost-supabase-operator/design-decisions.md: kept the 2025-10-03 image list as is, added a note pointing at api/v1alpha1/wellknown_images.go and hack/sync-upstream-images.sh as the source of truth

Not Changed

  • internal/status/ and api/v1alpha1/supabaseproject_types_test.go fixtures: kong:2.8.1 is only an arbitrary string there, not a default declaration
  • ai-docs/ and the rest of specs/001-selfhost-supabase-operator/: point in time snapshots
  • No Kong to Envoy renaming, to avoid conflicts with the planned gateway migration

The default Kong image is kong/kong:3.9.1, but several docs and code
comments still showed kong:2.8.1. Update the places that describe the
current behavior, and add a note to the 001 spec snapshot pointing at
the real source of truth.

Test fixtures in internal/status and api/v1alpha1 keep the old string
because it is only an arbitrary value there, not a default declaration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant