Skip to content

chore: enable MEN-8168 feature flag in the useradm service #492

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kjaskiewiczz wants to merge 1 commit into
base: staging
Choose a base branch
from
Open

chore: enable MEN-8168 feature flag in the useradm service #492

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions mender/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -835,6 +835,7 @@ useradm:
USERADM_REDIS_TIMEOUT_SEC: "1"
USERADM_REDIS_LIMITS_EXPIRE_SEC: "3600"
USERADM_TOTP_ISSUER: Mender
USERADM_MEN-8168: "true"

@alfrunes alfrunes Oct 21, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately, this change won't introduce any change on the templates itself. All the env.* values are actually hard-coded values in the pod template. You could use customEnvs value, but I don't think that's good practice.
I think this is a better candidate to put under the featureGates value as this is something we plan on making the default (remove) on the next major release.

podSecurityContext:
enabled: false
runAsNonRoot: true
Expand Down