Hi Greg, I have a few suggestions inline below. On Tuesday, August 8, 2017 at 6:58:29 AM UTC-7, Greg Baltzer wrote: > Here are a few things that we have tried so far in our attempt to use windows > containers with spinnaker on GCP. > > > 1) We created a docker image on windows of a simple asp.net application then > pushed that image up to our container registry on GCP. The image was then > grabbed by spinnaker, but every step after that failed. Here is the error > output we got via Spinnaker: > > > > > Failed to pull image "gcr.io/btinterns-168014/hello-node2:v1": [rpc error: > code = 2 desc = unknown blob, rpc error: code = 2 desc = unknown blob] > > Error syncing pod, skipping: failed to "StartContainer" for > "btinterns-168014-hello-node2" with ErrImagePull: "[rpc error: code = 2 desc > = unknown blob, rpc error: code = 2 desc = unknown blob]" > > Error syncing pod, skipping: failed to "StartContainer" for > "btinterns-168014-hello-node2" with ImagePullBackOff: "Back-off pulling image > \"gcr.io/btinterns-168014/hello-node2:v1\"" > > > > > 2) Since then, we started following this tutorial and were able to seemingly > setup the two windows server nodes outlined in the tutorial.
That tutorial may not reflect the most recent status of Kubernetes on Windows. Please take a look at the guide at https://github.com/apprenda/kubernetes-ovn-heterogeneous-cluster, which several folks from the sig-windows Kubernetes community (https://github.com/kubernetes/community/tree/master/sig-windows) have been working on. That guide currently uses OVN/OVS to set up an overlay network for the Windows containers due to networking limitations in Windows Server 2016. You can join the #sig-windows channel on Slack to see status updates and ask questions. > Problems arose when we started to setup the linux node where the Kubernetes > control plane is supposed to reside. While we were working on this, we > discovered the checkbox to enable Kubernetes-alpha features when creating a > new container cluster on Google Container Engine. We imagine that the reason > we were getting errors while following the tutorial listed above was because > that Kubernetes-alpha checkbox was not checked. It looks like you're trying to connect Windows nodes (VMs in Compute Engine?) to a Container Engine cluster? That configuration is unlikely to work at this time due to networking incompatibilities. If you don't want to go to the trouble of setting up your own cluster entirely in Compute Engine using OVN (the guide I linked to above), checking out the steps for setting up the Windows node at https://github.com/apprenda/kubernetes-ovn-heterogeneous-cluster/tree/master/worker#windows might get you a bit further along. > > One concern that we have is whether or not we will be able to hook the > container cluster that we create (which has 1 linux node and 2 windows nodes) > up with spinnaker. Should we continue deploying spinnaker via the GCP > Launcher, or would we be better off & gain more functionality if we deployed > it ourselves in a new VM on the compute engine? You'll get further if you run your entire heterogeneous (Windows + Linux) Kubernetes cluster in Compute Engine (no Container Engine) using the guide I mentioned above. That's the state-of-the-art for Kubernetes on Windows at this time, but Windows support is not even "beta" in the current Kubernetes release. > > > We are curious to see if anyone has any experience running a asp.net > container on google cloud platform. There are a few known issues with running docker containers on Windows Server 2016 VMs in Compute Engine. Please read through https://cloud.google.com/compute/docs/containers/#docker_on_windows for suggested steps to set up docker on your Windows nodes and to work around the known issues. Thanks, Peter -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
