Windows support

[banzo]

Check and update the (Minikube) installation instructions for windows support:

• deploy.sh adaptations (seems there is a Windows vs Linux file encoding issue)
• can/should the WSL be used? If yes, how?

[banzo]

Check and update the (Minikube) installation instructions for windows support:

./deploy.sh needs to be deploy.sh

• deploy.sh adaptations (seems there is a Windows vs Linux file encoding issue)

• Make the script less strict regarding errors when running on Windows:

  if [ "$OSTYPE" != "msys" ]; then
    set -o errexit
  fi
  

• make sure deploy.sh has the right line break format (DOS vs UNIX), see https://sourceforge.net/projects/dos2unix/

[banzo]

The following feature branch will incorporate those adaptations: https://github.com/cetic/fadi/tree/feature/installguide

[banzo]

There is a new problem introduced with Kubernetes 1.16: https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/

A workaround for installing Tiller can be found here: helm/helm#6374 (corresponding PR: helm/helm#6462), this should be fixed in next helm release (2.15) but the windows client is not yet available for this release, would need to build it.

But the subcharts of helm-fadi apparently need to be patched too (deploy.sh fails in the next steps after Tiller install).

Now, what we can do

• downgrade to K8S to version 1.15.*
• build a windows Helm client for Helm 2.15
• try Helm 3 --> tried before the deprecated API root cause has been identified, does not fix anything
• patch all the charts: for ours it should be relatively straightforward, for the external charts (to be identified) it will be a bit more messy

[alexnuttinck]

@banzo Is this problem still occur? Maybe we could create a new issue for your last comment? I don't think this problemn is only related to Windows?

[banzo]

@Empyrion42 feel free to leave some feedback here