The automatic sidecar injection has its own set of k8s install instructions for webhooks. This overlaps with the general k8s install instructions. We'll also introduce server-side configuration webhooks which need the same prerequisites.
* Update sidecar AWS verification
Add verification without ssh access on master node. Perform check directly with kubectl client.
* Update sidecar injection Docs
Update with @ayj remarks
* Update link
Update link for managing tls in a cluster, add a '/'
- Fix another issue with my arch-nemesis, the Copy button. My last fix for Copy button issues
resulted in screen flickering upon page loading. This is now fixed.
- Pin the size of the gear and magnifying glass icons in the header to avoid flicker as the
fonts for those renders a few ms too late and lead to flickering on page load.
- Cleaned up the site's JavaScript for clarity, and include minimized versions in the
site for improved perf.
The Google Crawl Engine reported a bunch of broken links pointing into istio.io.
This adds redirects so that these links work.
Add a hack such that the gear menu logic that lets you time travel through versions
of the site will insist that if a page existed in a given version, it must also exist
in subsequent versions. This will ensure we always create redirects when we move site
content, and thus avoid breaking links into the site. If a page is moved or removed,
this will lead to rake test errors when checking the content of archive.istio.io.
We now generate the test site into a subdirectory such that we can ensure all
links are correctly using {{home}}, which makes the site work correctly once
archived.
Fixed a bunch of broken cases.
* Istio Ingress Controller -> Istio Ingress
controller is a Kubernetes term, it does not serve here any purpose
* Ingress Resources -> Ingress Resource
fixed cardinality
* clarified Istio Ingress vs. Kubernetes Resource
* Istio ingress -> Istio Ingress
* Ingress Resource -> Ingress specification
* it allows defining -> it allows one to define
* istio-ingress pod -> istio-ingress service
* rephrased the sentence about applying Istio features
* Istio Ingress -> The Istio Ingress
* The following are the known limitations -> The following are known limitations
* into-the-cluster traffic -> traffic entering the cluster
* second time: into-the-cluster traffic -> traffic entering the cluster
* To remind -> a quick reminder
* would do -> good enough, make "Note" bold
* a single rule -> just a single rule
* It is -> This is
* see that -> verify that
* articles in English language -> the articles available on Wikipedia in the English language
* remove redundant verbs "will"
* Any MySQL instance would do -> You can use any MySQL instance
* Reversed sentence: As a MySQL client to feed the ratings data, I use mysqlsh MySQL Shell.
* Then I -> I then
* It means -> This means
* reversed the order of "for Bookinfo application I create a special user"
* extract the sentence about the SELECT privilege
* I do not -> I don't
* If I would use mysql, I would remove -> If I'm using use mysql, I'll remove
* Istio Bookinfo sample application -> the Istio Bookinfo sample application
* per each review -> for each review
* make original and application lower case in "The original Bookinfo application"
* added a comma before "and password"
* No need to mention -> I also assume everyone realizes
* removed a comma after "I route all the traffic destined to the _reviews_ service"
* Bookinfo Application -> Bookinfo application
* rephrase the sentence about the error message about ratings service
* added a comma between "the details and the reviews", before "and"
* put "let's call it `egress-rule-mysql.yaml`" into parenthesis instead of commas
* make "Egress Rules" lower case
* the both -> both
* rephrased the sentence about the visual cue
* for example database specific protocols -> such as database-specific protocols like
* CLient -> Client (erroneous upper-case of the second letter)
* each block -> with each block
* rephrased the sentence about multiple CIDR blocks
* a an -> an
* service, however -> service; however
* has to -> must
* remove redundant comma after "the machine which MySQL runs on"
* rephrased "Especially, when this expectation cannot be changed by the deployment configuration of the consuming applications."
* added a comma after "in my next blog posts"
* added a comma after "in this blog post"