nileshgule / pd-tech-fest-2019 Goto Github PK

Dependabot couldn't reach https://dotnet.myget.org/F/dotnet-core/api/v3/index.json as it timed out.

Is https://dotnet.myget.org/F/dotnet-core/api/v3/index.json accessible over the internet? If it is then this may be a transitory issue and can be ignored - Dependabot will close it on its next successful update run.

View the update logs.

I am using windows-10-Pro, 64 bit and windows power-shell versions as below for dev environment...

Name                           Value
----                           -----
PSVersion                      5.1.19041.610
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.610
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Also, I am new to power-shell and tried to execute initializeAKS.ps1 for provisioning an AKS infrastructure but it was failing with an error like
"az: error: unrecognized arguments: --enable-managed-identity --aks-custom-headers=CustomizedUbuntu=aks-ubuntu-1804,ContainerRuntime=containerd --attach-acr=ngAcrRegistry2"
Below mentioned script's code-block was giving an exception .. Pls help or suggest to enabling managed-identity with AKS ..

if ($aksCLusterExists -eq $false) {
    # Create AKS cluster
    Write-Host "Creating AKS cluster $clusterName with resource group $resourceGroupName in region $resourceGroupLocaltion" -ForegroundColor Yellow
    az aks create `
        --resource-group=$resourceGroupName `
        --name=$clusterName `
        --node-count=$workerNodeCount `
        --enable-managed-identity `
        --output=jsonc `
        --kubernetes-version=$kubernetesVersion `
        --aks-custom-headers="CustomizedUbuntu=aks-ubuntu-1804,ContainerRuntime=containerd" `
        --attach-acr=$acrRegistryName '

} 

Pls, Any suggestions..

Many Thanks,

We'll be updating the KEDA Samples README to call out which samples only work with KEDA 1.0. It looks like you'd need changes to make this 2.0 compatible (in deployment), so creating issue here to call out. Here's a link to the migration guide for 2.0 https://keda.sh/docs/2.0/migration/

Thanks regardless for this sample!

helm and heml