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

feat: run embedded discovery service in Omni #105

Merged
merged 1 commit into from
Jun 5, 2024

Conversation

utkuozdemir
Copy link
Member

@utkuozdemir utkuozdemir commented Apr 2, 2024

Run a discovery service instance inside Omni (enabled by default).

It listens only on the SideroLink interface on port 8093.

Clusters can opt in to use this embedded discovery service instead of the discovery.talos.dev. It is added as a new cluster feature both on frontend and in cluster templates.

Closes #20.

Docs: siderolabs/omni-docs#83

@utkuozdemir utkuozdemir force-pushed the bring-in-discovery-service branch 2 times, most recently from 1dbf15e to 01dbee2 Compare April 10, 2024 15:37
@utkuozdemir utkuozdemir force-pushed the bring-in-discovery-service branch 3 times, most recently from 358d0fa to b0e3220 Compare May 30, 2024 13:17
Makefile Outdated
GRPC_GO_VERSION ?= 1.3.0
GRPC_GATEWAY_VERSION ?= 2.19.1
GRPC_GATEWAY_VERSION ?= 2.19.1 # manually reverted to 2.19.1, as 2.20.0 breaks the frontend
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the culprit, otherwise PROTOBUF_GO_VERSION 1.34.1 is fine.

@utkuozdemir utkuozdemir marked this pull request as ready for review May 30, 2024 14:22
@TimJones
Copy link
Member

Just to note: make sure we also update omin-docs to reflect the new feature option in cluster templates.

@utkuozdemir utkuozdemir self-assigned this May 30, 2024
@utkuozdemir
Copy link
Member Author

Just to note: make sure we also update omin-docs to reflect the new feature option in cluster templates.

Thanks for the reminder, sure will do.

@smira
Copy link
Member

smira commented May 30, 2024

I think (after the discussion in the meeting) we need to default this feature to 'disabled' (i.e. use discovery.talos.dev by default).

@utkuozdemir utkuozdemir force-pushed the bring-in-discovery-service branch 4 times, most recently from ec9c2b2 to 93724ae Compare May 31, 2024 15:14
@utkuozdemir
Copy link
Member Author

I think (after the discussion in the meeting) we need to default this feature to 'disabled' (i.e. use discovery.talos.dev by default).

Changed the implementation to be that way, greatly simplified.

@Unix4ever
Copy link
Member

Unix4ever commented Jun 3, 2024

I guess ClusterMachineTeardown controller should check the cluster features and pick the right discovery service instance depending on which one is enabled for the cluster.

@utkuozdemir
Copy link
Member Author

I guess ClusterMachineTeardown controller should check the cluster features and pick the right discovery service instance depending on which one is enabled for the cluster.

Oh that's a good point, we need 2 discovery clients living in the same time in fact. I'll fix that.

@utkuozdemir
Copy link
Member Author

utkuozdemir commented Jun 4, 2024

I guess ClusterMachineTeardown controller should check the cluster features and pick the right discovery service instance depending on which one is enabled for the cluster.

Done. The logic there was not working properly anyway - was probing an already deleted ClusterMachineIdentity and returning without actually calling AffiliateDelete. I fixed the logic there and tested both with and without embedded discovery service being enabled.

Also addressed all other comments.

Run a discovery service instance inside Omni (enabled by default).

It listens only on the SideroLink interface on port 8093.

Clusters can opt in to use this embedded discovery service instead of the `discovery.talos.dev`. It is added as a new cluster feature both on frontend and in cluster templates.

Closes #20.

Signed-off-by: Utku Ozdemir <[email protected]>
@utkuozdemir
Copy link
Member Author

/m

@talos-bot talos-bot merged commit 331fc31 into main Jun 5, 2024
19 checks passed
@talos-bot talos-bot deleted the bring-in-discovery-service branch June 5, 2024 23:50
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.

bundle Discovery Service with Omni
5 participants