7 Commits (cd25bbee468fe00c2bc6ea7eefc7de7e6846e526)

Author	SHA1	Message	Date
Michael Taufen	503a6a8eec	Add --append-hash flag to kubectl create configmap/secret ... Specifying this new flag will automatically hash the configmap/secret contents with sha256 and append the first 40 hex-encoded bits of the hash to the name of the configmap/secret. This is especially useful for workflows that generate configmaps/secrets from files (e.g. --from-file). Note that vowels and vowel-like characters in the hash are remapped to consonants to make it more difficult to accidentally form bad words. See this Google doc for more background: https://docs.google.com/document/d/1x1fJ3pGRx20ujR-Y89HUAw8glUL8-ygaztLkkmQeCdU/edit	2017-08-28 14:17:47 -07:00
Timo Reimann	604dfb3197	Relax restrictions on environment variable names. ... The POSIX standard restricts environment variable names to uppercase letters, digits, and the underscore character in shell contexts only. For generic application usage, it is stated that all other characters shall be tolerated. This change relaxes the rules to some degree. Namely, we stop requiring environment variable names to be strict C_IDENTIFIERS and start permitting lowercase, dot, and dash characters. Public container images using environment variable names beyond the shell-only context can benefit from this relaxation. Elasticsearch is one popular example.	2017-07-28 22:11:26 +02:00
Michael Fraenkel	7eb49628c6	create configmap from-env-file	2017-03-08 07:58:01 -08:00
Clayton Coleman	9a2a50cda7	refactor: use metav1.ObjectMeta in other types	2017-01-17 16:17:19 -05:00
David McMahon	ef0c9f0c5b	Remove "All rights reserved" from all the headers.	2016-06-29 17:47:36 -07:00
derekwaynecarr	25ed62c3ea	Fix kubectl create secret/configmap to allow = values	2016-05-04 17:14:12 -04:00
Paul Morie	51a9c2c9ba	Add kubectl create configmap	2016-02-18 21:24:21 -05:00