The silent CVE in the heart of Kubernetes apiserver
Has there been any word of how long this has been known about? I recall a certain group of people talking confidently, open but vaguely about a serious k8s security bug at least a few months ago. Given the number of clusters that undoubtedly had to be upgraded for this, it wouldn't surprise me if this was found a while ago.Also, my heart goes out to the [big company] engineering manager asking in the GitHub thread if 1.7.x clusters are affected.