Probably useful... https://golang.org/pkg/unicode/utf8/#Valid

EXPERIMENTAL JENKINS PR BUILDER: e2e build succeeded.

@pmorie same question. If you like it, I'll update this pull.

I don't think we should print secret contents by default.
People are going to send in kubectl describe output in bug reports, and they don't want to accidentally send in a secret.

does describe take flags? do we want another command to show secret content?

I don't think we should print secret contents by default.
People are going to send in kubectl describe output in bug reports, and they don't want to accidentally send in a secret.

Being able to see secret content is very useful when debugging the system. Things like "I made this secret, but my pod keeps telling me that it doesn't have access. Let me try that secret manually.". I'd like to have some way to see them.

Fine with having a way to show it. But it should definitely take some extra effort to show it.

and the raw get -o yaml is comically hard to use, since you have to extract the value and base64 decode it yoursefl

Fine with having a way to show it. But it should definitely take some extra effort to show it.

sorry, bad button click:

Fine with having a way to show it. But it should definitely take some extra effort to show it.

Would you see that as an additional argument to describe (--show-confidential?), a separate command, or something else? I can't think of anything else we have that is confidential.

@deads2k

--show-confidential

I like that idea.

Embarassing: I reviewed #7101 which added secret describers. Should have commented then. 😳

sorry

GCE e2e build/test passed for commit a8a966e.

• Build Log
• Test Artifacts
• Internal Jenkins Results

Closing in favor of openshift/origin#3915