Supports PodSecurityContext and Gatling runner container securityContext

[kane8n]

Description

Provide a description of what has been changed

Checklist

Please check if applicable

• Tests have been added (if applicable, ie. when operator codes are added or modified)
• Relevant docs have been added or modified (if applicable, ie. when new features are added or current features are modified)

Relevant issue

#117

operation check

created user and group in the Dockerfile of the sample scenario and confirmed that it works by setting the user/group created in the securityContext.

[annappropriate]

This is great, I would love to be able to specify the sysctls for the port range!

[gold-kou]

Thanks for your PR.
Just nits.

[gold-kou]

I guess this command is not available for a genaral user(1000).
So root(0) is suitable in this case.

[kane8n]

@gold-kou
This configuration is a sample to show that SecurityContext works, and the user/group specified here is created in the Dockerfile to make the sample work.

[gold-kou]

I know this is just a sample, however even if sample, I just thought the value should be appropriate one.
However, as u said this sample works as expected. I checked the value in a gatling runner container.

gatling@gatling-sample01-runner-4ml82:/opt/gatling$ sysctl net.ipv4.ip_local_port_range
net.ipv4.ip_local_port_range = 1024	65535

Looks cool.

[gold-kou]

memo

Sysctls is only available in PodSecurityContext.

[gold-kou]

typo

[gold-kou]

LGTM

[itiB]

I've added procps to gatling/Dockerfile in order to use the ps command and entered the Pod to confirm that the settings are being applied correctly. I was able to verify that both sysctls and port_range are set, so the code you've written seems to be working well! Excellent job.

Checked point

Test simulation manifest

apiVersion: gatling-operator.tech.zozo.com/v1alpha1
kind: Gatling
metadata:
  name: gatling-sample01
spec:
  generateReport: false
  cleanupAfterJobDone: true
  podSpec:
    securityContext:
      runAsUser: 0
      runAsGroup: 0
      sysctls:
        - name: net.ipv4.ip_local_port_range
          value: "1024 65535"
    runnerContainerSecurityContext:
      runAsUser: 1000
      runAsGroup: 1000
    serviceAccountName: "gatling-operator-worker"
    gatlingImage: ghcr.io/st-tech/gatling:latest
  testScenarioSpec:
    parallelism: 3
    simulationClass: "MyBasicSimulation"
    env:
      - name: ENV
        value: "dev"
      - name: CONCURRENCY
        value: "1"
      - name: DURATION
        value: "60"

Detail about created pod

❯ make kind-sample-deploy
Cluster already exists
cd gatling && docker build -t gatling:20240618-120429 .
...
gatling.gatling-operator.tech.zozo.com/gatling-sample01 created

support-security-context ❯ k exec -it gatling-sample01-runner-6b6t2 -- /bin/sh
Defaulted container "gatling-runner" out of: gatling-runner, gatling-waiter (init)
$ ps -eo pid,user,uid,comm
    PID USER       UID COMMAND
      1 gatling   1000 sh
     15 gatling   1000 gatling.sh
     19 gatling   1000 java
     85 gatling   1000 java
    127 gatling   1000 sh
    142 gatling   1000 ps
$ sysctl net.ipv4.ip_local_port_range
net.ipv4.ip_local_port_range = 1024     65535
$