* Add docs for new istioctl and operator change
* fix lint and address some comments
* address more comments
* add instruction for helm
* address new comments
* fix new comments
* Update content/en/docs/setup/install/standalone-operator/index.md
Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>
* address comments
Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>
* Add example to watch multiple namespaces for istio operator
* Rename istioNamespace to watchedNamespaces
* Add suggestion
Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>
* Remove deprecated flag
* Move paragraph as per suggestion
Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>
* Few more improvements
Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>
Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>
If you are not running as root already, this will fail. The redirect part is not run as root previously
Co-authored-by: John Howard <howardjohn@google.com>
* Add instructions on installing Istio for vms
* Address review comments
workaround netlify
* Fix cert management link
* Remove /var/run/secrets from document
* Address linting problems
rebase for netlify failure
* Address review comments - not quite functional
This change addresses all reviewer comments, but does not address
my personal testing. That is the next commit in this PR:)
* Address reviewier comments
* One small improvement to the make command
* Address reviewer comments.
* Address reviewer comments and lintian problems
* Fix spellING errors.
* few linting errors.
* Self review.
* Add a plugin ca cert reference to individual CSOs.
force push to work around netlify issue
* Move from setup/install/multicluster
* Rebase to pick up cert-management directory change
netlify rebase
* Address @rshriram comment by adding a banner
force rebase to force netlify to build
* Address reviewer comments.
* Address reviewer comments
* Address reviewer comments
rebase for netlify
* Address reviewer comments
* Address @frankb 's comments.
force push for netlify
* Address reviewer comments.
* Prefix WORK_DIR with $HOME instead of $WORK_DIR. :)
netliffy rebase
* Address most of @smawson's comments
* Fix linting error
* Address reviewer comments.
rebase for netlify
* Fix linting errors
* Add tip explaining that only one VM can be registered
* Fix linting errors.
* Resolve reviewer comments.
* Uninstall: add note about removal of istio-system ns
Fixes: #23189.
* Clarify the reason of not removing it
* Apply suggestions from code review
Co-Authored-By: Frank Budinsky <frankb@ca.ibm.com>
Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>
* Retire helm documentation as we use a protobuf
The new rendered source of truth is:
https://preliminary.istio.io/docs/reference/config/istio.operator.v1alpha1/
This is rendered from the API repo protobuf which (may) need description fields
set. That protobuf is here:
https://github.com/istio/api/blob/master/operator/v1alpha1/operator.proto
* Follow the flowchart
The flowchart is not quite right and could use some improvement.
* Update content/en/blog/2019/performance-best-practices/index.md
Co-Authored-By: Frank Budinsky <frankb@ca.ibm.com>
Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>
* update multicluster shared control plane docs
* Merged single and multiple network instructions. They are nearly
identically except for specifying the mesh network configuration.
* Removed use of pod IPs for cross-cluster control plane. Added three
options that are more appropriate for production use.
* use `istioctl x create-remote-secret` instead of copy/paste bash
* Updated the master and remote cluster configuration examples to be
declartive instead of imperative. Users can copy/paste the examples,
edit, commit to scm, and apply to the clusters.
* Update content/en/docs/setup/install/multicluster/shared/index.md
Co-Authored-By: Frank Budinsky <frankb@ca.ibm.com>
* Update content/en/docs/setup/install/multicluster/shared/index.md
Co-Authored-By: Frank Budinsky <frankb@ca.ibm.com>
* Update content/en/docs/setup/install/multicluster/shared/index.md
Co-Authored-By: Frank Budinsky <frankb@ca.ibm.com>
* updates
* Update content/en/docs/setup/install/multicluster/shared/index.md
Co-Authored-By: Frank Budinsky <frankb@ca.ibm.com>
* Update content/en/docs/setup/install/multicluster/shared/index.md
Co-Authored-By: Frank Budinsky <frankb@ca.ibm.com>
* lint errors
* lint
* Update content/en/docs/setup/install/multicluster/shared/index.md
Co-Authored-By: Lin Sun <linsun@us.ibm.com>
* update networks and add selfSigned
* Apply suggestions from code review
Co-Authored-By: Lin Sun <linsun@us.ibm.com>
* Update content/en/docs/setup/install/multicluster/shared/index.md
Co-Authored-By: Lin Sun <linsun@us.ibm.com>
* fix config and remove option 3
* fix formatting and grammer
* move additional considerations after the sample services
Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>
Co-authored-by: Lin Sun <linsun@us.ibm.com>
* More base release 1.6 stuff
* Add 1.6.x to spelling
* Fix some broken links with sidecar/tls-check being removed
* Fix links pointing to install/kubernetes/helm/...
* Incorporate #6783 - Fix bug requiring placeholder release notes
* Restore some links to archive
* Fix one remainging link to archive
* Someone still pointing to current release upgrade notes. Remove.
* update operator ref doc
* fix broken link
* Update url to archive link
Co-Authored-By: Frank Budinsky <frankb@ca.ibm.com>
Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>
found during community testing:
- The version of API was incorrect.
- The first step of the doc did not have the namespace creation (it was
in a 2nd step in the English version)
These fix problems encountered when switching to the new Hugo which has
a completely different markdown engine. I went through diffs of the generated
HTML and made required adjustments.
- We don't need cookies for istio.io, the few settings we do have should be
managed with browser-local storage instead. This is a better privacy posture,
and avoids sending needless data to the server for every request.
* Added the Best Practices section with general principles.
This is the beginning of the new Best Practices section.
Our goal is to provide a section for all the best practices and recommendations
for Istio deployments. The best practices are based on the identified and
recommended deployment models.
Signed-off-by: rcaballeromx <grca@google.com>
* Change headings for clarity.
Adds clarity to some passages based on feedback.
Removes a list of recommendations that was causing some confusion.
Adds a glossary entry for failure domains and how they relate to a
platform's availability zones.
Signed-off-by: rcaballeromx <grca@google.com>
* Move Best Practices to Ops Guide
Signed-off-by: rcaballeromx <grca@google.com>
* Moved Deployment Best Practices to a new "Prepare Your Deployment" section.
Moved all deployment preparation content into a new section under "Setup".
For now the content includes the following sections:
- Deployment models
- Deployment best practices
- Pod requirements
Merged the two existing pages containing pod requirements into one single page.
Signed-off-by: rcaballeromx <grca@google.com>
* Replace example with better guidance around namespace tenancy.
Signed-off-by: Rigs Caballero <grca@google.com>
* Add links and language pointing to the Prepare section
Signed-off-by: Rigs Caballero <grca@google.com>
* Fix minor typos and broken links.
Signed-off-by: Rigs Caballero <grca@google.com>
* Move from Setup to Operations
Signed-off-by: Rigs Caballero <grca@google.com>
* Fix broken links
Signed-off-by: Rigs Caballero <grca@google.com>
* Fix rebasing issues.
Signed-off-by: Rigs Caballero <grca@google.com>
* Fix multicluster install link.
Signed-off-by: Rigs Caballero <grca@google.com>
* Update multicluster shared-vpn doc
Update docs for the multicluster installation for Shared control plane (single-network) to make it work with `istioctl manifest`.
* Update index.md
* Apply suggestions from code review
Co-Authored-By: Frank Budinsky <frankb@ca.ibm.com>
- Improved look of the call to action buttons
- Removed redundant attributions on all news items, those were
leftovers from when the relesse notes were in the blog section.
- Used consistent subtitles and descriptions for all news items.