goauthentik / goauthentik/authentik

SSH Docker outpost service connection missing the worker SSH key

Open
#25,257 0 comments 0 reactions 0 assignees View on GitHub
bug bug/confirmed
Dominant language
Python
Stars
25.6k
Forks
2k
Avg merge
1d 2h
Merged PRs (30d)
651

Description

## What

Docker/SSH outpost service-connection fails because the SSH key/config is missing or unused on the worker (including K8s multi-replica).

## Want

- Docker/SSH outpost service-connection fails because the SSH key/config is missing or unused on the worker (including K8s multi-replica)

## Ideas this came from

- [#3679 Docker Outpost integration via SSH not working](https://github.com/goauthentik/authentik/issues/3679) — Describe your question/ Authentik 2022.9.0. Am I properly configuring the remote docker outpost deployment using ssh? I am attempting to use the automatic docke
- [#4314 SSH Outpost integrations not working](https://github.com/goauthentik/authentik/issues/4314) — SSH Outpost integrations not working, possibly a problem with the SSH configuration file on the worker. To Reproduce Steps to reproduce the behavior: 1. Add SSH
- [#22968 SSH Docker Connection not working in Kubernetes Deployment](https://github.com/goauthentik/authentik/issues/22968) — When trying to create an authentik-managed Docker Outpost using ssh from a ha Kubernetes setup, the authentik.outposts.tasks.outpostcontroller task fails due to

Contributor guide

Open the contributing guide

Research direction

Start at the authentik.outposts.tasks.outpostcontroller task mentioned in the related Kubernetes issue and reproduce the Docker/SSH service-connection failure with multiple worker replicas. Compare the related issues #3679, #4314, and #22968 to trace how the worker receives SSH key/configuration. Done means the connection succeeds reliably, including in a Kubernetes multi-replica deployment.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, kubernetes, python
Domain
backend, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.