{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/website/issues/6529","repository_url":"https://api.github.com/repos/kubernetes/website","labels_url":"https://api.github.com/repos/kubernetes/website/issues/6529/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/website/issues/6529/comments","events_url":"https://api.github.com/repos/kubernetes/website/issues/6529/events","html_url":"https://github.com/kubernetes/website/issues/6529","id":278383681,"number":6529,"title":"Make ConfigMaps Usable in Compact key: value Assignments","user":{"login":"Hardy2015","id":10435917,"avatar_url":"https://avatars2.githubusercontent.com/u/10435917?v=4","gravatar_id":"","url":"https://api.github.com/users/Hardy2015","html_url":"https://github.com/Hardy2015","followers_url":"https://api.github.com/users/Hardy2015/followers","following_url":"https://api.github.com/users/Hardy2015/following{/other_user}","gists_url":"https://api.github.com/users/Hardy2015/gists{/gist_id}","starred_url":"https://api.github.com/users/Hardy2015/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Hardy2015/subscriptions","organizations_url":"https://api.github.com/users/Hardy2015/orgs","repos_url":"https://api.github.com/users/Hardy2015/repos","events_url":"https://api.github.com/users/Hardy2015/events{/privacy}","received_events_url":"https://api.github.com/users/Hardy2015/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2017-12-01T07:46:47Z","updated_at":"2017-12-01T16:00:48Z","closed_at":"2017-12-01T10:13:22Z","author_association":"NONE","body":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. -->\r\n\r\n<!--Required Information-->\r\n\r\n**This is a...** \r\n<!-- choose one by changing [ ] to [x] -->\r\n- [x] Feature Request\r\n- [ ] Bug Report\r\n\r\n**Problem:**\r\n\r\nConfigMaps are a very cool feature. I'm using it to decouple key/value pairs like \r\n```\r\n      - env:\r\n        - name: jaas_owner\r\n          value: D023081\r\n```\r\nby replacing ```value``` by \r\n```  \r\n     valueFrom:\r\n            configMapKeyRef:.....\r\n```\r\n\r\nHowever, I would also like to replace other attributes in my rc.yaml, that come more compact, like: \r\n```\r\n        resources:\r\n          limits:\r\n            cpu: \"4\"\r\n            memory: 30Gi\r\n          requests:\r\n            cpu: 500m\r\n            memory: 7Gi\r\n``` \r\n\r\nAfter reading the documentation, I didn't find a way to decouple the \"4\" in ```cpu``` through a ConfigMap. \r\n\r\n**Proposed Solution:**\r\n\r\nPlease make ConfigMaps also availabe to the compact ```key: value``` syntax like ```cpu: \"4\"```\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/website/issues/comments/348532901","html_url":"https://github.com/kubernetes/website/issues/6529#issuecomment-348532901","issue_url":"https://api.github.com/repos/kubernetes/website/issues/6529","id":348532901,"user":{"login":"Hardy2015","id":10435917,"avatar_url":"https://avatars2.githubusercontent.com/u/10435917?v=4","gravatar_id":"","url":"https://api.github.com/users/Hardy2015","html_url":"https://github.com/Hardy2015","followers_url":"https://api.github.com/users/Hardy2015/followers","following_url":"https://api.github.com/users/Hardy2015/following{/other_user}","gists_url":"https://api.github.com/users/Hardy2015/gists{/gist_id}","starred_url":"https://api.github.com/users/Hardy2015/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Hardy2015/subscriptions","organizations_url":"https://api.github.com/users/Hardy2015/orgs","repos_url":"https://api.github.com/users/Hardy2015/repos","events_url":"https://api.github.com/users/Hardy2015/events{/privacy}","received_events_url":"https://api.github.com/users/Hardy2015/received_events","type":"User","site_admin":false},"created_at":"2017-12-01T16:00:48Z","updated_at":"2017-12-01T16:00:48Z","author_association":"NONE","body":"Thank you very much. Yes, LimitRange goes into the right direction. However in my given namespace, there are 400 RCs of smaller size and 250 RCs of larger size. Technically, they are the same thing, which is why they live in the same namespace. Apparently, LimitRange only allows me to restrict all namespace inhabitants at the same time.  I tried to distinguish the both through\r\n```\r\nspec:\r\n  selector:\r\n    matchLabels:\r\n      imageType: basic\r\n```\r\nBut this seems to be not allowed here: \r\n```\r\nerror: error validating \"basic-limit-range\": error validating data: found invalid field selector for v1.LimitRangeSpec; if you choose to ignore these errors, turn validation off with --validate=false\r\n```\r\nAm I overlooking something, where I could configure the both specifically? "}}
{"actor":{"display_login":"Hardy2015"}}