Fix loading the Kubernetes attached machine with TLS #3368
Merged
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.
Description
An issue was identified where the attached machine name was not displaying correctly when the machine had the
TLS
option enabled. This occurred because, in such cases, the backend was set to the machine'sIP:PORT
rather than aURL
. To resolve this, I implemented a checker that determines whether the backend is aURL
or anIP
. Based on this check, the appropriate machine name is retrieved.Changes
Related Issues
Comment
Checklist