Documentation on how to run the Istio-proxy as a container on VM's instead of the istio-proxy runtime(rpm/deb)

[KristiaanHoogendoorn]

Description

Some documentation on how someone could run the Istio proxy as a container on their preferred VM platform.

• A user can iterate on the existing VM documentation (and is required to understand it).
• The user is responsible for automation around it.

Disclaimer, sorry for possible bad spelling but I'm dyslectic and probably have missed some/ created some weird sentences.

Overall feedback is very welcome.

Reviewers

• Ambient
• Docs
• Installation
• Networking
• Performance and Scalability
• Extensions and Telemetry
• Security
• Test and Release
• User Experience
• Developer Infrastructure
• Localization/Translation

[linux-foundation-easycla]

• ❌ The email address for the commit (9bbf9cd, f0c6fa9) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[istio-policy-bot]

😊 Welcome! This is either your first contribution to the Istio documentation repo, or
it's been a while since you've been here. A few things you should know:

• You can learn about how we write and maintain documentation, our style guidelines,
  and the available web site features by visiting Contributing to the Docs.

• In the next few minutes, an automatic preview of your change will be built with
  a full copy of the istio.io website. You can find this preview by clicking on
  the Details link next to the deploy/netlify entry in the status section of this
  page.

• We care about quality, so we've put in place a number of checks to ensure our documentation
  is top-notch. We do spell checking, sanitize the Markdown, ensure all hyperlinks point to a
  valid location, and more. If your PR doesn't pass one of these checks, you'll see a red X in the
  lint_istio.io entry in the status section. Click on the Details link to get a list of the
  problems with your PR. Fix those problems and push an update; this will automatically re-run the
  tests. Hopefully this time everything will be perfect!

• Once your changes are accepted and merged into the repository, they will initially show up
  on https://preliminary.istio.io. The changes will be published to https://istio.io
  the next time we do a major release (which typically happens every 3 months or so).
  To publish them sooner, add a cherrypick/release-x.xx label, where x.xx is the current
  release of Istio.

Thanks for contributing!

Courtesy of your friendly welcome wagon.

[istio-testing]

Hi @KristiaanHoogendoorn. Thanks for your PR.

I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Arhell]

/ok-to-test

[craigbox]

failing test due to not being sorted properly

[KristiaanHoogendoorn]

should be fixed

[craigbox]

Unless you're writing a test for this page - which would be great if you could - you don't need this set.

[KristiaanHoogendoorn]

Hey Craig thanks for checking. Are there docs available to get me started? I might be able to setup something similar to the VM setup with docker in docker but have to see.

[craigbox]

I have no idea how we would go about testing something involving a VM. Have a look to see if we have any kind of testing for the existing VM docs?