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

Fix loading the Kubernetes attached machine with TLS #3368

Merged
merged 2 commits into from
Sep 8, 2024

Conversation

Mahmoud-Emad
Copy link
Contributor

@Mahmoud-Emad Mahmoud-Emad commented Sep 4, 2024

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's IP:PORT rather than a URL. To resolve this, I implemented a checker that determines whether the backend is a URL or an IP. Based on this check, the appropriate machine name is retrieved.

Changes

  • Check if the backends are URL or IP and get the attached machine based on it.

Related Issues

Comment

Checklist

  • Tests included
  • Build pass
  • Documentation
  • Code format and docstrings
  • Screenshots/Video attached (needed for UI changes)

- Check if the backends are URL or IP and get the attached machine based on it.
@Mahmoud-Emad Mahmoud-Emad merged commit ea80744 into development Sep 8, 2024
10 checks passed
@Mahmoud-Emad Mahmoud-Emad deleted the development_kubernetes_domains branch September 8, 2024 07:55
@xmonader xmonader added this to the 2.6.0 milestone Sep 24, 2024
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.

4 participants