* fixed capitalization - make Service Mesh, Egress/Route Rules lowercase
* added missing definite articles
* rephrase the second paragraph
* rephrase the third paragraph
* will work -> work
* I will copy here -> here is a copy of
* whose boundaries -> the boundaries of which, dashed -> dotted
* rephrase the route rule to details v2
* added commas in the "good news" paragraph
* removed hmm
* rewrote the paragraph about the wildcard feature
* will produce -> produces
* rephrases TLS origination
* 443, the port the service listens to -> 443, which is the port...
* kubernetes deployment, container spec -> Kubernetes Deployment spec, container section
* strong identity -> a strong identity
* in order to -> to
* The trick -> the attack
* rephrase "right now we are working"
* the future releases -> future releases
* we are working -> we're working
* change dot to colon in "let's define an egress rule"
* for the sake of example -> for the sake of the example
* Ruby module -> the Ruby module
* additional case of Service Mesh -> service mesh
* added a comma after and
* additional case of the future releases -> future releases
* added initial version of Egress HTTPS blog, including adding blog section for 2018
* replace dash with comma
* that has Istio installed -> with Istio installed
* route rule -> Route Rule
* app -> application
* restructured error propagation
* could have gone wrong -> might have gone wrong
* which -> that
* the same -> the previous
* moved "now" after "accessing"
* rephrased "the previous error..."
* rewrote the passage about dynamically defined egress rules, marked some terms in bold
* rephrased "written or configured differently"
* IP -> destination IP
* removed "to secure Egress Rules"
* "to add applying" -> "to enable applying"
* rephrased the passage about no tracing, telemetry, mixer checks
* checkss -> checks, tracing/telemetry -> tracing, telemetry
* logging -> tracing
* rephrased the conclusion section
* e.g -> for example
* added "currently" to "Istio cannot perform filtering"
* allow Istio perform -> allow Istio to perform
* "true" string -> _"true"_
* "Egress Rule" is, it enables -> "Egress Rules" are, they enable, just -> only
* rewrote the sentence about the malicious attack
* ... Mixer checks -> ... Mixer checks for the egress traffic
* updated the date to be 26-th of January
* App -> Application
* cluster -> Kubernetes cluster
* added graceful service degradation
* BookInfo -> Bookinfo
* BookInfo -> Bookinfo in a second place
* Book Details displayed without error -> Book Details displayed correctly
* The issues -> Issues
* no Mixer Checks -> No Mixer Checks in section's title
* on the egress traffic -> for the egress traffic
* on the egress traffic -> for the egress traffic, in the second place
* we achieve -> we have
* added Envoy proxy in parenthesis when talking about Istio sidecar proxy
* completed the https from the app diagram, inside/outside of Istio
* added a figure with HTTPS traffic, from inside/outside of Istio
* added a paragraph about the HTTPS traffic figure
* added a paragraph about the port 443
* added "differently," after configured
* replaced places of "from inside" and "from outside"
since "from outside" appears first on the diagram
* container spec -> the `container` spec
* fixed two links
* moved "to external services" after "traffic"
* the Istio Service Mesh -> an Istio Service Mesh
* traffic between the proxy -> traffic between the pod
* the Istio Service Mesh -> an Istio Service Mesh
* has/have to -> must
* the microservice code -> the code of the microservices
* inside/outside of -> inside/outside
* outside of -> outside (removed of)
* Egress Requests -> egress requests
* added derived from the URL's schema
* URL -> URI, added (https://)
* remove .DS_Store, submitted accidentially
* to outside the cluster -> to destinations outside the cluster
* made "block all the traffic to destinations outside the cluster"
* extended the example about the wildcard match of Egress Rules
www.googleapis.com and fcm.googleapis.com
* replaced "now" with "after deleting the Egress Rule"
* fixed calculating the latest blog, thanks to Martin Teillefer
* removed using istio initializer, since starting from 0.5.0 it requires Kubernetes 1.9
* added mentioning of the Istio version for this blog post
* updated the date to be 31 January 2018
* added mentioning that the example work with or without mTLS
* added a sub-section on a relation to Istio Mutual TLS
* Added: The TLS origination for the external services will work, whether the Istio mutual TLS is enabled or not.
* fixed a link to Egress Rules reference
* added a migration use cases for external services
- Stop using the prism functionality for syntax highlighting since
it doesn't handle embedded links in <pre> blocks, which prevents
cross-linking to type names properly. We now roll our own PRE block
handling.
- Stop drawing a box around inline code elements which substantially improves
the visuals, especially in tables.
- Improve appearance of tables to be a bit cleaner.
The documentation change here reflects the work that was done on:
https://github.com/istio/istio/pull/2465
and should only be merged IFF the aforementioned PR is merged
Fixes#837
But we need probably some replacement text
We can’t anyway link to master with line numbers, that wasn’t working
even before we deleted the files
Cc @douglas-reid
I made a last minute change to shrink the header height when on mobile,
but I forgot to compensate for that on the home page, which left a white
gap on the screen. Yuck.
Four major themes to this work:
* Performance. This new site is fast. It loads considerably faster, especially on mobile.
Every pixel is drawn exactly once. Clicking around doesn't result in things jiggling everywhere.
* Navigation. I wanted to make it easier to get around the site, especially on mobile. To that end, we now have:
- Sticky navigation elements. The top nav bar, the left sidebar and the right TOC are now sticky and remain
on screen even as page content is scrolled.
- Tabs in the Docs section have been removed and integrated as accordion items in the left sidebar.
* Layout. I moved a bit of content around to make it easier to find and give us some room to grow:
- The Help page is now replaced with a full Help section. This provides a home for the FAQ, glossary,
bug reporting, and troubleshooting pages.
- The About page is now replaced with a full About section. This provides a home for the release notes, roadmap, upcoming "in the news" section, etc.
* Design. I tried to improve consistency across the site and provide a slightly lighter feel by minimizing the impact of some design elements. Specifics:
- Font sizes are now consistent across the site.
- The site does a much better job at adjusting to different screen sizes which makes the mobile experience better.
- Accessibility is improved by adding many attributes for screen readers, and by ensuring the site scales properly based on user-selected fonts.