* automated test - insecure remote access to telemetry addons
* Change profile to demo and add snippets to clean up DestinationRule (besides Gateway and VirtualService)
* automated doc test = secure remote access to telemetry addons through gateway
* Automated test for secure access of common telemetry addons and factor out common snippets to test_utils.sh
* moved test_utils to tests/util/addons.sh so that it can be reused across tests
* refactor addons with a more flexible deploy/undeploy function and fix naming of functions to access addons
* fix cleanup after tests
* fix sourcing
* remove verification for istio config deployment
* don't assume the existence of load-balancer in CI environment, but use _set_ingress_environment_variables instead of snippet in the documentation page
* add verification steps back
* fix output snippets and add verifications
* Use standard ports for telemetry exposure
Blocker for https://github.com/istio/istio/issues/22911
* Full update and include HTTPS
* Fix link
* Remove from ports table
* Apply suggestions from code review
Co-Authored-By: Rachael Graham <rachael.graham@ibm.com>
Co-authored-by: Rachael Graham <rachael.graham@ibm.com>
* Refactor Secure Ingress tasks
Ingress SDS is now the default and recommended. This removes the file
mount task, which is no longer recommended and will avoid confusion, and
cleans up the task a bit. I also documented the new supported secret
formats.
* use archive