feat!(rsyncd): add sshd
as an alternative Rsync Daemon to rsyncd
#1434
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to jenkins-infra/helpdesk#4402
This PR adds the support of an alternative rsync backend:
sshd
in thersyncd
chart.It introduces a set for changes, which most of them are breaking and requires values updates:
nobody:nogroup
(65534:65534
) torsyncd:rsyncd
(1000:1000
)/nowhere
to/home/rsyncd
run
temp dir for PID files changes from/run
to/home/rsyncd/run
rsyncd
) directories (data/
,/etc
) changes to/home/rsyncd/*
sshd
instead ofrsyncd
, configured by the new valueconfiguration.rsyncd_daemon
set tosshd
. Otherwise defaults torsyncd
. When enabled:1873
to2222
(unless specified through the valueport
)873
to22
(unless specified through the valueservice.port
)2.1.0
(ref. jenkins-infra/docker-rsyncd@1.0.68...2.1.0)rsyncd
can be specified using the valueconfiguration.sshd.public_key
configuration.sshd.log_level
(defaults toINFO
)configuration.motd
is now ignoredconfiguration.components
directive may have writing enabled with the new attributewriteEnabled