Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix links related to projection of keys and file permissions in the ConfigMap documentation #44748

Merged
merged 1 commit into from
Jan 16, 2024
Merged

Fix links related to projection of keys and file permissions in the ConfigMap documentation #44748

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -728,10 +728,8 @@ kubectl delete pod dapi-test-pod --now

### Project keys to specific paths and file permissions

You can project keys to specific paths and specific permissions on a per-file
basis. The
[Secrets](/docs/concepts/configuration/secret/#using-secrets-as-files-from-a-pod)
guide explains the syntax.
You can project keys to specific paths. Refer to the corresponding section in the [Secrets](/docs/tasks/inject-data-application/distribute-credentials-secure/#project-secret-keys-to-specific-file-paths) guide for the syntax.
You can set POSIX permissions for keys. Refer to the corresponding section in the [Secrets](/docs/tasks/inject-data-application/distribute-credentials-secure/#set-posix-permissions-for-secret-keys) guide for the syntax.
Copy link
Contributor

Choose a reason for hiding this comment

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

How about:

[more text here]

### Set POSIX permissions for ConfigMap keys

You can set the POSIX file access permission bits for a single key in a volume
backed by a ConfigMap.
If you don't specify any permissions, `0644` is used by default.
You can also set a default POSIX file mode for the entire ConfigMap volume, and
you can override per key if needed.

For example, you can specify a default mode like this:

```yaml
apiVersion: v1
kind: Pod
metadata:
  name: mypod
spec:
  containers:
  - name: mypod
    image: redis
    volumeMounts:
    - name: foo
      mountPath: "/etc/foo"
  volumes:
  - name: foo
    configMap:
      configMapName: example-configmap
      defaultMode: 0400

The ConfigMap is mounted on /etc/foo; all the files created by the
ConfigMap volume mount have permission 0400.

{{< note >}}
If you're defining a Pod or a Pod template using JSON, beware that the JSON
specification doesn't support octal literals for numbers because JSON considers
0400 to be the decimal value 400. In JSON, use decimal values for the
defaultMode instead. If you're writing YAML, you can write the defaultMode
in octal.
{{< /note >}}


### Optional references

Expand Down