* 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
* Document preference to using an NLB with gateways
Gateways multicluster runs best with NLBs. Share this arcane bit of
information in the documentation.
* Address linting
* Address reviewer comments.
* Address reviewer comments
* Fix the flow and language of the Getting started doc.
Signed-off-by: rcaballeromx <grca@google.com>
* Add cross-reference on the k8s install guide.
Signed-off-by: rcaballeromx <grca@google.com>
* Rework concluding paragraph to clarify timeline.
Signed-off-by: rcaballeromx <grca@google.com>
* Move cross-reference to landing page.
Signed-off-by: rcaballeromx <grca@google.com>
* Refine the multicluster gateways installation documentation
Change all occurances of we to you.
Use the kubernetes version macro instead of hard-coding.
Refinements to the wording in various places.
Improvements to the workflow, so it works 100% of the time instead of most of the time.
Add the a warning flag related to the samples certs.
Add more information about stubbing a domain for cloud provides that have specific unique procedures.
* refinements
* Fix shortcode error
* Fix linting problems
* Apply review comments.
* Fixes Issue #4142
Document the helm whitespace command line problem. We should consider
producing a list of known Helm problems as they relate to Istio - post
1.2 (with a quick backport to all of the branches including deprecated
Istio versions). It will take some time to generate this list, but we
could replace this 1 warning with all of the various Helm issues we
see in production usage along with the upstream tracking bug.
* Improve readability of this change
* compress the text of this issue
Moves the content found in examples/advanced-gateways/ to
tasks/traffic-management/edge-traffic and
the content found in examples/multicluster/ to tasks/multicluster/
Fixes all broken links caused by the move and adds aliases to the moved pages.
The changes are applied to both, English and Chinese, websites.
Signed-off-by: rcaballeromx <grca@google.com>
- Added a test suite to test out the different compositions of
site features.
- Substantially improve the composability of site features
(callouts, tabs, text blocks, boilerplates, lists). You can
now more confidentally mix & match these in any combination
and have a pretty good chance it'll render correctly.
* Rework IBM Cloud public instructions to call common instructions
* Review comment - further simplification
* Update content/docs/setup/kubernetes/install/platform/ibm/index.md
* Remomve AWS Kops as a docummented option
This doesn't mean you can't get AWS Kops to deploy Istio, just that
nobody cares to maintain the documentation. If in the future someone
wishes to maintain the documentation, we can consider adding this page
back in. I would suggest however a page on any EKS specific requirements
needed for Istio as this will be the more likely path folks take to run
Istio.
* Remove link to AWS
* Add warning callout to securing Tiller installs
There are 3 other `helm init` redundant sections. I am likely
to just C&P this warning to those sections. As a team, we need
to seriously rethink how to document these options longer term.
* Add C&P warning to all `helm init` sections
Clearly the C&P is not ideal. What would be better is to consolidate
all install instructions in these various documents into our main helm
install page as the helm init instructions are not doing anything special.
* Fix linter errors
* Boilerplate the helm security warning
* Workaround <{{ not parsable by hugo
use <pre></pre> to get hugo moving on the boilerplate. This needs
to be resolved at some point, but I'm hopeful this workaround will
work for now.
* Better workaround to problem of parsing a boiler
* Address reviewer comments
- We haven't been checking external links for months now due to a script error
when someone added an option that didn't work as expected. I'm fixing a bunch
of resulting broken links. I can't turn on the link checker yet since there are
some bad links in reference docs which I have to address first.
- Add a bunch of links to yaml files in our code examples using the @@ syntax.
* Update docs regarding when to use flexible mTLS
mTLS is now supported with stateful sets and headless services.
See https://github.com/istio/istio/issues/1277
* Fix formatting
- Move requirements up to be the first thing people see. This matches
the order presented in the landing page.
- Shuffle the order in the sidebar a bit to correspond to the order
the material is presented in the landing page.
- Clean up some of the wording on the k8s landing page.
- Shorten the platform names used in the sidebar nav so they fit better.
This matches the names used in the Platform Setup section.
Mariam John
mergify[bot]
Vadim Eisenberg
Eric Van Norman
Steven Dake
Frank Budinsky
Dan Ciruli
Martin Ostrowski
Romain Lenglet
Rigs Caballero
imgbot[bot]
Rachael Graham
Steven Dake
Morven Cao
Martin Taillefer
Lin Sun
Gregory Hanson
Brian Avery
Anmol Sethi
lei-tang
Shriram Rajagopalan