hop of those help? It's not really an answer, but is a bit of a work round. It looks like the 64 bit version does not work in windows 8.1 or in VS2012 Express or the combination of both even though it is the 64 bit version of the OS. If I build the solution with a platform target of x86, it all works fine.
Does that help You need to pass the special Wicket-Ajax request parameters. See the ones sent by Wicket Ajax behaviour for their exact names. AFAIR they are: Wicket-Ajax=true and Wicket-Base-Url=something. See wicket-ajax-jquery.js to see how to create the value for the second.
it should still fix some issue Simply speaking the process of running pod is the following: User makes API request to create pod in namespace. API server validates the request making sure that user has necessary authorization to create pod in given namespace and that request conforms to PodSpec. If request is valid API server creates API object of kind "Pod" in its Etcd database. Kube-scheduler watches Pods and sees that there is new Pod object. It then evaluates Pod's resources, affinity rules, nodeSelectors, tolerations and so on and finally makes a decision on which node the pod should run. If there are no nodes available due to lack of resources or other constraints - Pod remains in state Pending. Kube-scheduler periodically retries scheduling decisions for Pending pods. After Pod is scheduled to node kube-scheduler passes the job to kubelet on selected node. Kubelet is then responsible for actually starting the pod.