Dialer pod does not conform to restricted pod security profile

Open
#3,517 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go, kubernetes
Domain
infrastructure, security

Research direction

Locate the in-cluster dialer pod definition in the repository and inspect how its security context is configured. Compare the pod against the restricted pod security profile requirements named in the issue, then verify that the resulting deployment no longer produces warnings or fails under enforcement.

Written by the indexing model from the issue text.

Description

The in-cluster dialer pod used during deployment does not set the
security context fields required by the "restricted" pod security
profile: allowPrivilegeEscalation, capabilities drop, runAsNonRoot,
and seccompProfile.

This produces warnings on clusters enforcing pod security admission
and will fail on clusters that enforce (rather than warn) the
restricted profile.

Related: SRVOCF-445

Dominant language
Go
Stars
365
Forks
223
Avg merge
2d 3h
Merged PRs (30d)
25

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from knative/func

All issues in knative/func

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.