* Upgrade release notes
8 months of work. Lots of changes. Very difficult to distill into
a short set of release notes, but here is my take :)
* Fix broken link
* Address reviewer comments
* Clarify language regarding the sidecar webhook.
Signed-off-by: rcaballeromx <grca@google.com>
* Clarify the injection process further.
Signed-off-by: rcaballeromx <grca@google.com>
* Remove blank lines around short codes.
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
- Add a test suite for various compositions of site features.
- Substantially improve composition of various site features to eliminate bad
interactions. It's not perfect yet, but it's much better. The one thing still
broken is "a text block inside a warning in a list in a tab". There's still
something funny going on there, but I have some ideas for later.
- Added a new linter check to detect misuse of https://preliminary.istio.io in docs,
and fixed one offending instance.
* Add doc on policy check enablement and clean-up P&T release notes
* Add in-process adapter model deprecation notice
* Add deprecation feature status for in-proc
* Fix doc link
* Add port usage
* Review comments
* Monitoring port is hardcoded and not overridable
* Restructure Istio port table
* Code review comments: Shorten table, description
- Added call-to-action buttons in the 1.1 announcements. We can use the same
buttons in future release announcements.
- Fixed broken large warning icon on the 404 error page.
- Fix oerder of blog posts in the side bar.
- Add support to not expand @@ notations in text blocks and use
it for a text blocks that's currently triggering a build failure
- Fixed broken rendering of some text blocks when syntax coloring
is turned off via the menu.
* 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.