12 Commits

Author	SHA1	Message	Date
John Gardiner Myers	fa053ffba5	Prepare 1.23 branch	2021-08-27 21:07:14 -07:00
John Gardiner Myers	11f28b6d90	Announce k8s removals two kOps versions in advance	2021-05-13 21:32:00 -07:00
John Gardiner Myers	81956f622c	Prepare for kOps 1.22	2021-05-07 13:44:58 -07:00
axpraka	3033caa5e7	Update kops as kOps and remove extra spaces from .md files ... - Updated kops as kOps in .md files. - Remove extra spaces from .md files	2020-11-13 20:09:51 -05:00
John Gardiner Myers	9ecc4b2ec0	Use "remove" instead of "drop" in upgrade_k8s.md	2020-10-29 13:25:37 -07:00
John Gardiner Myers	edfa6a0e94	Adjust Kubernetes version removals and deprecations for 1.20	2020-10-29 13:25:37 -07:00
John Gardiner Myers	07f5e58cac	Bump supported and recommended k8s versions for kops 1.19	2020-06-04 12:11:51 -07:00
John Gardiner Myers	758f8017e4	Deprecate Kubernetes 1.10	2020-03-25 20:10:51 -07:00
John Gardiner Myers	d843915fcf	Announce Kubernetes 1.9 deprecation	2019-12-28 08:49:31 -08:00
Peter Rifel	0a917a1744	Add deprecation warning for older k8s versions ... As discussed during yesterday's office hours. This should be cherry-picked back to 1.16. We'll need to bump the minor version in the 1.17 and master branches. Once we officially drop support we could make this a sliding window that uses the `kops.Version` variable. I think we could have deprecation warnings for the 2 oldest versions still supported by the kops version, announcing that the n+2 Kops version will no longer support the specified k8s version.	2019-12-21 14:47:44 -06:00
mikesplain	7d6165118e	Fix permalink	2019-10-28 08:24:34 -04:00
Justin Santa Barbara	379e0ca098	Channel manifest should be version aware ... * We can target AMIs to kubernetes versions * We can recommend / force a kops upgrade * We can recommend / force a kubernetes upgrade	2017-01-25 23:13:48 -05:00