- Add tests for the various text block features.
- Combine text_file and text_dynamic into text_import
- Add support for snippet extraction for text downloaded from a URL
- Add support for formatting output blocks in a different style for
content downloaded from a URL
- Report some errors when unable to fetch content from a URL.
- Fixed a few small bugs along the way.
- 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.
- 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
- 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.
- 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.
- 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.
* Add a tip about prefixing with sudo for TCP sample
This adds a note about using sudo while running the TCP Traffic Shifting
sample on certain platforms.
Signed-off-by: Venil Noronha <veniln@vmware.com>
* Switch from a tip to a warning
This updates the help text to a warning.
Signed-off-by: Venil Noronha <veniln@vmware.com>
* add access log task
* change config map to configuration map to prevent spelling errors
* add an empty line between two boilerplates
seems to be required, otherwise a redundant <p> tag is generated
* make the task's title Getting Envoy's Access Logs
* mind escaping -> be sure to escape
* check the log of sleep, httpbin -> check sleep's, httpbin's log
* change -> customize
* to do it, edit -> by editing
* use a separate gateway for bookinfo in the case of multiple hosts
* set the name parameter to be "istio" instead of "istio-ingressgateway"
Since the original istio-ingressgateway was deployed with the name parameter "istio".
Otherwise, the following error will be received:
The Deployment "istio-ingressgateway" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{"chart":"gateways", "heritage":"Tiller", "istio":"ingressgateway", "release":"istio-ingressgateway", "app":"istio-ingressgateway"}: `selector` does not match template `labels`
The problem is that the "release" label contains the name parameter of helm template,
and if this label will not match in the new and the original deployments of istio-ingressgateway,
kubectl apply will fail.
* add ingress troubleshooting section
* it does not arrive to the Istio -> it does not arrive to the ingress gateway
* fix a link
* remove checking the log since access log will be removed in 1.1
* you have no other Kubernetes Ingress resources -> you have no Kubernetes Ingress resources
* fail with 503 instead of 000 for injected-app
As a bad destination rule is set to disable client side mTLS and receiving side is mTLS enabled. At this point, Running the curl command between sidecar injected Istio services all requests will fail with a 503 error code as the client side is still using plain-text.
Frank Budinsky