Skip to content

Rather tricky to deploy and use with Kubernetes #169

Description

@calmh

I'd like to use tsidp for some services deployed in the same cluster. However, this seems tricky or impossible (I haven't succeeded, at least). The problems, as I experience them:

  • tsidp uses its own internal Tailscale client for listening, meaning it's not possible to point a local Service toward it.
  • Without a Service, other cluster workloads could only talk to it via its Tailscale address.
  • Creating an externalName service with the Tailscale Operator appears to work, but any communication times out. I'm guessing this has something to do with the pods not being able to establish VPN within the cluster.
  • There's an option for listening on a local port, but it appears hardcoded for localhost which would not work from outside the container.

I don't know if the internal Tailscale client is somehow fundamental to how it works, but if it could run as a normal workload behind a service and a Tailscale ingress, that would solve all the operational problems.

It needs to have the ability to be reachable via Tailscale by clients, but respond to token exchanges etc on a cluster address.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions