We want to backup certmanager CRDs in the case of Tiller usage.
Also clarify thee filename slightly to indicate it is CRD data and
related to Istio 1.0.
Fixes: #3753
* Organize control plane update page
* small wording
* typo
* Update content/docs/setup/kubernetes/upgrade/index.md
Co-Authored-By: linsun <linsun@us.ibm.com>
* Update content/docs/setup/kubernetes/upgrade/index.md
Co-Authored-By: linsun <linsun@us.ibm.com>
* address martin comment and hope to fix circleci
* more update
* fix circle lint
* 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 port usage
* Review comments
* Monitoring port is hardcoded and not overridable
* Restructure Istio port table
* Code review comments: Shorten table, description
* 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.
* First round of mesh expansion doc updates.
* Bash syntax works now, and remove the headline to be consistent.
* fix the spelling.
* SERVICE_NAMESPACE and cleanup.
* Use more SERVICE_NAMESPACE in the cmd.
* Another round of fixing the doc by following exactly what it says.
* add gcloud ssh
* VM instance ip as a step.
* address comments. ns explaining.
* comments fixing and echo to tee.
* update meshexpansion.enabled
* applied my zone, project in scp.
* add istio-sys ns crtn.
* Fix frank suggestion.
* gce instance ip
* Verfied manually: use helm template for CRD.
* Verfied manually: use helm template for CRD.
* for example comma.
* Add tips to disclaim GCE.
* Update content/docs/setup/kubernetes/mesh-expansion/index.md
Co-Authored-By: incfly <jianfeih@google.com>
* Update content/docs/setup/kubernetes/mesh-expansion/index.md
Co-Authored-By: incfly <jianfeih@google.com>
* address taos comments.
* fix the link for cert life config.
* Change to require helm in prerequisite.
* fix lint
* congrats section and cleanup vm model section.
* Apply 23 suggestions to code review from github.
Co-Authored-By: incfly <jianfeih@google.com>
* remove tip section.
* fix trailing spaces lint.
* fix lint.
* remove duplicate sentence.
* remove duplicate the the.
so that users don't need to download istio archive.
confirmed these files exist for me:
```
~/istio-fetch/istio ⌚ 13:55:51
$ ls
Chart.yaml templates values-istio-remote.yaml
README.md values-istio-demo-auth.yaml values-istio-sds-auth.yaml
charts values-istio-demo-common.yaml values.yaml
example-values values-istio-demo.yaml
requirements.yaml values-istio-minimal.yaml
```
* Implement consitent term for installation related flows
Replaced "paths", "instructions", and other similar terms
with the term "flow" to ensure readers from different
Geos are not confused by multiple meanings or idiomatic use.
Signed-off-by: Rigs Caballero <grca@google.com>
* Implement consistent term for installation related flows
Replaced "paths", "instructions", and other similar terms
with the term "flow" to ensure readers from different
Geos are not confused by multiple meanings or idiomatic use.
Signed-off-by: Rigs Caballero <grca@google.com>
* Fix typos and lint issue.
Signed-off-by: Rigs Caballero <grca@google.com>