* un-split command lines
* split long text lines
* CA -> Citadel
* update the first paragraph, "you-language" and Service Entries instead of Egress Rules
* fix the subtitle: Egress Rules -> Mesh-external Service Entries
* ServiceEntry -> Service Entry
* add a note that the blog was updated
* Istio 0.3+ -> Istio 0.8+
* changed we/I-language into you-language
* remove mentioning HTTPS as a motivation for TCP egress control
HTTPS is handled now separately by TLS egress control
* replace route/egress rules by virtual services/service entries
* add using MYSQL_DB_HOST and MYSQL_DB_PORT environment variables
* put 1 into backticks
* add an output from the update table command
* instruct the users to apply the default destination rules
* do not use kube-inject in the commands
* add a reminder for users to make sure they applied the default destination rules
* use istioctl replace, update the output
* use bash-inlined service entry with bash variables
* specify a single IP address as a CIDR block with suffix 32
* update the output of deleting the virtual services
* remove kube-inject from deleting a deployment
* instruct the user how to set MYSQL_DB_IP for a local database
* change the update date to 23 of July
* I demonstrate you -> I demonstrate
* add a comma before respectively
* releasearchive -> release archive
* TLS -> HTTPS
* egress rule -> service entry
* remove a redundant empty line
* put the configuration item's path in backticks
* remove future work
* remove "Note:", remove the sentence of the old API to be removed
* data, outside -> data outside
* Extract platform prerequisites
* Reorg
* Remove the inner pages from the menu
* Conform to the site directory structure
* Fix the link wording to match the title of the link and the uppercase
* Fix lint errors
* more lint errors
* Consolidate the security concept pages into a single page.
- This updates the security concept material to be on a single page, which matches the
change done last week for the rest of the concept material. This ends up being a less clicky
more directed introduction for newcomers to the platform.
- While I was there, I moved the redundant What is Istio page from our about section and stuck
the content at the top of the What is Istio page in the Concepts section.
- Add <github_file> <github_blob> and <github_tree> to make it simpler to link to the right
place on GitHub.
- Use these new sequences throughout the docs.
- Also, fix bad HTML generated for the TOC in certain cirsumstances.
- Fix extra blank line inserted at the bottom of indented code blocks.
- Remove What's next sections since we now have auto-generated See also sections
- Fix a few incorrectly capitalized headers, "istio", "kubernetes", "sidecar"
* remove egress TCP task
the example can be implemented by HTTPS Service Entries
* remove a reference to Egress TCP Task in Egress TCP blog
* replace a reference to the Egress TCP task by the Egress TCP blog post
in About -> Feature Status -> Istio features/Traffic management
* add an alias from the removed task to Egress/TCP blog post
- We now automatically generate a See Also section on pages when possible.
The links are determined by a reverse index based on the keywords
assigned to each page in its front-matter.
- Do a pass to assign keywords to all our pages to populate the See Also
links.
- Leverage the keywords in the front-matter to generate a keyword metadata entry for each
generated page.
- Within a code block, you can now surround a relative file path with @@. This will
cause the path to be rendered as a link to raw.githubusercontent.com/istio/istio/<path>.
This lets the user click on the link to see the content of the file, which is mighty
handy.
- Updated all code blocks to take advantage of the above.
- Introduce support for {{< branch_name >}} which returns the source code branch
name associated with the current doc site.
- Use {{< branch_name >}} in all our references to content in istio/istio on GitHub. This thus
pins our references to the correct version of the content in GitHub. This prevents errors from
gradually appearing in our doc set as content in GitHub starts to diverge from the expectation
in the site content.
- Remove some leftover toc:false front matter from a few pages. The site now generally
figures out automatically that a TOC is not necessary.
- Enable a Hugo feature that queries Git for a last modified date on files. As a result,
instead of having the site build date in the footer, we now have a "this page was last modified"
date.
- Move the landing page's content out of the layouts directory and into the content directory
where it belongs.
- Use Hugo shortcodes for our embedded icon imagery. And make those icons scale with the
font size rather than being fixed sizes.
- Enable support for emojis in our content. Just use ⛵
and you'll get a sailboat for example.
mtail
Limin Wang
Vadim Eisenberg
Martin Taillefer
Andra Cismaru
Frank Budinsky
Isaiah Snell-Feikema
Yossi Mesika
gargnupur
Vincent
Jimmy Song
imgbot[bot]
Hong Zhiguo