When an instance does not exist yet and needs to be started, its status is not assumed to be starting anymore. Instead, the statue will be retrieved from the provider. This changes one thing, it's that you may be able to start and access your services instantly because they'll be instantly seen as ready. With this change, you might want to make sure that your containers have a proper healthcheck used to determine when the application is able to process incoming requests. * refactor: add interface guards * refactor(providers): remove instance.State as a return value from Stop and Start * test(e2e): add healthcheck on nginx container Because now the container check is so fast, we need to add a delay on which the container is considered started and healthy to have a proper waiting page. * fix(tests): using acouvreur/whoami:v1.10.2 instead of containous/whoami:v1.5.0 This image simply retrieve the curl binary from curlimages/curl:8.8.0 to be able to add proper docker healthcheck commands. Once this is merged with traefik/whoami, I'll update back to the original image. See https://github.com/traefik/whoami/issues/33
Install kubectl
sudo install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl
Install helm3
curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash
Start k3s
docker compose up -d sudo chown vscode ./kubeconfig.yaml chmod 600 ./kubeconfig.yaml export KUBECONFIG=./kubeconfig.yaml
kubectl create configmap -n istio-system sablier-wasm-plugin --from-file ../../sablierproxywasm.wasm
Install Istio Helm charts
helm repo add istio https://istio-release.storage.googleapis.com/charts helm repo update helm install istio-base istio/base -n istio-system --wait helm install istiod istio/istiod -n istio-system --wait kubectl label namespace istio-system istio-injection=enabled helm install istio-ingressgateway istio/gateway --values ./istio-gateway-values.yaml -n istio-system --wait
Install Sablier
kubectl apply -f ./manifests/sablier.yml
Build proxywasm
make docker