mirror of https://github.com/istio/istio.io.git
535f68b81d
* 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 |
||
|---|---|---|
| .circleci | ||
| _about | ||
| _blog | ||
| _data | ||
| _docs | ||
| _faq | ||
| _glossary | ||
| _help | ||
| _includes | ||
| _layouts | ||
| _sass | ||
| css | ||
| favicons | ||
| img | ||
| js | ||
| scripts | ||
| talks | ||
| .firebaserc | ||
| .gitignore | ||
| 404.md | ||
| BingSiteAuth.xml | ||
| CNAME | ||
| CONTRIBUTING.md | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| README.md | ||
| Rakefile | ||
| _config.yml | ||
| browserconfig.xml | ||
| community.md | ||
| feed.xml | ||
| firebase.json | ||
| index.html | ||
| manifest.json | ||
| robots.txt | ||
| search.md | ||
README.md
istio.github.io
This repository contains the source code for the istio.io web site.
Please see the main Istio README file to learn about the overall Istio project and how to get in touch with us. To learn how you can contribute to any of the Istio components, please see the Istio contribution guidelines.
The website uses Jekyll templates and is hosted on GitHub Pages. Please make sure you are familiar with these before editing.
To run the site locally with Docker, use the following command from the toplevel directory for this git repo
(e.g. pwd must be ~/github/istio.github.io if you were in ~/github when you issued
git clone https://github.com/istio/istio.github.io.git)
# First time: (slow)
docker run --name istio-jekyll --volume=$(pwd):/srv/jekyll -it -p 4000:4000 jekyll/jekyll:3.5.2 sh -c "bundle install && rake test && bundle exec jekyll serve --incremental --host 0.0.0.0"
# Then open browser with url 127.0.0.1:4000 to see the change.
# Subsequent, each time you want to see a new change and you stopped the previous run by ctrl+c: (much faster)
docker start istio-jekyll -a -i
# Clean up, only needed if you won't be previewing website changes for a long time or you want to start over:
docker rm istio-jekyll
The rake test part is to make sure you are not introducing html errors or bad links, you should see
HTML-Proofer finished successfully.
in the output
Local/Native Jekyll install:
Alternatively, if you just want to develop locally w/o Docker/Kubernetes/Minikube, you can try installing Jekyll locally. You may need to install other prerequisites manually (which is where using the docker image shines). Here's an example of doing so for Mac OS X:
xcode-select --install
sudo xcodebuild -license
brew install ruby
gem update --system
gem install bundler
gem install jekyll
cd istio.github.io
bundle install
bundle exec rake test
bundle exec jekyll serve