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

Mark vexination and bombastic API pods ready only when initial search index can be loaded #532

Closed
lulf opened this issue Sep 14, 2023 · 1 comment
Closed

Mark vexination and bombastic API pods ready only when initial search index can be loaded #532

lulf opened this issue Sep 14, 2023 · 1 comment
Assignees
@lulf

Comments

@lulf
Copy link
Contributor

lulf commented Sep 14, 2023

This is required to prevent a situation during the upgrade where the schema was updated but the indexer has not yet pushed a new index, so the new API pods should not receive traffic until they've successfully loaded the index.

This will ensure that during an upgrade, the old API pods will still be running with the old index and schema until the new one has been rebuilt.
@lulf lulf self-assigned this Sep 14, 2023
@lulf lulf mentioned this issue Sep 14, 2023
Merged
lulf pushed a commit that referenced this issue Sep 14, 2023
feat: add readiness probe for API search availability
1e35be2 
If the search index fails the initial sync, the readiness probe will not pass, which will
allow the previous instance of the API to continue working.

Issue #532
@lulf lulf mentioned this issue Sep 14, 2023
Merged
lulf pushed a commit that referenced this issue Sep 15, 2023
feat: add readiness probe for API search availability
4fc46cf 
If the search index fails the initial sync, the readiness probe will not pass, which will
allow the previous instance of the API to continue working.

Issue #532
github-merge-queue bot pushed a commit that referenced this issue Sep 15, 2023
feat: add readiness probe for API search availability
d8ca663 
If the search index fails the initial sync, the readiness probe will not pass, which will
allow the previous instance of the API to continue working.

Issue #532
@lulf
Copy link
Contributor Author

lulf commented Oct 24, 2023

This has been fixed for a while

@lulf lulf closed this as completed Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lulf lulf

Labels
None yet
Projects
Supply-Chain Trust Manager
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lulf