I installed kubernates on linux environment in a lan.
i try to add a windows 10 node to a cluster but the documentation refer only to a windows server 2019. Is there a way to add a windows 10 node?
Related
I have a multi node pool cluster setup in Azure Kubernetes service. linux node pool and windows node pool. I also have 2 containers deployed in a single pod on the windows node pool (since the application is built on .net frameowrk ). My containers are up and running however i wanted to know if there is a way to debug these containers while they are running. Tools found online are inclined towards linux node pool or .net core. It is going to take some time to convert code to .net core since we still have legacy WCF stuff.
is there a way or a tool (3rd party or via VS 2019 ) where i can connect to the cluster and debug the containers in the windows node pool. (Azure Dev Spaces also are inclined towards linux node pool unless i taint the windows node pool).
I've the same problem since we're planning to migrate to AKS and have some Windows legacy stuff that we would like to move to AKS Windows nodes, as far as I know Dev Spaces only works with Linux based pods and right now the only option to debug Windows ones is to use the Visual Studio snapshot debugger but we've not yet tried this road in AKS.
Im totally new to Google Cloud. I got free uses for some time from google.
I want to setup a lab. So I want to install Windows 7 on Google Cloud.
Thanks
The image for Windows 7 is not available, you can create a custom image, upload it and then create an instance with that image, but honestly I would not follow this path if you have just started and you want only to run a Windows server.
So, if you don't really need Windows 7 for some reason and you want to run a Windows virtual machine the easiest thing to do is to create an instance using one of the available images:
Windows Server version 1709 Core for Containers (Beta)
Windows Server version 1709 Core
Windows Server 2008 R2
Windows Server 2012 R2 Core
Windows Server 2012 R2
Windows Server 2016 Core
Windows Server 2016
In order to do so go to the Console, enter in Compute Engine, VM instances, click on create instance, at this point from the tab that will be opened select the Windows image that you prefer and set up the machine as you like. Wait some minute and you will be able to connect to it through RDP.
Note that there is a Quickstart guide in order to help you in the process.
I have a Windows 10 machine. Recently I have installed Hyper-V 2016 server on my machine. From then whenever I start my system I only see a blue screen with various commands. I do not see any other thing other than that. Now how can I go back to my normal Windows machine?
See this image for reference:
you had Windows 10 installed on your machine now you have Microsoft Hyper-V Server 2016.
I assume you downloaded an ISO and installed that one. Whereas within Windows 10 you only have to activated a feature called Hyper-V.
Grap your latest Backups and install Windows 10 back onto your machine.
KR
Guenther
We have several systems with windows 7 installed on. Is there any chance to create a cluster with these systems without installing any windows server. I mean we want to use windows 7s as computing nodes in our cluster.
Thank you in advance.
In HPC Pack 2012 you can install them as Workstation nodes if they're running Windows 7 Enterprise, Windows 7 Professional, or Windows 7 Ultimate
From https://technet.microsoft.com/en-us/library/ff601843(v=ws.11).aspx
since yesterday I had my Windows 2012R2 Datacenter server correctly running Hyper-V machines.
After a windows update I'm not able to start any of the VMs and get a message that say Hypervisor not in execution.
If I check from services I don't see the service but from server manager the hyperv role seems to be running.
From windows features list i don't see anymore the Hyper-v (i wanted to uninstall and reinstall it).
Any suggestion?
It is unlikely that Windows updates have deleted any services.
You should still be able to see the Hyper-V Virtual Machine Management service even if it is stopped or running/broken.
If not, I suggest that you re-install the Hyper-V role.