Improvement for k8s.io/docs/concepts/configuration/secret/

[Ostromix]

Can you please add in documentation menu description about using such type of construction in
SECRET description in documentation

apiVersion: v1
kind: Pod
metadata:
labels:
name: supername
name: supername
namespace: supernamespace
spec:
containers:

• image: superrepo/superimage
  name: supername
  envFrom:
  • secretRef:
    name: mysupersecret

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[aryasoni98]

/assign

[utkarsh-singh1]

Page link -> https://kubernetes.io/docs/concepts/configuration/secret/

/language en

[utkarsh-singh1]

@Ostromix, there can be multiple ways to use secrets in PodSpec like using envFrom, valueFrom etc.

[utkarsh-singh1]

So it will be better to point out the usage of such cases in the docs.

[network-charles]

I believe this is what you are looking for.

https://kubernetes.io/docs/tasks/inject-data-application/distribute-credentials-secure/#configure-all-key-value-pairs-in-a-secret-as-container-environment-variables

This section describes an example that uses the “envFrom” field.

[utkarsh-singh1]

This section describes an example that uses the “envFrom” field.

@Ostromix as above command describes there is already available, so I don't think there is need to change any docs, but we can mention this page in whats next section.

[network-charles]

@utkarsh-singh1, the page is already referenced in this section.