0

Prometheus server with its respective Loadbalancer in AKS.

I wanted to secure the access to /metrics through network rules...but it doesn't work. I can still acess to the endpoint with any device.

  az network nsg rule create \
    --resource-group $AKS_RESOURCE_GROUP \
    --nsg-name $AKS_NSG \
    --name DenyAcess \
    --access Deny \
    --protocol Tcp \
    --direction Inbound \
    --priority 521 \
    --source-address-prefix "*" \
    --source-port-range "*" \
    --destination-port-range 9090

  az network nsg rule create \
    --resource-group $AKS_RESOURCE_GROUP \
    --nsg-name $AKS_NSG \
    --name AllowSpecificIP \
    --access Allow \
    --protocol Tcp \
    --direction Inbound \
    --priority 522 \
    --source-address-prefix $MY_CERTAIN_IP \
    --source-port-range "*" \
    --destination-port-range 9090

I was trying to avoid installing any ingress like haproxy or nginx-ingress...it's the only way to restrict access to the Prometheus endpoint?

Extra: Basic authorization with Prometheus in Helm doesn't work either, it could be useful too :(

Wadjet
  • 1

0 Answers0