Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prevent Proxy namespace from being modified #9635

Merged
merged 2 commits into from
Jun 17, 2024

Conversation

lgadban
Copy link
Contributor

@lgadban lgadban commented Jun 17, 2024

Previously, a 'metaKey' was generated for each Proxy being translated
and synced to envoy. This key was used as a 'tag' for tracing of the
translation/sync prcoess. It used a custom function that was almost exactly
matched how the SnapshotCacheKey used for xDS was generated; this function
also modified the actual Proxy's namespace, which broke assumptions of where
the proxy lives in the in-memory client.

By removing the namespace modification we fix various status error logs as
now the Proxy is located where the rest of the system expects (the write
namespace). Also, we can simply use the SnapshotCacheKey(...) to generate
a key with the same logic used for xds.
@solo-changelog-bot
Copy link

Issues linked to changelog:
https://github.com/solo-io/solo-projects/issues/6252

@github-actions github-actions bot added the keep pr updated signals bulldozer to keep pr up to date with base branch label Jun 17, 2024
@lgadban lgadban enabled auto-merge (squash) June 17, 2024 19:23
@lgadban lgadban merged commit 8c8747e into v1.17.x Jun 17, 2024
22 checks passed
@lgadban lgadban deleted the backport/fix-status-spamming/v1.17 branch June 17, 2024 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keep pr updated signals bulldozer to keep pr up to date with base branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants