- Move some info to front-matter in the different security bulletins
such that it can be used when building the security bulleting index page.
- Update the security bulletin index page to show affected relesses and
impact score.
- Make it so table headers are vertically centered, which looks a lot nicer
when there are a combination of single-line and multi-line headers in the
same table.
- Add a few checks to correctly hide draft mode documents from sight
in more cases.
- Remove a stale document that's been in draft mode since first being
created in 2017.
- Clean up a bit of text in some release notes.
- If a returning user comes to the site, if there are unread
blog posts or news articles less than 15 quadrllion nanosecond
old will be treated as being unread. When there are unred articles,
the News or Blog link in the title bar will get a green dot indicating
articles are available. When clicking on News, then you'll get the
news categories with a pill showing how many articles are unread for
each category.
First-time visitors to the site will not get any dots or pills for
existing articles. These will only appear in subsequent visits for
new articles.
Due to the default behavior for new users, if you just look at the
preview, you will not see any pills or dots. To see what this actually
looks like, load up the preview, then go to the Chrome Developer Tools,
click on the Application tab, then on Local Storage, and then find the
visitedPages entry. Right click on the entry, select Edit Value,
and set the value to {}. Then refresh the page and you
should see some dots show up next to the Blog and News links in
the header.
- Security bulletins now have a cleaner style, with a common table
at the top capturing common info.
- Generate a custom table when showing the list of bulletins.
* Added the Best Practices section with general principles.
This is the beginning of the new Best Practices section.
Our goal is to provide a section for all the best practices and recommendations
for Istio deployments. The best practices are based on the identified and
recommended deployment models.
Signed-off-by: rcaballeromx <grca@google.com>
* Change headings for clarity.
Adds clarity to some passages based on feedback.
Removes a list of recommendations that was causing some confusion.
Adds a glossary entry for failure domains and how they relate to a
platform's availability zones.
Signed-off-by: rcaballeromx <grca@google.com>
* Move Best Practices to Ops Guide
Signed-off-by: rcaballeromx <grca@google.com>
* Moved Deployment Best Practices to a new "Prepare Your Deployment" section.
Moved all deployment preparation content into a new section under "Setup".
For now the content includes the following sections:
- Deployment models
- Deployment best practices
- Pod requirements
Merged the two existing pages containing pod requirements into one single page.
Signed-off-by: rcaballeromx <grca@google.com>
* Replace example with better guidance around namespace tenancy.
Signed-off-by: Rigs Caballero <grca@google.com>
* Add links and language pointing to the Prepare section
Signed-off-by: Rigs Caballero <grca@google.com>
* Fix minor typos and broken links.
Signed-off-by: Rigs Caballero <grca@google.com>
* Move from Setup to Operations
Signed-off-by: Rigs Caballero <grca@google.com>
* Fix broken links
Signed-off-by: Rigs Caballero <grca@google.com>
* Fix rebasing issues.
Signed-off-by: Rigs Caballero <grca@google.com>
* Fix multicluster install link.
Signed-off-by: Rigs Caballero <grca@google.com>
* Added release notes for 1.3.5
* Cleaned up description of Issue 16458 and 17266
* Cleaned up wording for 17266
* added entry for ISTIO-SECURITY-2019-006 and two more bug fix entries
* Make update lowercase
Co-Authored-By: Martin Taillefer <geeknoid@users.noreply.github.com>
* Added CVE
- Improved look of the call to action buttons
- Removed redundant attributions on all news items, those were
leftovers from when the relesse notes were in the blog section.
- Used consistent subtitles and descriptions for all news items.
* Initial 1.4.0 release notes
There will definitely be more release notes to add in the future, but
for now I think we can focus on getting a few in and iterate from there
to try to avoid the 300 comment PR madness.
* Update content/en/news/2019/announcing-1.4/change-notes/index.md
Co-Authored-By: Rigs Caballero <grca@google.com>
* Apply suggestions from code review
Co-Authored-By: Rigs Caballero <grca@google.com>
* Update content/en/news/2019/announcing-1.4/change-notes/index.md
Co-Authored-By: Rigs Caballero <grca@google.com>
* Fix mirror notes
* Update content/en/news/2019/announcing-1.4/change-notes/index.md
Co-Authored-By: Martin Taillefer <geeknoid@users.noreply.github.com>
* Replace daily builds
- Fix a bunch of heading capitalization.
- Remove words that shouldn't be in the dictionary
and update the text accordingly.
- Added a few @@ sequences to reference content files from text blocks.
- Used a few {{< source_branch_name >}} sequences to refer to the proper
branch in GitHub rather than master.
* Draft of upgrade docs
* Fixed PR comments
* More PR review comments addressed
* Added note about -f and --set flag support
* Further PR comments
* shortcode added for istioctl
* rebase and typo fixes
* Typo fixes
* 1.1 release notes
* Cleaned up wording and formatting to match other point release
* Updated to remove UTF-8 from spelling as well as link to the last issue
* Moved release announcement to news
* Fixed capitalization and removed aliases for 1.3.1 release notes
* Removed references to pull requests rather than issues and added reference for metadata exchange and stats
* Added WebAssembly to the dictionary and removed duplicate of webhook
* Fixed date
Martin Taillefer
Steve Manuel
Frank Budinsky
Jianfei Hu
Phillip Quy Le
Yangmin Zhu
Lin Sun
Rigs Caballero
John Howard
lei-tang
Dan Ciruli
Francois Pesce
Brian Avery
Neeraj Poddar
Steven Dake
Istio Automation
Adam Miller
Jason Wang
Joshua Blatt
Ed Snible