starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[Docs] Is "Enable HTTPS" supported? #954

New Issue
Closed
opened 2025-12-29 02:26:39 +01:00 by adam · 6 comments
adam commented 2025-12-29 02:26:39 +01:00
Owner
Copy Link

Originally created by @tidux on GitHub (Feb 23, 2025).

Use case

I use the Tailscale Kubernetes Operator to expose Ingresses which include creating public DNS records and requesting HTTPS certificates for them via Let's Encrypt. I want to know if this is a supported usecase for Headscale (yet?) or if I should keep using Tailscale's free plan.

Description

The relevant Tailscale features are:

The Kubernetes Operator is installed via Helm charts so does not need anything from the Headscale project directly, but it does depend on the other two features for full functionality.

Contribution

  • I can write the design doc for this feature
  • I can contribute this feature

How can it be implemented?

No response

Originally created by @tidux on GitHub (Feb 23, 2025). ### Use case I use the Tailscale Kubernetes Operator to expose Ingresses which include creating public DNS records and requesting HTTPS certificates for them via Let's Encrypt. I want to know if this is a supported usecase for Headscale (yet?) or if I should keep using Tailscale's free plan. ### Description The relevant Tailscale features are: * [Enable HTTPS](https://tailscale.com/kb/1153/enabling-https) * [oAuth clients](https://tailscale.com/kb/1215/oauth-clients) * [Kubernetes Operator](https://tailscale.com/kb/1236/kubernetes-operator) The Kubernetes Operator is installed via Helm charts so does not need anything from the Headscale project directly, but it does depend on the other two features for full functionality. ### Contribution - [ ] I can write the design doc for this feature - [ ] I can contribute this feature ### How can it be implemented? _No response_
adam added the enhancementstaledocumentation labels 2025-12-29 02:26:39 +01:00
adam closed this issue 2025-12-29 02:26:39 +01:00
adam commented 2025-12-29 02:26:40 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Feb 23, 2025):

We do not support the Kubernetes Operator, so if you are using that, you have to stay with Tailscale. We do not support OAuth clients which would be the key piece needed. I do not realistically think we will, its a security heavy feature that we dont really have capacity to implement, at least not for years.

HTTPS; I do not think we do, but that is probably more feasible.

@kradalby commented on GitHub (Feb 23, 2025): We do not support the Kubernetes Operator, so if you are using that, you have to stay with Tailscale. We do not support OAuth clients which would be the key piece needed. I do not realistically think we will, its a security heavy feature that we dont really have capacity to implement, at least not for years. HTTPS; I do not think we do, but that is probably more feasible.
adam commented 2025-12-29 02:26:40 +01:00
Author
Owner
Copy Link

@tidux commented on GitHub (Feb 24, 2025):

I wouldn't recommend writing oAuth from scratch either. Maybe integrate with Dex or Keycloak?

@tidux commented on GitHub (Feb 24, 2025): I wouldn't recommend writing oAuth from scratch either. Maybe integrate with Dex or Keycloak?
adam commented 2025-12-29 02:26:40 +01:00
Author
Owner
Copy Link

@evilhamsterman commented on GitHub (Mar 14, 2025):

Dex or keycloak are identity providers that an application can use to offload authentication. OAuth2 for machine to machine isn't as bad and there are plenty of libraries to do it. The complexity is probably in how to handle the permissions

@evilhamsterman commented on GitHub (Mar 14, 2025): Dex or keycloak are identity providers that an application can use to offload authentication. OAuth2 for machine to machine isn't as bad and there are plenty of libraries to do it. The complexity is probably in how to handle the permissions
adam commented 2025-12-29 02:26:41 +01:00
Author
Owner
Copy Link

@evilhamsterman commented on GitHub (Mar 14, 2025):

Though I guess you were referring to dex and keycloak as the authorization server. Nevermind I'll see myself out

@evilhamsterman commented on GitHub (Mar 14, 2025): Though I guess you were referring to dex and keycloak as the authorization server. Nevermind I'll see myself out
adam commented 2025-12-29 02:26:41 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 13, 2025):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (Jun 13, 2025): This issue is stale because it has been open for 90 days with no activity.
adam commented 2025-12-29 02:26:41 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 21, 2025):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Jun 21, 2025): This issue was closed because it has been inactive for 14 days since being marked as stale.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label documentation enhancement stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#954
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?