contai-nerd

In a distrubuted system, storage isn't simple to manage without a good abstraction, kubernetes offer an object called persistent volume to let pod to reclaim storage for persisting data. In the pod definition you can define your volume type with another object called persistentVolumeClaim where you can define type size and many other things. There are different phase in the persistent storage lifecycle: Provisioning : when an administrator create a Persistent Volume or a cloud resource dynamically request Binding : when a PVC is created  k8s control loop watch if there are Persisten Volume matching the PVC  and bind them together. Use : when the bound volume is mounted in to the pod Releasing : whene the POD is done and an API request is sent to delete the related bound PVC, the volume in this stage remains Reclaim : there are three options related to this state: - Retain:  keep data interact and allow an administrato to handle data from storage - Delete:  te...

If your company provide only windows machine the good way to get it working is: - download the windows release https://github.com/istio/istio/releases/ - setup the linux version with WLS To do the installation follow these steps: enable WLS on your windows 10 machine, follow the instruction here . install kubectl on your WLS distro . copy kubectl config files from c:\Users\<your_user>\.kube\config in your linux home dire under .kube folder, to do that from WLS shell run this command root@NBMBUCCAR:~/.kube# cp /mnt/c/Users/mbuccarello/.kube/config /root/.kube/ copy minikube confgi files from c:\Users\<your_user>\.minikube to the .minikube directory in your home, to do that run this commands from your WLS shell root@NBMBUCCAR:~/.kube# cp /mnt/c/Users/mbuccarello/.minikube/client.* /root/.minikube root@NBMBUCCAR:~/.kube# cp /mnt/c/Users/mbuccarello/.minikube/ca.crt /root/.minikube At the end of this process the situation on your WLS shell directories and...

Istio 1.0 is becoming mature than the other release, now with helm the installation is easy and pretty straightforward as described here . If you are on windows like me I kindly suggest to install windows linux subsystem so you can follow the steps for linux on your window machine. after you download via curl istio just copy from WSL to your prefered location ( in my case c:\kuberentes ) your istio 1.0 folder download helm for windows and from powershell run the init comands described in the option 2 for the istio guide at the end you can verify your deployment via kubectl And now you can play with istio! Now with helm you can enable all the things you need just just with simple flags as described in the documentation: helm install install/kubernetes/helm/istio --name istio --namespace istio-system \   --set ingress.enabled=false \   --set gateways.istio-ingressgateway.enabled=false \   --set gateways.istio-egressgateway.enabled=false \   ...

On official Istio blog 17 august there is a great twitch stream to celebrate Istio 1.0! Thanks to Spencer Krum @nibalizer  IBM Developer Advocate in his effort in sharing knowledge in this stream about the hottest Cloud Native project of this year! Stream start 10 am PST  ( 1PM EST )  and end 5pm EST. If you want to be part of the stream know just reach Spencer as described   here ! Twitch official channel is the IBMCode channel https://www.twitch.tv/ibmcode. This is an unique opportunity to learn more about Istio 1.0 release! ENJOY!!!!!!!!!