Ernie Costa
Ernie Costa
We worked thru this by leveraging some type of other HTTP load balancer in front of nginx/AKS-Hybrid. In our case, we used a Netscaler appliance and passed it on using...
I see this was added to Azure Portal. Is it exposed through PowerShell modules?
Hey @PragyaDw - I see this was maybe gonna make the Jan/Feb release? Is there any update on it?
I cannot stress how important and awesome this would be! Folks commonly undersize their VIP pool, especially in POC scenarios. They also don't understand _how_ VIPs are used and can...
@Elektronenvolt - assume you had small pools for both service IPs and node IPs. When you upgrade AKS-HCI, it spawns new Worker Node VMs (which burns a node IP) and...
@Elektronenvolt - I dont have any error messages available without spinning and repro'ing in a lab. But yes, that error message you pasted looks familiar.
@PragyaDw - this would be amazing to get back into the queue for a future release. Folks misconfigure production clusters all the time. To have to tear down AKS-Hybrid just...
[BUG] Moc checks for Powershell Remoting are incorrect in assumptions about single-node availability
Well, after smashing my head against a keyboard for awhile, it appears that this user's Hyper-V host was misconfigured to use incorrect DNS servers that couldn't resolve shortnames, but obviously...
[BUG] Moc checks for Powershell Remoting are incorrect in assumptions about single-node availability
Negative, def not a DNS problem on my side. Brand new server with correct DNS, the same error occurs:  I just edited Moc, Kva, and AksHci modules and replaced...
[BUG] Moc checks for Powershell Remoting are incorrect in assumptions about single-node availability
There appears to be a few spots in KVA, MOC, and AKSHCI cmdlets that also use `hostname` instead of `$env:COMPUTERNAME`. Again, by replacing that with something that generates an FQDN,...