* initial eol announcement for 1.17
* Update content/en/news/support/announcing-1.17/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/support/announcing-1.17/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/support/announcing-1.17/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* rename and fix date
* Update content/en/news/support/announcing-1.17-eol/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/support/announcing-1.17-eol/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
---------
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
We dropped support for 1.20 which was the main part of this PR. But I also think we can shift to 1.28 - we are already testinng pre-releases, and k8s will release before we do so should be fine. We can always change it once we ship 1.19, this doesn't commit us to anything. its only for preliminary.istio.io.
* initial draft
* Fix typo
* remove 1.22 k8s warning
* Updating supportStatus table
* Update content/en/news/releases/1.18.x/announcing-1.18/_index.md
Co-authored-by: jacob-delgado <jacob.delgado@volunteers.acasi.info>
* Update content/en/news/releases/1.18.x/announcing-1.18/_index.md
Co-authored-by: Xiaopeng Han <hanxiaop8@outlook.com>
* Review fixes
* Fix trailing -
* Finished first draft
* Minor change
* Fixed linting issues save for link checking
* Update content/en/news/releases/1.18.x/announcing-1.18/_index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/releases/1.18.x/announcing-1.18/upgrade-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/releases/1.18.x/announcing-1.18/upgrade-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/releases/1.18.x/announcing-1.18/_index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Minor wording change
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Fix line break
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Fixing .spelling
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Minor fixes
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Review fixes
* Changes to .spelling
* Update content/en/news/releases/1.18.x/announcing-1.18/change-notes/index.md
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update release date
* Added more issue links
---------
Co-authored-by: jacob-delgado <jacob.delgado@volunteers.acasi.info>
Co-authored-by: Xiaopeng Han <hanxiaop8@outlook.com>
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Reformat dates to use a consistent format
Consistency looks better, and formatting to a short month keeps things on a single line except when
(Expected) is added to the End of Life fields.
* Update data/compatibility/supportStatus.yml
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* add periods to shortened month names
* remove periods
---------
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* breakout support status table to yaml file
* use k8s versions from new yaml file, based off previous ver
* same as previous commit but based off idx of yaml obj
* trim whitespace from supported k8s vers shortcode
* make verion lists arrays instead of strings
* update shortcode to read yaml data array
* rename support status shortcode to follow naming convention
* make versions in table use new arrays, update reference to support status table
* make each version in yaml file a string
* update header comment, change ext to *.yml to follow repo convention
* use prelim ternary to select k8s versions
* update supportStatus.yml heading comments
* update supported k8s shortcode to use branch name
* initial commit of python support status updater
* add null representer
* use lambda for quoted representer
* put back master population off idx 1, update comments
* working stdout version complete: use flow style for version list keys
* prepend yaml with header comments, cleanup script
* perform version check, default write errors are more helpful
* add copyright and license info
* linter has some weird tastes
* this is 100% worse but if it makes the linter happy
* call update_support_status.py from within create version
* update version matrix path since script ran from repo root
* use yq for updating the version support matrix instead of PyYAML
Xiaopeng Han
John Howard
Daniel Hawton
Kalya Subramanian
Daniel Hawton
Paul Merrison
Eric Van Norman
Skyler Spaeth