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

Remove p2p route table check on startup #89

Merged
merged 1 commit into from
May 2, 2023
Merged

Conversation

phillebaba
Copy link
Member

The thinking originally was that the registry should not start until bootstrap had completed. This was implemented when the mirror configuration was not written until the registry had started. With the introduction of the node port service which forwards traffic to other nodes to handle the mirroring there is no real point of doing this. Especially because we have seen startup issues when a cluster is being created.

What will happen now is that if the routing table is not populated a 404 will be returned forcing Containerd to attempt the next option in the mirror list.

I have added a TODO to explore if its worth returning early if the routing table is empty.

@phillebaba phillebaba changed the title Remove bootstrap check on startup Remove p2p route table check on startup May 2, 2023
@phillebaba phillebaba merged commit 6af304f into main May 2, 2023
@phillebaba phillebaba deleted the startup-check branch May 2, 2023 13:28
t1mt pushed a commit to t1mt/spegel that referenced this pull request Sep 3, 2024
Remove p2p route table check on startup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant