Skip to content

config.yaml parameter integration.kubernetes.pod_name unclear in case of separate pods #443

@jessebot

Description

@jessebot

Description

Hoi again!

Right now, the config example says the integration.kubernetes.pod_name parameter comment points at a file that I can seem to find (docs/Integrated-Mode.md ) and I'm not sure what to do in the case that headplane lives in a separate pod from headscale 🤔 :

  # Please refer to docs/integration/Kubernetes.md for more information
  # on how to configure the Kubernetes integration. There are requirements in
  # order to allow Headscale to be controlled by Headplane in a cluster.
  kubernetes:
    enabled: false
    # Validates the manifest for the Pod to ensure all of the criteria
    # are set correctly. Turn this off if you are having issues with
    # shareProcessNamespace not being validated correctly.
    validate_manifest: true
    # This should be the name of the Pod running Headscale and Headplane.
    # If this isn't static you should be using the Kubernetes Downward API
    # to set this value (refer to docs/Integrated-Mode.md for more info).
    pod_name: "headscale"

If you could help me understand how to proceed better, I'm happy to help update any comments or docs 🙏

Headplane Version

v0.6.1

Headscale Version

v0.27.1

Metadata

Metadata

Assignees

Labels

BugSomething isn't workingNeeds TriageIssues yet to be triaged

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions