Skip to content

[🐛 Bug]: Resource Limits missing for pre-pull InitContainer #2398

@Koeppchen

Description

@Koeppchen

What happened?

With 44d9224 an Init Container without resource limits was added. All containers should have resource limits.
Changing templates/_helpers.tpl initContainer to

initContainers:
  - name: "pre-puller-{{ .name }}"
    image: {{ printf "%s/%s:%s" $nodeImageRegistry .node.imageName $nodeImageTag }}
    command: ["bash", "-c", "'true'"]
  {{- with .node.resources }}
    resources: {{- toYaml . | nindent 10 }}
  {{- end }}
{{- if $.Values.videoRecorder.enabled }}
  - name: "pre-puller-{{ $.Values.videoRecorder.name }}"

would already be suficient do do this.

Command used to start Selenium Grid with Docker (or Kubernetes)

helm install

Relevant log output

36s         Warning   FailedCreate        replicaset/selenium4-selenium-edge-node-688b799797      Error creating: admission webhook "validation.gatekeeper.sh" denied the request: [container-must-have-limits] container <pre-puller-selenium4-selenium-edge-node> has no resource limits

Operating System

Kubernetes

Docker Selenium version (image tag)

4.24.0-20240907

Selenium Grid chart version (chart version)

0.35.2

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions