In Go, there are several ways to allocate and initialize memory. Pre-requisite: undertsand types in Go var Declaration When you declare a variable using var: var x int var s string var m map[string]int var sl []int * The variable is zero-valued (0 for numeric types, "" for
Primitive Types Primitive types (also called basic types) are the simplest, fundamental data types that aren't composed of other types: * Numeric types: * Integers: int, int8, int16, int32, int64, uint, uint8, etc. * Floating-point: float32, float64 * Complex: complex64, complex128 * Boolean type: bool * String type: string These types store their values
A concept that serves as both a negotiation tool and a practical decision-making framework, on efficiency of an algorithm that suits the needs of current problem. Big O just tells how slower my program is going to be as the input size increases. So technically, It doesn't dictate
In my current organization, I wrote a helper script long back to organize and set up Kubernetes contexts across multiple GCP projects and environments, with custom naming based on cluster labels. I also created another script to handle all EKS clusters across AWS regions using a specified AWS SSO profile.
— The nightmares we all live are truly an inspiration to never live. Honesty is a fragile illusion, a reflection of never being good enough. We live to rule, and we rule to live—trapped in the chaos of collective minds, yet bound by the desperate need to be seen. Why?
We’ve been building gokakashi in Go for a while now, and we had this wild thought: “What if users could define their own evaluation conditions on top of the scan reports?” Something like this in the config file: check: condition: | sev.critical > 0 || sev.high > 0 &
This is how I finally made sense of interfaces in Go. There are countless resources out there, but fails to simplify how to grasp and implement interfaces effectively, atleast for me. While observing my niece one day (toddlers can be surprisingly inspiring!), an analogy clicked in my mind. Let me
Cardinality refers to the number of unique elements in a set or the number of distinct values in a data set. In the context of metrics and time-series data, cardinality refers to the number of unique combinations of metric name, label name, and label value that are present in a
k8s_terraform_metrics/templates/k8s_provider.tf at main · ashwiniag/k8s_terraform_metricsTerraform + K8s + Vicoriametrics + Kube-state-metrics + Prometheus operator - ashwiniag/k8s_terraform_metricsGitHubashwiniag
Simple setup to monitor my machine using node_exporter: Exposes my machine metrics at http://localhost:9100/metrics vmagent: Scrapes the metrics exposed at /metrics at defined interval and sends it to victoriametrics victoriametrics: It is a single node set up, a tsdb storage. grafana: Visual representation of metrics used
k8s_terraform_metrics/templates/ssm.tf at main · ashwiniag/k8s_terraform_metricsTerraform + K8s + Vicoriametrics + Kube-state-metrics + Prometheus operator - ashwiniag/k8s_terraform_metricsGitHubashwiniag
Most basic setup to have when working with terraform is - Where to store terraform statefile and avoid all hassles! Some issues you run into: * Access to tfstate: Needs access to same terraform statefile across the team to work with infra setup. Hence, statefiles are to be storedin shared location.