Fix Discovery boot when Proxy is not yet available#60457
Merged
marcoandredinis merged 1 commit intomasterfrom Oct 23, 2025
Merged
Fix Discovery boot when Proxy is not yet available#60457marcoandredinis merged 1 commit intomasterfrom
marcoandredinis merged 1 commit intomasterfrom
Conversation
marcoandredinis
added
no-changelog
smallinsky
approved these changes
Oct 22, 2025
Contributor
Author
Collaborator
|
/excludeflake * |
marcoandredinis
force-pushed
the
marco/discovery_fix-missing-public-addr
branch
from
a51100d to
dd19b57
Compare
Contributor
Author
|
@camscale @ryanclark Can you please take a look when you get a chance? |
ryanclark
approved these changes
Oct 23, 2025
public-teleport-github-review-bot
bot
removed the request for review
from camscale
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
If teleport is started with just Auth and Discovery in the same host, the Public Proxy Addr is not available. Even tho this means that Discovery will not be able to enroll Servers, this is a valid set up. When the Proxy becomes available, the next Discovery iteration will correctly enroll servers.
marcoandredinis
force-pushed
the
marco/discovery_fix-missing-public-addr
branch
from
dd19b57 to
f4b2832
Compare
Contributor
|
@marcoandredinis See the table below for backport results.
|
marcoandredinis
added a commit
that referenced
this pull request
Oct 23, 2025
If teleport is started with just Auth and Discovery in the same host, the Public Proxy Addr is not available. Even tho this means that Discovery will not be able to enroll Servers, this is a valid set up. When the Proxy becomes available, the next Discovery iteration will correctly enroll servers.
marcoandredinis
added a commit
that referenced
this pull request
Oct 24, 2025
If teleport is started with just Auth and Discovery in the same host, the Public Proxy Addr is not available. Even tho this means that Discovery will not be able to enroll Servers, this is a valid set up. When the Proxy becomes available, the next Discovery iteration will correctly enroll servers.
marcoandredinis
added a commit
that referenced
this pull request
Oct 24, 2025
If teleport is started with just Auth and Discovery in the same host, the Public Proxy Addr is not available. Even tho this means that Discovery will not be able to enroll Servers, this is a valid set up. When the Proxy becomes available, the next Discovery iteration will correctly enroll servers.
github-merge-queue bot
pushed a commit
that referenced
this pull request
Oct 24, 2025
…ipt` SSM Document (#60434) * Use AWS-RunShellScript as the default SSM Doc in EC2 Auto Discover * escape url values * Fix Discovery boot when Proxy is not yet available (#60457) If teleport is started with just Auth and Discovery in the same host, the Public Proxy Addr is not available. Even tho this means that Discovery will not be able to enroll Servers, this is a valid set up. When the Proxy becomes available, the next Discovery iteration will correctly enroll servers.
mmcallister
pushed a commit
that referenced
this pull request
Nov 6, 2025
If teleport is started with just Auth and Discovery in the same host, the Public Proxy Addr is not available. Even tho this means that Discovery will not be able to enroll Servers, this is a valid set up. When the Proxy becomes available, the next Discovery iteration will correctly enroll servers.
mmcallister
pushed a commit
that referenced
this pull request
Nov 19, 2025
If teleport is started with just Auth and Discovery in the same host, the Public Proxy Addr is not available. Even tho this means that Discovery will not be able to enroll Servers, this is a valid set up. When the Proxy becomes available, the next Discovery iteration will correctly enroll servers.
mmcallister
pushed a commit
that referenced
this pull request
Nov 20, 2025
If teleport is started with just Auth and Discovery in the same host, the Public Proxy Addr is not available. Even tho this means that Discovery will not be able to enroll Servers, this is a valid set up. When the Proxy becomes available, the next Discovery iteration will correctly enroll servers.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If teleport is started with just Auth and Discovery in the same process, the Public Proxy Addr is not available.
Even tho this means that Discovery will not be able to enroll Servers, this is a valid set up.
When the Proxy becomes available, the next Discovery iteration will correctly enroll servers.
Not adding a changelog because this didn't made into any release branch.
Thank you @smallinsky for reporting this early.