mitzen

 This is a quite handy in case we needed to copy and paste to dockerfile. # Base image FROM ubuntu:20.04 # Packages required to run the Azure CLI installation RUN apt-get update && apt-get -y install curl # Azure installation command RUN curl -sL https://aka.ms/InstallAzureCLIDeb | bash

Install the required CRDS kubectl kustomize "github.com/kubernetes-sigs/gateway-api/config/crd?ref=v0.6.1" | kubectl apply -f -   To setup Gateway API, use the following command :- istioctl install --set profile = minimal -y Ensure your namespace is injectable  kubectl label namespace default istio-injection = enabled Run your httpbin from samples folder kubectl apply -f samples/httpbin/httpbin.yaml Setup your HttpRoute and Gateway for your host Run the following command to create gateway Run the following command to create httproutes httproute start httproute end Next using curl to hit the page  curl -s -I -HHost:httpbin.example.com "http://localhost/status/200" Let's say we're setting for only a single hostname, then may be best the use the following yaml (removing the host name.  apiVersion : gateway.networking.k8s.io/v1beta1 kind : Gateway metadata :   name : gateway   namespace : istio-system spec :   gatewayClassName : istio   lis...

Istio has quite a number of loggings options which you can turn on. Amon them are admin, client, connection, rbac, dns.  You can change the log option for these component by running the following command. Here we are using a sample httpbin pods and setting rbac logging to debug kubectl exec httpbin-847f64cc8d-b7nnq -c istio-proxy --  curl -X POST localhost:15000/logging?rbac=debug -s Please note: Port 15000 is istio admin port. or your can also use istioctl command to do turn on logging level. In this example, we are setting the logging level for all to debug  istioctl proxy-config log httpbin-f66f49b6f-jhmmz --level debug. These are the type of logging supported. none error warn info debug The effect is immediate. Right after you run the command, the information level changes.

 

  Was trying to login a VM with PUTTY/SOLAR PUTTY but hit with this error.  First, ensure you have your private key saved in a text file. Then fire up putty gen, the click on the "Load" button to load your private key file.  Next, follow the instruction here: https://superuser.com/questions/1647896/putty-key-format-too-new-when-using-ppk-file-for-putty-ssh-key-authentication After that, click "Save private key".  Connecting to your VM  Next, you should be able to connect to your VM by using this key.