SSH not working due missing security capability in CRI-O environment #176
No reviewers
Labels
No Label
has
backport
in progress
invalid
kind
breaking
kind
bug
kind
build
kind
dependency
kind
deployment
kind
docs
kind
enhancement
kind
feature
kind
lint
kind
proposal
kind
question
kind
refactor
kind
security
kind
testing
kind
translation
kind
ui
need
backport
priority
critical
priority
low
priority
maybe
priority
medium
reviewed
duplicate
reviewed
invalid
reviewed
wontfix
skip-changelog
status
blocked
status
needs-feedback
status
needs-reviews
status
wip
upstream
gitea
upstream
other
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/helm-chart#176
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "volker.raschek/helm-chart:master"
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?
This patch add the SYS_CHROOT capability if the securityContext is
undefined. Otherwise the SSH Server does not work correctly as described
in the issue #161.
Fixes: #161
30a672f055
to4b504feadd
4b504feadd
to0e0583cb3e
WIP as per #161 (comment)
0e0583cb3e
to0b18e467be
(in values.yaml)
Is
SYS_CHROOT
necessary for both image variants? If so, could you pleass extend this comment so that users don't get confused?Maybe something like
...except for clusters using cri-o where SYS_CHROOT needs to be set
. ?@volker.raschek Please update your branch to the latest master and have a look at that comment.
0b18e467be
to7121d5e804
LGTM. Thanks for your effort.
[Close #161] fix: SSH not working due missing security capabilityto SSH not working due missing security capability in CRI-O environment