Skip to content

feat(server): support openshift restricted-v2 SCC by default#583

Open
oleksandr-codefresh wants to merge 2 commits intomainfrom
osaulyak/server-openshift-scc-support
Open

feat(server): support openshift restricted-v2 SCC by default#583
oleksandr-codefresh wants to merge 2 commits intomainfrom
osaulyak/server-openshift-scc-support

Conversation

@oleksandr-codefresh
Copy link
Copy Markdown

Description

Pre-requisites

  • I have read How we use GitHub Issues for help deciding when and where it's appropriate to make an issue.
  • I have added a changeset with an appropriate customer facing description.
  • I have considered appropriate testing for my change.
  • This PR affects all release versions and will need to be forward merged.

@oleksandr-codefresh oleksandr-codefresh requested review from a team as code owners May 5, 2026 06:34
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 5, 2026

⚠️ No Changeset found

Latest commit: 435d9c6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Comment on lines -150 to -156
runAsNonRoot: true
runAsGroup: 999
runAsUser: 999
readOnlyRootFilesystem: true
podSecurityContext:
fsGroup: 999
fsGroupChangePolicy: OnRootMismatch
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

removed as now our image uses non-root user by default

@oleksandr-codefresh
Copy link
Copy Markdown
Author

need to bump chartVersion / appVersion after 2026.2 released or what to do?

{{- if .Values.serviceAccount.create -}}
{{- default (printf "%s-mssql" (include "octopus.fullname" .)) .Values.serviceAccount.name -}}
{{- else -}}
default "default-mssql" .Values.serviceAccount.name
Copy link
Copy Markdown

@ATGardner ATGardner May 5, 2026

Choose a reason for hiding this comment

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

i am not a helm expert, but shouldn't that be inside some {{ }} ?

Note: `enableDockerInDocker` must be set to `false` when using a read-only root filesystem, as Docker-in-Docker requires a privileged, writable container.

### Openshift
If you are using build in mssql chart on Openshift with values:
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
If you are using build in mssql chart on Openshift with values:
If you are using built-in mssql chart on Openshift with values:

enabled: true
```

Our mssql has such default security contexts for mssql.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
Our mssql has such default security contexts for mssql.
Our mssql has these default security context values:

drop:
- ALL
add:
- NET_BIND_SERVICE
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

why is that needed if the port is 1433 (i think this is only needed when running on ports below 1024)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants