Tag Archives: Kubernetes

Helm: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress
0 (0)

24 May 2024

Sometimes, when deploying Helm charts, the error “UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress” may appear: It can occur because the previous deployment failed due to errors in the chart, or the connection between the build machine and the Kubernetes cluster was lost. Check the release status with ls –all: $ helm -n dev-backend-api-ns… Read More: Helm: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress0 (0) »

Loading

AWS: VPC Flow Logs, NAT Gateways, and Kubernetes Pods – a detailed overview
5 (1)

5 May 2024

We have a relatively large spending on AWS NAT Gateway Processed Bytes, and it became interesting to know what exactly is processed through it. It would seem that everything is simple – just turn on VPC Flow Logs and see what’s what. But when it comes to AWS Elastic Kubernetes Service and NAT Gateways, things… Read More: AWS: VPC Flow Logs, NAT Gateways, and Kubernetes Pods –… »

Loading

AWS: VPC Prefix and the maximum of Pods on Kubernetes WorkerNodes
0 (0)

29 February 2024

Each WorkerNode in a Kubernetes cluster can have a limited number of Pods running, and this limit is determined by three parameters: CPU: the total number of requests.cpu cannot be more than the number of CPUs on the Node Memory: the total number of requests.memory cannot be more than the Memory on the Node IP:… Read More: AWS: VPC Prefix and the maximum of Pods on Kubernetes… »

Loading

Karpenter: its monitoring, and Grafana dashboard for Kubernetes WorkerNodes
0 (0)

18 February 2024

We have an AWS Elastic Kubernetes Service cluster with Karpenter which is responsible for EC2 auto-scaling, see AWS: Getting started with Karpenter for autoscaling in EKS, and its installation with Helm. In general, there are no problems with it so far, but in any case we need to monitor it. For its monitoring, Karpenter provides… Read More: Karpenter: its monitoring, and Grafana dashboard for Kubernetes WorkerNodes0 (0) »

Loading

AWS: EKS Pod Identities – a replacement for IRSA? Simplifying IAM access management
0 (0)

16 December 2023

Another very interesting new feature from the latest re:Invent is the EKS Pod Identities: a new ability to manage Pod access to AWS resources. The current state: IAM Roles for Service Accounts Before that, we used the IAM Roles for Service Accounts (IRSA) model, where in order to give a Pod access to, for example,… Read More: AWS: EKS Pod Identities – a replacement for IRSA? Simplifying… »

Loading

AWS Elastic Kubernetes Service: RBAC Authorization via AWS IAM and RBAC Groups
0 (0)

25 November 2023

We have two new projects in the Elastic Kubernetes Service (см. AWS Elastic Kubernetes Service: a cluster creation automation, part 1 – CloudFormation), each project lives in its own separate Namespace. In addition, there are two users, developers, who need to be given access to these two Namespaces, but only to Pods in them and… Read More: AWS Elastic Kubernetes Service: RBAC Authorization via AWS IAM and… »

Loading

Grafana Loki: collecting AWS LoadBalancer logs from S3 with Promtail Lambda
0 (0)

25 November 2023

Currently, we are able to collect our API Gateway logs from the CloudWatch Logs to Grafana Loki, see. Loki: collecting logs from CloudWatch Logs using Lambda Promtail. But in the process of migrating to Kubernetes, we have Application Load Balancers that can only write logs to S3, and we need to learn how to collect… Read More: Grafana Loki: collecting AWS LoadBalancer logs from S3 with Promtail… »

Loading

Kubernetes: ensuring High Availability for Pods
0 (0)

25 November 2023

We have a Kubernetes cluster, where WorkerNodes are scaled by Karpenter, and Karpenter has the disruption.consolidationPolicy=WhenUnderutilized parameter for its NodePool, and this means, that Karpenter will try to “consolidate” the placement of pods on Nodes in order to maximize the use of CPU and Memory resources. In general, everything works, but this leads to the… Read More: Kubernetes: ensuring High Availability for Pods0 (0) »

Loading

Kubernetes: Liveness and Readiness Probes – Best practices
0 (0)

18 November 2023

Some useful tips on using Liveness and Readiness Probes in Kubernetes – the difference between them, and how to properly configure these checks. To put it very briefly: livenessProbe: is used by Kubernetes to know when to perform a Pod restart readinessProbe: is used by Kubernetes to know when a container is ready to receive… Read More: Kubernetes: Liveness and Readiness Probes – Best practices0 (0) »

Loading

VictoriaMetrics: pushing metrics without Prometheus Pushgateway
0 (0)

18 November 2023

In the Prometheus: running Pushgateway on Kubernetes with Helm and Terraform post I wrote about how to add Pushgateway to Prometheus, which allows using the Push model instead of Pull, that is, an Exporter can send metrics directly to the database instead of waiting for Prometheus or VMAgent to come to it. With VictoriaMetrics, it’s… Read More: VictoriaMetrics: pushing metrics without Prometheus Pushgateway0 (0) »

Loading