Download volume balancer

Addon. --enable-workload-identity (PREVIEW) Enable Workload Identity addon for cluster. --ephemeral-disk-nvme-perf-tier Set ephemeral disk volume type for azure container storage. Accepted values: Basic, Premium, Standard--ephemeral-disk-volume-type Set ephemeral disk volume type for azure container storage. Accepted values: EphemeralVolumeOnly, PersistentVolumeWithAnnotation Specify DNS server for Windows gmsa on cluster. You do not need to set this if you have set DNS server in the VNET used by the cluster.You must set or not set --gmsa-dns-server and --gmsa-root-domain-name at the same time when setting --enable-windows-gmsa. Specify root domain name for Windows gmsa on cluster. You do not need to set this if you have set DNS server in the VNET used by the cluster.You must set or not set --gmsa-dns-server and --gmsa-root-domain-name at the same time when setting --enable-windows-gmsa. Resource ID of the Azure Managed Grafana Workspace. HTTP Proxy configuration for this cluster. The value provided will be compared to the ETag of the managed cluster, if it matches the operation will proceed. If it does not match, the request will be rejected to prevent accidental overwrites. This must not be specified when creating a new cluster. Set to '*' to allow a new cluster to be created, but to prevent updating an existing cluster. Other values will be ignored. --image-cleaner-interval-hours ImageCleaner scanning interval. A comma separated list of IP versions to use for cluster networking. Each IP version should be in the format IPvN. For example, IPv4. Choose from "KubernetesOfficial" or "AKSLongTermSupport", with "AKSLongTermSupport" you get 1 extra year of CVE patchs. Accepted values: AKSLongTermSupport, KubernetesOfficial--ksm-metric-annotations-allow-list Comma-separated list of additional Kubernetes label keys that will be used in the resource' labels metric. By default the metric contains only name and namespace labels. To include additional labels provide a list of resource names in their plural form and Kubernetes label keys you would like to allow for them (e.g.'=namespaces=[k8s-label-1,k8s-label-n,...],pods=[app],...)'. A single '' can be provided per resource instead to allow any labels, but that has severe performance implications (e.g. '=pods=[]'). --ksm-metric-labels-allow-list Comma-separated list of additional Kubernetes label keys that will be used in the resource' labels metric. By default the metric contains only name and namespace labels. To include additional labels provide a list of resource names in their plural form and Kubernetes label keys you would like to allow for them (e.g. '=namespaces=[k8s-label-1,k8s-label-n,...],pods=[app],...)'. A single '' can be provided per resource instead to allow any labels, but that has severe performance implications (e.g. '=pods=[]'). Kube-proxy configuration for this cluster. --load-balancer-backend-pool-type Load balancer backend pool type. Load balancer backend pool type, supported values are nodeIP and nodeIPConfiguration.--load-balancer-idle-timeout Load balancer idle timeout in minutes. Desired idle timeout for load balancer outbound flows, default is 30 minutes. Please specify a value in the range of [4, 100].--load-balancer-managed-outbound-ip-count

IntroductionSometimes on projects with tight budgets we don’t have access to expensive APM tools like DataDog and New Relic. In such projects, there is no easy way to find out which of the APIs are slow causing performance issues for your application. In such cases, processing AWS Application Load Balancer logs which (if enabled) are stored in a S3 bucket can lead to valuable insights.This tutorial walks you through the process of downloading Application Load Balancer logs from AWS S3, consolidating them, and analyzing them using tools like GoAccess, Excel, and SQLite. By the end of this guide, you’ll be able to extract meaningful metrics and identify slow requests or errors impacting your application’s performance.You will need:AWS CLI configured with the necessary permissions to access your Application Load Balancer logs in S3. You can get it from here.GoAccess installed on your local machine for log analysis. You can get it from hereSQLite3 installed for querying log data. On all modern Linux and Mac machines SQLite should be available by default. If you are using Windows, please use WSL2 follow this tutorial.Excel: Excel or any spreadsheet software for additional data manipulation.Step 1: Configure AWS CLI and Download the LogsFirst, ensure your AWS CLI is configured correctly:aws configureProvide your AWS Access Key ID, Secret Access Key, Default Region, and Default Output Format when prompted.Next, synchronize your Application Load Balancer logs from the S3 bucket to a local directory:aws s3 sync s3://your-alb-logs-bucket/path/to/logs ./alb-logsReplace s3://your-alb-logs-bucket/path/to/logs with the actual S3 path to your Application Load Balancer logs../alb-logs is the local directory where the logs will be downloaded.Note: The logs will be downloaded into a nested directory structure organized by year, month, and day.Step 2: Consolidate Log FilesTo simplify processing, it’s helpful to move all .log.gz files into a single directory.Navigate to your logs directory:cd alb-logsUse the following command to find and move all .log.gz files to the current directory:find . -type f -name "*.log.gz" -exec mv {} . \;Explanation:find .: Searches in the current directory and subdirectories.-type f: Looks for files.-name "*.log.gz": Matches files ending with .log.gz.-exec mv {} . \;: Executes the mv command to move each found file to the current directory.Step 3: Combine Logs into a Single FileUnzip and combine all log files into one file for easier processing:gunzip -c *.log.gz > combined-log.txtExplanation:gunzip -c: Unzips the files and outputs to stdout.*.log.gz: Matches all compressed log files.> combined-log.txt: Redirects the output to combined-log.txt.Optional: Check the number of log lines:cat combined-log.txt | wc -lThis command counts the number of lines in the combined log file, giving you an idea of the volume of data you’re working with.Step 4: Analyze Logs with GoAccessUse GoAccess to parse and analyze the combined log file:cat combined-log.txt | goaccess

[--disable-pod-security-policy] [--disable-private-cluster] [--disable-public-fqdn] [--disable-secret-rotation] [--disable-snapshot-controller] [--disable-static-egress-gateway] [--disable-vpa] [--disable-workload-identity] [--disk-driver-version {v1, v2}] [--enable-aad] [--enable-acns] [--enable-addon-autoscaling] [--enable-ahub] [--enable-ai-toolchain-operator] [--enable-apiserver-vnet-integration] [--enable-azure-container-storage {azureDisk, elasticSan, ephemeralDisk}] [--enable-azure-keyvault-kms] [--enable-azure-monitor-app-monitoring] [--enable-azure-monitor-metrics] [--enable-azure-rbac] [--enable-blob-driver] [--enable-cluster-autoscaler] [--enable-cost-analysis] [--enable-defender] [--enable-disk-driver] [--enable-file-driver] [--enable-force-upgrade] [--enable-image-cleaner] [--enable-image-integrity] [--enable-imds-restriction] [--enable-keda] [--enable-local-accounts] [--enable-managed-identity] [--enable-oidc-issuer] [--enable-pod-identity] [--enable-pod-identity-with-kubenet] [--enable-private-cluster] [--enable-public-fqdn] [--enable-secret-rotation] [--enable-snapshot-controller] [--enable-static-egress-gateway] [--enable-vpa] [--enable-windows-gmsa] [--enable-windows-recording-rules] [--enable-workload-identity] [--ephemeral-disk-nvme-perf-tier {Basic, Premium, Standard}] [--ephemeral-disk-volume-type {EphemeralVolumeOnly, PersistentVolumeWithAnnotation}] [--gmsa-dns-server] [--gmsa-root-domain-name] [--grafana-resource-id] [--http-proxy-config] [--if-match] [--if-none-match] [--image-cleaner-interval-hours] [--ip-families] [--k8s-support-plan {AKSLongTermSupport, KubernetesOfficial}] [--ksm-metric-annotations-allow-list] [--ksm-metric-labels-allow-list] [--kube-proxy-config] [--load-balancer-backend-pool-type] [--load-balancer-idle-timeout] [--load-balancer-managed-outbound-ip-count] [--load-balancer-managed-outbound-ipv6-count] [--load-balancer-outbound-ip-prefixes] [--load-balancer-outbound-ips] [--load-balancer-outbound-ports] [--max-count] [--min-count] [--nat-gateway-idle-timeout] [--nat-gateway-managed-outbound-ip-count] [--network-dataplane {azure, cilium}] [--network-plugin {azure, kubenet, none}] [--network-plugin-mode] [--network-policy] [--no-wait] [--node-init-taints] [--node-os-upgrade-channel {NodeImage, None, SecurityPatch, Unmanaged}] [--node-provisioning-mode {Auto, Manual}] [--nodepool-labels] [--nodepool-taints] [--nrg-lockdown-restriction-level {ReadOnly, Unrestricted}] [--outbound-type {block, loadBalancer, managedNATGateway, none, userAssignedNATGateway, userDefinedRouting}] [--pod-cidr] [--private-dns-zone] [--rotation-poll-interval] [--safeguards-excluded-ns] [--safeguards-level {Enforcement, Off, Warning}] [--safeguards-version] [--sku {automatic, base}] [--ssh-key-value] [--storage-pool-name] [--storage-pool-option {NVMe, Temp, all}] [--storage-pool-size] [--storage-pool-sku {PremiumV2_LRS, Premium_LRS, Premium_ZRS, StandardSSD_LRS, StandardSSD_ZRS, Standard_LRS, UltraSSD_LRS}] [--tags] [--tier {free, premium, standard}] [--update-cluster-autoscaler] [--upgrade-override-until] [--windows-admin-password] [--yes] Examples Reconcile the cluster back to its current state. az aks update -g MyResourceGroup -n MyManagedCluster Enable cluster-autoscaler within node count range [1,5] az aks update --enable-cluster-autoscaler --min-count 1 --max-count 5 -g MyResourceGroup -n MyManagedCluster Disable cluster-autoscaler for an existing cluster az aks update --disable-cluster-autoscaler -g MyResourceGroup -n MyManagedCluster Update min-count or max-count for cluster autoscaler. az aks update --update-cluster-autoscaler --min-count 1 --max-count 10 -g MyResourceGroup -n MyManagedCluster Disable pod security policy. az aks update --disable-pod-security-policy -g MyResourceGroup -n MyManagedCluster Update a kubernetes cluster with standard SKU load balancer to use two AKS created IPs for the load balancer outbound connection usage. az aks update -g MyResourceGroup -n MyManagedCluster --load-balancer-managed-outbound-ip-count 2 Update a kubernetes cluster with standard SKU load balancer to use the provided public IPs for the load balancer outbound connection usage. az aks update -g MyResourceGroup -n MyManagedCluster --load-balancer-outbound-ips Update a kubernetes cluster with standard SKU load balancer to use the provided public IP prefixes for the load balancer outbound connection usage. az aks update -g MyResourceGroup -n MyManagedCluster --load-balancer-outbound-ip-prefixes Update a kubernetes cluster with new outbound type az aks update -g MyResourceGroup -n MyManagedCluster --outbound-type managedNATGateway Update a kubernetes cluster with two outbound AKS managed IPs an idle flow timeout of 5 minutes and 8000 allocated ports per machine az aks update -g MyResourceGroup -n MyManagedCluster --load-balancer-managed-outbound-ip-count 2 --load-balancer-idle-timeout 5 --load-balancer-outbound-ports 8000 Update a kubernetes cluster of managedNATGateway outbound type with two outbound AKS managed IPs an idle flow timeout of 4 minutes az aks update -g MyResourceGroup -n MyManagedCluster --nat-gateway-managed-outbound-ip-count 2 --nat-gateway-idle-timeout 4 Update a kubernetes cluster with authorized apiserver ip ranges. az aks update -g MyResourceGroup -n MyManagedCluster --api-server-authorized-ip-ranges 193.168.1.0/24,194.168.1.0/24 Disable authorized apiserver ip ranges feature for a kubernetes cluster. az aks update -g MyResourceGroup -n MyManagedCluster --api-server-authorized-ip-ranges "" Restrict apiserver traffic in a kubernetes cluster