{"action":"created","issue":{"url":"https://api.github.com/repos/coreos/vault-operator/issues/311","repository_url":"https://api.github.com/repos/coreos/vault-operator","labels_url":"https://api.github.com/repos/coreos/vault-operator/issues/311/labels{/name}","comments_url":"https://api.github.com/repos/coreos/vault-operator/issues/311/comments","events_url":"https://api.github.com/repos/coreos/vault-operator/issues/311/events","html_url":"https://github.com/coreos/vault-operator/issues/311","id":317450895,"number":311,"title":"is the IPC_LOCK capability really needed?","user":{"login":"raffaelespazzoli","id":6179036,"avatar_url":"https://avatars2.githubusercontent.com/u/6179036?v=4","gravatar_id":"","url":"https://api.github.com/users/raffaelespazzoli","html_url":"https://github.com/raffaelespazzoli","followers_url":"https://api.github.com/users/raffaelespazzoli/followers","following_url":"https://api.github.com/users/raffaelespazzoli/following{/other_user}","gists_url":"https://api.github.com/users/raffaelespazzoli/gists{/gist_id}","starred_url":"https://api.github.com/users/raffaelespazzoli/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/raffaelespazzoli/subscriptions","organizations_url":"https://api.github.com/users/raffaelespazzoli/orgs","repos_url":"https://api.github.com/users/raffaelespazzoli/repos","events_url":"https://api.github.com/users/raffaelespazzoli/events{/privacy}","received_events_url":"https://api.github.com/users/raffaelespazzoli/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-04-25T01:38:33Z","updated_at":"2018-04-27T05:34:20Z","closed_at":null,"author_association":"NONE","body":"Vault operator creates a vault deployment requesting the IPC_LOCK capability.\r\nBut in kubernetes swap is mandatorily disabled (the kubelet now doesn't start if swap is active).\r\nSo, if vault can be set to run with `disable_mlock=true`, then the IPC_LOCK can be probably removed.\r\nThis makes deployment simpler in those organization where pod security contexts (kubernetes) or scc (OpenShift) are closely scrutinized."},"comment":{"url":"https://api.github.com/repos/coreos/vault-operator/issues/comments/384868903","html_url":"https://github.com/coreos/vault-operator/issues/311#issuecomment-384868903","issue_url":"https://api.github.com/repos/coreos/vault-operator/issues/311","id":384868903,"user":{"login":"ncorrare","id":1202900,"avatar_url":"https://avatars0.githubusercontent.com/u/1202900?v=4","gravatar_id":"","url":"https://api.github.com/users/ncorrare","html_url":"https://github.com/ncorrare","followers_url":"https://api.github.com/users/ncorrare/followers","following_url":"https://api.github.com/users/ncorrare/following{/other_user}","gists_url":"https://api.github.com/users/ncorrare/gists{/gist_id}","starred_url":"https://api.github.com/users/ncorrare/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ncorrare/subscriptions","organizations_url":"https://api.github.com/users/ncorrare/orgs","repos_url":"https://api.github.com/users/ncorrare/repos","events_url":"https://api.github.com/users/ncorrare/events{/privacy}","received_events_url":"https://api.github.com/users/ncorrare/received_events","type":"User","site_admin":false},"created_at":"2018-04-27T05:34:20Z","updated_at":"2018-04-27T05:34:20Z","author_association":"NONE","body":"A the same time, Vault is ultimately a security product, so the idea of potentially swapping secrets that should be only available in memory is a considerable threat vector."}}
{"actor":{"display_login":"ncorrare"}}