Support managing domain on kubernetes

[AhmedHanafy725]

Which package/s are you suggesting this feature for?

Dashboard

Is your feature request related to a problem? Please describe

The user might have some solutions on the cluster that require an ingress with a domain.

Describe the solution you'd like

It would be good if he could create domains pointing to the cluster's master.

[Mahmoud-Emad]

Issue update

Work done

Changes

• Optimized the ManageGatewy component to work on both types of machines normal VM and K8S machine
• Generate the name based on the master
• takes the master networks as the domain-supported networks
• Change the dialog title to be dynamic
• Working on refactoring the component
• Load the WireGuard network name dynamic based on the machine type

Screenshots/Video

Screencast.from.08-18-2024.03.10.58.PM.webm

[Mahmoud-Emad]

After some investgation we found that our K3S image binds on IPv4 and won't work on IPv6 e.g. Mycelium or Planetary networks, we need to search if there a way to bind on both IPs v4 or v6 without break the current behavior

[Mahmoud-Emad]

Due to threefoldtech/tf-images#291 we have 2 options now

1. • Support only IPv4 and Wireguard networks
2. • Wait until the operations update the K3S image

[Mahmoud-Emad]

During the implementation, we discovered and agreed on:

• Set the default port to 443
• Define a new selector that lists all node's master/workers
• Let the user select the target node and load its interfaces based on the selected node
• Remove any V6 from the networks, let the user only choose Public IPv4 or Wireguard

We'll go with the first option

Due to threefoldtech/tf-images#291 we have 2 options now

1. • Support only IPv4 and Wireguard networks
2. • Wait until the operations update the K3S image

[Mahmoud-Emad]

During the implementation i faced this bug #3321

[A-Harby]

Can we change one of the logo of the manage workers or domain? Both having the same logo is kind of confusing.

And maybe we add a new column to identify to whom this domain is attached to (master or which worker).

[A-Harby]

Not all the domain interfaces are shown.

I deployed worker with all the networks.

But it only shows me Wireguard and IPv4.

And master with deployed with planetary and mycelium, but also it only shows wireguard.

[Mahmoud-Emad]

Can we change one of the logo of the manage workers or domain? Both having the same logo is kind of confusing.

And maybe we add a new column to identify to whom this domain is attached to (master or which worker).

@ehab-hassan , please give it a look

[Mahmoud-Emad]

Not all the domain interfaces are shown.

I deployed worker with all the networks.

But it only shows me Wireguard and IPv4.

And master with deployed with planetary and mycelium, but also it only shows wireguard.

@A-Harby , Please see the above comment

Due to threefoldtech/tf-images#291 we have 2 options now

1. • Support only IPv4 and Wireguard networks
2. • Wait until the operations update the K3S image

[ehab-hassan]

Can we change one of the logo of the manage workers or domain? Both having the same logo is kind of confusing.
And maybe we add a new column to identify to whom this domain is attached to (master or which worker).

@ehab-hassan , please give it a look

use this for Workers
https://pictogrammers.com/library/mdi/icon/cube-outline/

and Globe for domain

also, we had a tooltip here to be cleared to the user

[Mahmoud-Emad]

@ehab-hassan
We can't use the Globe icon for the domain for two reasons

1. The manage domains icon in the VMs view is the settings icon, so we have to be consistent.
2. The Globe icon used in the Manage Domains modal and point to redirecting the user to the domain

IMO. setting it as the settings icon and only changing the Manage workers icon might be good, what do you think?

[Mahmoud-Emad]

Can we change one of the logo of the manage workers or domain? Both having the same logo is kind of confusing.

And maybe we add a new column to identify to whom this domain is attached to (master or which worker).

@A-Harby
Please check

[A-Harby]

Verified, Devnet 4829e02.

Icons of manage worker was changed.

And a new column was added to identify which master or worker the domain is attached to.

And the domains are working correctly on master and workers (for wireguard and IPv4 only).

New test case: TC2815 - Add domain to a Kubernetes master and worker

[A-Harby]

Unfortunately, I found a bug when the TLs is turned on; the domain won't work, and the attached file disappears!.

[Mahmoud-Emad]

Unfortunately, I found a bug when the TLs is turned on; the domain won't work, and the attached file disappears!.

@A-Harby
Yeah, there is an issue with loading the attached machine name in case the machine is enabled with the TLS option, However, how do you run the server inside the machine?

[A-Harby]

Verified Devnet, ebe226c.

The loading attachment bug was solved, and the name now appears on TLs on or off.

And also, the domain is working.

Updated the test case with ingress steps: TC2815 - Add domain to a Kubernetes master and worker