* Modify build_site.sh to work with new build-tools image
babel-cli must be used instead of babel. babel=version6,
babel-cli=version7. I don't know the details, but make serve
seems to work well enough.
I had to drop a minifier rule. We can reintroduce this rule.
The babel-cli required a reordering of command line args.
* Take 2
* Make netlify work properly
* Mesh Expansion with gateways
* format
* format
* fix broken link
* format
* format
* format
* format
* review comments
* remove GCE
* fix port number
* frank review comments
* move location
* fix check
* move
* move location
* fix doc pointer
* fix broken link
* fix lint
* fix lint
* Document how and why to use distroless variant
Co-authored-by: Philipp Stehle <philipp.stehle@sap.com>
* Fix linting issues
Co-authored-by: Philipp Stehle <philipp.stehle@sap.com>
Co-authored-by: Ulrich Kramer <u.kramer@sap.com>
* Clearify why distroless tag is available for non-distroless images
Co-authored-by: Philipp Stehle <philipp.stehle@sap.com>
Co-authored-by: Ulrich Kramer <u.kramer@sap.com>
* Incorporate feedback.
Co-authored-by: Ralf Pannemans <ralf.pannemans@sap.com>
* istio api evolution blog post
* changed list elements to use dashes
* whitespace fixes for presubmit
* fixes for whitespace, spelling, and relative links
* reformatted list of k8s objects to inline, using backticks
* removed unnecessary terms
* mTLS -> mutual TLS
This feature adds the capability to compare changes to the configuration options
in the helm values.yaml files between the current and previous release. This was
included in the 1.1 release but did not get merged. Here is the link to the
original PR: https://github.com/istio/istio.io/pull/3420Fixes: #4384
* remove federation from the keywords of "multiple control plane" pattern
* rename Multiple Control Planes -> Dedicated Control Planes
* remove "single control plane" from the Shared control plane configurations
* add "topology" to "shared control plane" sections
* rewrite the description of shared control plane topology
remove "single" control plane
* two cluster mesh -> two-cluster mesh
* rewrite the explanation of the shared control plane single network topology
remote "the single control plane"
* Revert "rewrite the explanation of the shared control plane single network topology"
This reverts commit fb2d9f6b1a.
* Revert "rewrite the description of shared control plane topology"
This reverts commit 1170fe34ae.
* Revert "remove "single control plane" from the Shared control plane configurations"
This reverts commit 11e1caf1fa.
* fix announcing 1.1 blog post
* fix the multicluster version routing blog post
* fix remaining links to multicluster topologies
* put back removed "topologies" from the announcing-1.1 blog post
* fix a link in the multicluster version routing blog post
* Cross-namespace config
* clarifications
* Fix spelling
* tweaks
* improvements
* more details
* Reference the problem from egress gateway task
* tweak
* review comments and remove broken link
* broken link
* a skeleton version
* add full content
* fix internal links to previous egress examples
* make the structure flat
decrease the indentation level of two subsections
* replace subtitle and description with content relevant for part 3
* add referencing the third part from the first and the second parts
* secure egress traffic control -> secure control of egress traffic
* Update content/blog/2019/egress-traffic-control-in-istio-part-3/index.md
Co-Authored-By: Rigs Caballero <grca@google.com>
* remove "new from
Co-Authored-By: Rigs Caballero <grca@google.com>
* such as Kubernetes Network Policies -> such as using Kubernetes Network Policies
Co-Authored-By: Rigs Caballero <grca@google.com>
* proxies/firewalls -> proxies and firewalls
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence of reminding the requirements
Co-Authored-By: Rigs Caballero <grca@google.com>
* support for -> support of
Co-Authored-By: Rigs Caballero <grca@google.com>
* remove by Istio, support for -> support of
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence about the two alternative solutions
Co-Authored-By: Rigs Caballero <grca@google.com>
* cannot satisfy -> the requirements they can't satisfy
Co-Authored-By: Rigs Caballero <grca@google.com>
* remove the dot from subtitle
since Hugo complains about it
* add mentioning the alternative solutions before presenting them
* The most natural solution -> Kubernetes provides a native solution
* rewrite the sentence about cluster operators and network policies
Co-Authored-By: Rigs Caballero <grca@google.com>
* can be identified -> cluster operators can identify
Co-Authored-By: Rigs Caballero <grca@google.com>
* stress the relation between IP ranges and not being DNS-aware
* the requirement is satisfied -> network policies satisfy the requirement
* rewrite the sentence about K8s network policies and requirements 3 and 4
* remove passive voice in the sentence about the fifth requirement and k8s network policies
Co-Authored-By: Rigs Caballero <grca@google.com>
* and to interfere -> and interfere, the node - the said node
Co-Authored-By: Rigs Caballero <grca@google.com>
* Add "lastly", remove passive voice from the k8s network policies and the sixth requirement
Co-Authored-By: Rigs Caballero <grca@google.com>
* add "in summary" to the last sentence about k8s network policies
Co-Authored-By: Rigs Caballero <grca@google.com>
* another approach -> the second alternative, add the to Kubernetes network policies, add "Using ... lets you"
Co-Authored-By: Rigs Caballero <grca@google.com>
* are configured -> configure
Co-Authored-By: Rigs Caballero <grca@google.com>
* remove passive voice, use operators as subjects
Co-Authored-By: Rigs Caballero <grca@google.com>
* not known to proxies -> proxies do not know about them
Co-Authored-By: Rigs Caballero <grca@google.com>
* they -> egress proxies, source specified by -> Kubernetes artifacts specifies the source
Co-Authored-By: Rigs Caballero <grca@google.com>
* add "in summary" to the last sentence about egress proxies
Co-Authored-By: Rigs Caballero <grca@google.com>
* but not -> but can't satisfy
Co-Authored-By: Rigs Caballero <grca@google.com>
* connect two sentences about not specifying the requirements and why they do not specify the requirements
Co-Authored-By: Rigs Caballero <grca@google.com>
* fix the subtitle and description that were mistakenly reverted
* use lower case for network policies
* remove redundant white space
* remove a redundant empty line
* remove a leftover and fix lines arrangement
* hop with two proxies, the egress gateway -> hop with one or two proxies in the egress gateway
* pay attention to performance overhead and measure it
* remove "because they are DNS-aware" since they are by definiton DNS-aware
* requirements 3 and 4 -> the third and the fourth requirements
* proxy/firewall -> proxy or firewall
* have to -> must
* for authentication only without encrypting -> for authentication only, without encrypting
* remove comma in "in the egress gateway, should not have a large impact"
* remove "so I hope the overhead of egress traffic control in Istio will be reduced in the future"
since it is implied for the fact that we are working to reduce it
* use colon instead of "namely"
Co-Authored-By: Rigs Caballero <grca@google.com>
* split a long sentence
Co-Authored-By: Rigs Caballero <grca@google.com>
* do not -> don't, remove "to" after "or"
Co-Authored-By: Rigs Caballero <grca@google.com>
* tamper-proof -> resilient to tampering
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence about Istio's additional features
Co-Authored-By: Rigs Caballero <grca@google.com>
* it allows defining -> define
Co-Authored-By: Rigs Caballero <grca@google.com>
* Is intergrated out of the box -> Out-of-the-box integration
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence about writing the adapters to external monitoring once
Co-Authored-By: Rigs Caballero <grca@google.com>
* You can apply -> Use
Co-Authored-By: Rigs Caballero <grca@google.com>
* We call a system that has the advantages above -> We refer to a system with the advantages above as
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the "Let me summarize" sentence
Co-Authored-By: Rigs Caballero <grca@google.com>
* put Istio the first in the features table
* rewrite the sentence about the price of egress control
Co-Authored-By: Rigs Caballero <grca@google.com>
* increase of CPU usage by the cluster pods -> increased CPU usage by the cluster's pods
Co-Authored-By: Rigs Caballero <grca@google.com>
* Rewrite the sentence about traffic passing through two proxies
Co-Authored-By: Rigs Caballero <grca@google.com>
* complete the previous commit
Co-Authored-By: Rigs Caballero <grca@google.com>
* In the case of -> if you use
Co-Authored-By: Rigs Caballero <grca@google.com>
* making the count of proxies three -> adding a third proxy.
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence about the traffic between proxies on the local host
Co-Authored-By: Rigs Caballero <grca@google.com>
* different configurations of Istio -> different Istio configurations set to control
Co-Authored-By: Rigs Caballero <grca@google.com>
* to measure carefully -> to carefully measure, for your applications -> with your applications
Co-Authored-By: Rigs Caballero <grca@google.com>
* measure and decide -> measure before you decide
Co-Authored-By: Rigs Caballero <grca@google.com>
* , and also compare with -> and compare
Co-Authored-By: Rigs Caballero <grca@google.com>
* provide our take -> share my thoughts
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence about high latency of access to external services, part 1
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence about high latency of access to external services, part 2
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence about microservice architecture
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence about the additional hop
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence "we are working to reduce performance"
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence about possible optimizations, part 1
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence about possible optimizations, part 2
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence about possible optimizations, part 3
Co-Authored-By: Rigs Caballero <grca@google.com>
* I also hope -> hopefully, can serve as -> is, for controlling -> to control
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence about the first Istio use case
Co-Authored-By: Rigs Caballero <grca@google.com>
* remove leftover from the previous commit
Co-Authored-By: Rigs Caballero <grca@google.com>
* remove the last sentence about the performance overhead
* add links to Istio features
* with Istio sidecar injected -> in the mesh
* then apply the adapters -> apply them
* add a comma
* rewrite the sentence about Istio being already beneficial
Co-Authored-By: Rigs Caballero <grca@google.com>
* replace * bullets by -
* remove double and
* The network policies -> Network policies
* remove "adding a third proxy"
* split a long line
* add a sentence about "Istio is the only solution"
* encourage users to install Istio, check Istio tasks and use discuss.istio.io
* fix a typo
* rewrite Istio is the only solution as bullets
Co-Authored-By: Rigs Caballero <grca@google.com>
* compete the previous commit
Co-Authored-By: Rigs Caballero <grca@google.com>
* rewrite the sentence "if you had not a chance to work with Istio yet"
Co-Authored-By: Rigs Caballero <grca@google.com>
* chec egress traffic control -> check egress traffic control task
Co-Authored-By: Rigs Caballero <grca@google.com>
* Tell us what you think -> we also want to hear from you
Co-Authored-By: Rigs Caballero <grca@google.com>
* specify a traffic source -> specify the traffic source
* egress control task -> egress control tasks
* remove the final dot from the third bullet
* use a relative url for istio.io
* change the published date to today
* Add distroless as a core feature for 1.3.
Distroless is ready for Alpha. The images are built, pushed, and have been
running in CI for some time including presubmit testing.
* Add distroless to spelling file
Adam Miller
Martin Taillefer
navinger
Frank Budinsky
Steven Dake
Martin Taillefer
Joshua Blatt
Iris
Ulrich Kramer
Sandeep Parikh
Istio Automation
Varga Zsolt
Francois Pesce
Mariam John
Võ Anh Duy
wusphinx
mergify[bot]
Rigs Caballero
imgbot[bot]
Vadim Eisenberg
santinoncs
Katharine Berry
Eric Van Norman