{"action":"created","issue":{"url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/3560","labels_url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/3560/labels{/name}","comments_url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/3560/comments","events_url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/3560/events","html_url":"https://github.com/GoogleCloudPlatform/kubernetes/issues/3560","id":54588549,"number":3560,"title":"Define supported version skew between components","user":{"login":"erictune","id":8105590,"avatar_url":"https://avatars.githubusercontent.com/u/8105590?v=3","gravatar_id":"","url":"https://api.github.com/users/erictune","html_url":"https://github.com/erictune","followers_url":"https://api.github.com/users/erictune/followers","following_url":"https://api.github.com/users/erictune/following{/other_user}","gists_url":"https://api.github.com/users/erictune/gists{/gist_id}","starred_url":"https://api.github.com/users/erictune/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/erictune/subscriptions","organizations_url":"https://api.github.com/users/erictune/orgs","repos_url":"https://api.github.com/users/erictune/repos","events_url":"https://api.github.com/users/erictune/events{/privacy}","received_events_url":"https://api.github.com/users/erictune/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-01-16T15:38:09Z","updated_at":"2015-01-16T15:38:54Z","closed_at":null,"body":" Upgrades are described broadly in issue #2524.  This issue is about defining our support window for a specific case in upgrades.\r\n\r\nTypically a user starts a cluster with all the software components built at the same version.\r\nThen the user wants to do an upgrade.  The user may need to upgrade one component before the others, (e.g. master before the nodes).  Reasons include:, perfectly synchronized and simultaneous upgrades are infeasible; the user may want to stage work; user error; etc.\r\n\r\nTherefore, \"nearby\" versions of components must work with each other.  However, kubernetes developers can't be expected to maintain compatibility between very different software versions.  \r\n\r\nWe should define how far apart we allow versions of components to be.\r\n\r\nOptions:\r\n  - any components that share the same api-version will work together.  E.g if master support v1beta1 and kubelet supports v1beta1, then they will work together.\r\n  - one minor revision:  e.g. v0.8.5 master will work with v0.9.9 kubelet and v0.7.1 kubelet  but not with v0.6.5 or v0.10.1\r\n  - compatibility matrixes, or deprecation schedules\r\n"},"comment":{"url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/comments/70271012","html_url":"https://github.com/GoogleCloudPlatform/kubernetes/issues/3560#issuecomment-70271012","issue_url":"https://api.github.com/repos/GoogleCloudPlatform/kubernetes/issues/3560","id":70271012,"user":{"login":"erictune","id":8105590,"avatar_url":"https://avatars.githubusercontent.com/u/8105590?v=3","gravatar_id":"","url":"https://api.github.com/users/erictune","html_url":"https://github.com/erictune","followers_url":"https://api.github.com/users/erictune/followers","following_url":"https://api.github.com/users/erictune/following{/other_user}","gists_url":"https://api.github.com/users/erictune/gists{/gist_id}","starred_url":"https://api.github.com/users/erictune/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/erictune/subscriptions","organizations_url":"https://api.github.com/users/erictune/orgs","repos_url":"https://api.github.com/users/erictune/repos","events_url":"https://api.github.com/users/erictune/events{/privacy}","received_events_url":"https://api.github.com/users/erictune/received_events","type":"User","site_admin":false},"created_at":"2015-01-16T15:38:54Z","updated_at":"2015-01-16T15:38:54Z","body":"This came up in issue #2483 "}}