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.

Sign up for GitHub

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

Jump to bottom

KIC 2.0 - Config SHA for Kong Admin Updates #1280

Closed
1 task
shaneutt opened this issue May 4, 2021 · 0 comments · Fixed by #1282
Closed
1 task

KIC 2.0 - Config SHA for Kong Admin Updates #1280

shaneutt opened this issue May 4, 2021 · 0 comments · Fixed by #1282
Assignees
@shaneutt
Labels
area/perf Performance Related Issues priority/high
Milestone
Blockers for cutt...

Comments

@shaneutt
Copy link
Contributor

shaneutt commented May 4, 2021

Related to a previous discussion #1274 (comment).

The purpose of this task is to re-apply the KIC v1.x logic of creating and using a SHA to determine whether the configuration of the Kong Admin API had actually been updated in order to drop extraneous configuration updates.

Acceptance Criteria

  • SHA sums are captured for updates to the client-go caching based Proxy implementation to ignore nil updates
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shaneutt shaneutt

Labels
area/perf Performance Related Issues priority/high
Projects
None yet
Milestone
Blockers for cutting KIC 2.0-alpha.1
Development

Successfully merging a pull request may close this issue.

fix: add kong update sha checks Kong/kubernetes-ingress-controller
1 participant
@shaneutt