Vault Use Passthrough IngressGateway in BigBang

Similar to Keycloak, create the following for the Vault package to configure and document using an Istio Passthrough IngressGateway when deployed via BigBang:

• BigBang chart values have ingress.gateway along with ingress.cert & ingress.key
• BigBang tests/test-values.yaml vault values pointed to utilize the passthrough Ingressgateway complete with certs
• Create an example values file for Vault passthrough iGW configuration at docs/example_configs/vault-dev-values.yaml

added to epic &99 (closed)

changed the description

changed the description

added kindenhancement priority5 teamXForce vault labels

set weight to 2

changed iteration to Big Bang Iterations May 3, 2022 - May 16, 2022

added statusblocked label

created branch 1158-vault-use-passthrough-ingressgateway to address this issue

mentioned in merge request !1629 (merged)

added statusdoing label and removed statusblocked label

When I enable Vault TLS the autoInit job stops working because the vault api changes to vault.bigbang.dev. Have to figure out what to do.

assigned to @kevin.wilder

marked the checklist item BigBang tests/test-values.yaml vault values pointed to utilize the passthrough Ingressgateway complete with certs as completed

marked the checklist item Create an example values file for Vault passthrough iGW configuration at docs/example_configs/vault-dev-values.yaml as completed

mentioned in issue #1186 (closed)

changed iteration to Big Bang Iterations May 17, 2022 - May 30, 2022

changed milestone to %1.35.0

added statusreview label and removed statusdoing label