fix: unique per-env Gateways so NGF nginx is not shared #182
No reviewers
Labels
No labels
prio/P1
prio/P2
prio/P3
status/leftover
status/new
status/parked
type/feature
type/ops
type/research
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MeshFlowsGPL/meshflows!182
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/unique-gateway-names"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Test plan
NGF 2.4.2 names the data-plane Deploy/Service {gateway}-nginx. Every env used Gateway meshflows, so nginx mixed config across namespaces. Render meshflows-{env} via __MESHFLOWS_ENV__ (same path as hostnames). Leftover meshflows-nginx is not removed by NGF; delete that Deploy/Service per env after cutover. ci: put environment and deploy mode in the Actions run-name Forgejo listed every deploy.yml run as Deploy to Cluster. The title now includes env plus verify-only, flows-only, or engine-only from workflow inputs. Co-authored-by: Cursor <cursoragent@cursor.com>fix: unique per-env Gateways so NGF nginx is not sharedto WIP: fix: unique per-env Gateways so NGF nginx is not sharedPin swallowed a missing meshflows-{env}-nginx while leftover meshflows-nginx kept the env ports. Verify now waits and asserts NodePorts. run-name must use the forgejo context (not github.*) or Forgejo 16 falls back to Deploy to Cluster. Co-authored-by: Cursor <cursoragent@cursor.com>Forgejo 16 list and run headings use workflow name:, not run-name. Split push/dispatch onto deploy-{env}.yml wrappers that call deploy.yml. Co-authored-by: Cursor <cursoragent@cursor.com>WIP: fix: unique per-env Gateways so NGF nginx is not sharedto fix: unique per-env Gateways so NGF nginx is not shared