```bash
kubectl apply -f ./helloworld-versions.yaml
```

Apply the following route rule to distribute the helloworld traffic 90% to v1, 10% to v2:

```bash
kubectl apply -f ./helloworld-route.yaml
```

Run the previous curl commands again:

```bash
for run in {1..10}; do curl http://$INGRESS_HOST/hello; done
```

```bash
istioctl install -f iop.yaml -y
```

## Setup Loki

Run the following script to install `Loki`:

```bash
kubectl apply -f ../../addons/loki.yaml -n istio-system
```

## Setup otel-collector service

First, create an `otel-collector` backend with a simple configuration.

```bash
kubectl apply -f otel.yaml -n istio-system
```

		source $HOME/.bash_profile

		# Load the kubeadm completion code for bash into the current shell
		source <(kubeadm completion bash)

		# Write bash completion code to a file and source it from .bash_profile
		kubeadm completion bash > ~/.kube/kubeadm_completion.bash.inc
		printf "\n# Kubeadm shell completion\nsource '$HOME/.kube/kubeadm_completion.bash.inc'\n" >> $HOME/.bash_profile
		source $HOME/.bash_profile

To run both versions of the helloworld service, use the following command:

```bash
kubectl apply -f helloworld.yaml
```

Alternatively, you can run just one version at a time by first defining the service:

```bash
kubectl apply -f helloworld.yaml -l service=helloworld
```

and then deploying version v1, v2, or both:

```bash
kubectl apply -f helloworld.yaml -l version=v1

    def "can execute generated Unix start script in Bash"() {
        given:
        succeeds('installDist')

        when:
        runViaUnixStartScript("bash")

        then:
        outputContains('Hello World!')
    }

    @Requires([UnitTestPreconditions.UnixDerivative, PluginTestPreconditions.DashAvailable])
    def "can execute generated Unix start script in Dash"() {
        given:
        succeeds('installDist')

  ```bash
  $ istioctl install -f istio-spire-config.yaml
  ```

1. Create a ClusterSPIFFEID to create a registration entry for all workloads with the `spiffe.io/spire-managed-identity: true` label:

  ```bash
  $ kubectl apply -f clusterspiffeid.yaml
  ```

1. Add the `spiffe.io/spire-managed-identity: true` label to the Ingress-gateway Deployment:

  ```bash

The following steps are automated with the script `create_cluster_gke.sh` located in this directory. To create a cluster with the script, simply run:

```bash
./tests/integration/create_cluster_gke.sh -c ${CLUSTER_NAME}
```

To list the options for the script, you can get help via `-h`:

```bash
./tests/integration/create_cluster_gke.sh -h
```

### Create the cluster

FROM ${BASEIMAGE} as builder

# This image needs bash for running "migrate-if-needed.sh". Instead of a full debian image
# we use just the bash-static and we wrap bash-static into a distroless image instead of
# a full debian image
RUN apt-get update -y \
	&& apt-get -yy -q install --no-install-recommends --no-install-suggests --fix-missing \
		bash-static

RUN cp /bin/bash-static /sh

FROM ${RUNNERIMAGE}
WORKDIR /

#### 2a. Create a regular Kubernetes cluster

Ensure your GCP authentication is current:

```bash
gcloud auth application-default login
gcloud auth login
```

Invoke kube-up.sh with these environment variables:

```bash
# WINDOWS_NODE_OS_DISTRIBUTION: the Windows version you want your nodes to
#   run, e.g. win2019 or win1909.

Run the following script to request `httpbin` from `fortio`.

```bash
kubectl exec -it $(kubectl get po | grep fortio | awk '{print $1}') -- fortio curl httpbin:8000/ip
```

Run the following script to checkout ALS output.

```bash
kubectl logs $(kubectl get po -n observability | grep otel | awk '{print $1}') -n observability
```

## Cleanup

```bash
kubectl delete -f ../otel.yaml -n observability