Feature: allow configuring files in volumes without configmaps

[grosser]

atm I need to use a configmap to add files to my fake volumes, for example:

apiVersion: v1
kind: ConfigMap
data:
  process.yaml: |
    init_config:

... and later ...

      volumes:
        - name: configfiles
          configMap:
            name: datadog

this is a bit awkward since the reader has to jump back and forth, but also adds a separate model that needs to be managed / makes the deployment not be atomic (revert without updating configmap -> boom) ... so ideally it be possible to do this configuration inline:

      volumes:
        - name: configfiles
          data:
            process.yaml: |
              init_config:

[k8s-github-robot]

@grosser There are no sig labels on this issue. Please add a sig label by:
(1) mentioning a sig: @kubernetes/sig-<team-name>-misc
(2) specifying the label manually: /sig <label>

Note: method (1) will trigger a notification to the team. You can find the team list here.

[0xmichalis]

/sig storage

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close