readonly mount is not supported in kubernetes yaml

[x70b1]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind feature

Description

At the moment a setting like readonly: true is ignored for a mount in a kubernetes yaml.
I found out that it seems to be supported for a cli run: #6380

Steps to reproduce the issue:

spec:
  hostname: dns
  restartPolicy: always
  containers:
    - image: ...
      name: ...
      volumeMounts:
        - name: dnsovertls-config
          mountPath: /etc/unbound/unbound.conf
          readonly: true                                              <------------------------------

  volumes:
    - name: dnsovertls-config
      hostPath:
        path: /srv/podman/dns/dnsovertls/config/unbound.conf
        type: File

Describe the results you received:

The container is still able to write in a file.

Describe the results you expected:

The container should not be able to change a file on the host.

Output of podman version:

podman version 2.0.6

[vrothberg]

Thanks for opening the issue, @x70b1!

@ashley-cui, do you have cycles to tackle the issue?

[ashley-cui]

@vrothberg i'll take a stab at it

[x70b1]

@ashley-cui Thanks a lot for your work.

I have a note here:

In my initial request I used readonly in the yaml tree.
But the Kubernetes docs call it readOnly.

Should this be fixed? Sorry if this creates work again.
But if podman would be compatible to the kubernetes pod yaml that woud be cool for the future.

[ashley-cui]

@x70b1 both readonly and readOnly work with this fix

[x70b1]

Oh, awesome! Thx!