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

Fix endpoint update of configmap based tcp services #842

Merged
merged 1 commit into from
Aug 30, 2021

Conversation

jcmoraisjr
Copy link
Owner

Legacy ConfigMap based TCP services has its own endpoint list that doesn't track partial parsing. The entry point was changed when Gateway API was added, it was was incorrectly configured to only run when a full sync is needed, or when the ConfigMap was changed, leading to new state not being reflected in the configuration. This update ensures that ConfigMap based TCP services is always parsed when something changes in the cluster.

Legacy ConfigMap based TCP services has its own endpoint list that
doesn't track partial parsing. The entry point was changed when Gateway
API was added, it was was incorrectly configured to only run when a full
sync is needed, or when the ConfigMap was changed, leading to new state
not being reflected in the configuration. This update ensures that
ConfigMap based TCP services is always parsed when something changes in
the cluster.
@jcmoraisjr
Copy link
Owner Author

#840

@jcmoraisjr jcmoraisjr merged commit e5965da into master Aug 30, 2021
@jcmoraisjr jcmoraisjr deleted the jm-fix-tcp-ep-update branch August 30, 2021 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant