<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>LEVERAGE POINT</title>
    <link>https://leverage-point.dev/</link>
    <description>Recent content on LEVERAGE POINT</description>
    <generator>Hugo</generator>
    <language>ko-kr</language>
    <lastBuildDate>Wed, 27 May 2026 00:00:00 +0900</lastBuildDate>
    <atom:link href="https://leverage-point.dev/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>종료 지향 워크로드와 Kubernetes의 철학적 경계 (CRD를 만들며 배운 것들)</title>
      <link>https://leverage-point.dev/posts/k8s-job-crd-philosophical-boundary/</link>
      <pubDate>Wed, 27 May 2026 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/k8s-job-crd-philosophical-boundary/</guid>
      <description>&lt;p&gt;Job 관련 CRD를 계속 개발하다 보면 어느 순간 &amp;ldquo;왜 이게 이렇게 안 맞지?&amp;ldquo;라는 느낌을 받게 된다. 도구가 잘못된 건지, 설계가 잘못된 건지, 아니면 제가 뭔가 놓치고 있는 건지. 이 글은 그 느낌의 근원을 추적하다가 도달한 하나의 결론에 대한 이야기입니다.&lt;/p&gt;
&lt;p&gt;회사에서 Job 관련 워크로드를 만들면서 부딪힌 마찰들이 모두 같은 뿌리에서 나왔다는 사실을 뒤늦게 깨닫게 되었습니다.&lt;/p&gt;
&lt;h2 id=&#34;kubernetes의-본질&#34;&gt;Kubernetes의 본질&lt;/h2&gt;
&lt;p&gt;Kubernetes를 사용하다 보면 &amp;ldquo;선언적&amp;quot;이라는 단어를 자주 듣는다. 하지만 선언적이라는 말보다 더 정확한 표현은 &lt;strong&gt;level-triggered reconciliation&lt;/strong&gt;라고 봅니다.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Elasticsearch Lucene Write Lock 문제 해결 가이드 - CSI 장애와 StatefulSet 복구</title>
      <link>https://leverage-point.dev/posts/elasticsearch-lucene-write-lock-csi-troubleshooting/</link>
      <pubDate>Mon, 17 Nov 2025 01:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/elasticsearch-lucene-write-lock-csi-troubleshooting/</guid>
      <description>Kubernetes 환경에서 CSI 이상으로 Elasticsearch 클러스터가 마비될 때 Lucene write.lock 충돌 해결 방법과 StatefulSet 안전 관리, 인프라팀 협업 가이드를 제공합니다.</description>
    </item>
    <item>
      <title>Kubernetes 컨테이너에서 MIG 활성화된 GPU 메모리 정보를 안전하게 조회하기</title>
      <link>https://leverage-point.dev/posts/k8s-mig-gpu-memory-monitoring-troubleshooting/</link>
      <pubDate>Fri, 16 May 2025 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/k8s-mig-gpu-memory-monitoring-troubleshooting/</guid>
      <description>MIG 모드가 켜진 NVIDIA GPU를 Kubernetes 컨테이너에서 모니터링할 때 나타나는 Insufficient Permissions 오류의 원인과 해결 방법, 그리고 권한 최소화 사례를 정리합니다.</description>
    </item>
    <item>
      <title>GCP에 VM으로 직접 쿠버네티스 클러스터 구축하는 방법</title>
      <link>https://leverage-point.dev/posts/how-to-setup-k8s-on-gcp-with-kubeadm/</link>
      <pubDate>Tue, 13 May 2025 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/how-to-setup-k8s-on-gcp-with-kubeadm/</guid>
      <description>kubeadm을 활용한 프로덕션 수준의 쿠버네티스 클러스터(Kubernetes Cluster) 구축 경험을 정리합니다.</description>
    </item>
    <item>
      <title>AWS S3 버킷 보안 세팅 문제 해결</title>
      <link>https://leverage-point.dev/posts/aws-s3-boto3-bucket-troubleshooting/</link>
      <pubDate>Tue, 17 Oct 2023 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/aws-s3-boto3-bucket-troubleshooting/</guid>
      <description>Boto3를 활용하여 AWS S3에 데이터를 저장할 때 발생한 문제와 해결 방법</description>
    </item>
    <item>
      <title>pg_stat_statements로 쿼리 성능 모니터링하기</title>
      <link>https://leverage-point.dev/posts/monitoring-query-performance-with-pg-stat-statements/</link>
      <pubDate>Thu, 13 Jul 2023 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/monitoring-query-performance-with-pg-stat-statements/</guid>
      <description>docker-compose에서 PostgreSQL을 실행하고 pg_stat_statements 모듈을 활성화하여 쿼리 성능을 모니터링하는 방법을 알아보자.</description>
    </item>
    <item>
      <title>Django에서 DB Connection 관리</title>
      <link>https://leverage-point.dev/posts/django-db-connections-management/</link>
      <pubDate>Sun, 11 Dec 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/django-db-connections-management/</guid>
      <description>DB Connection 관리방식(DB Connection Pool, Persistent Connection)과 Django DB Connection 관리방식</description>
    </item>
    <item>
      <title>AWS ECR로 Docker 이미지 관리하기</title>
      <link>https://leverage-point.dev/posts/managing-docker-images-with-aws-ecr/</link>
      <pubDate>Fri, 17 Jun 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/managing-docker-images-with-aws-ecr/</guid>
      <description>AWS Amazon ECR(Elastic Container Registry)로 도커 이미지를 푸시, 풀, 삭제하기</description>
    </item>
    <item>
      <title>Memory Management 2.</title>
      <link>https://leverage-point.dev/posts/os-memory-management-2/</link>
      <pubDate>Fri, 25 Feb 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/os-memory-management-2/</guid>
      <description>Paging 기법에 대하여</description>
    </item>
    <item>
      <title>Memory Management 1.</title>
      <link>https://leverage-point.dev/posts/os-memory-management-1/</link>
      <pubDate>Mon, 14 Feb 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/os-memory-management-1/</guid>
      <description>Memory management overview</description>
    </item>
    <item>
      <title>Deadlock</title>
      <link>https://leverage-point.dev/posts/2022-02-10-os-deadlock/</link>
      <pubDate>Thu, 10 Feb 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/2022-02-10-os-deadlock/</guid>
      <description>Deadlock의 개념과 발생조건 및 처리방법에 대하여</description>
    </item>
    <item>
      <title>NoSQL</title>
      <link>https://leverage-point.dev/posts/nosql/</link>
      <pubDate>Wed, 09 Feb 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/nosql/</guid>
      <description>NoSQL의 개념과 종류(Key-value, Column, Document, Graph)에 대하여</description>
    </item>
    <item>
      <title>Process Synchronization 5.</title>
      <link>https://leverage-point.dev/posts/os-process-synchronization-5/</link>
      <pubDate>Tue, 08 Feb 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/os-process-synchronization-5/</guid>
      <description>Monitor에 대하여</description>
    </item>
    <item>
      <title>Process Synchronization 4.</title>
      <link>https://leverage-point.dev/posts/os-process-synchronization-4/</link>
      <pubDate>Sun, 06 Feb 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/os-process-synchronization-4/</guid>
      <description>Classical problem of synchronization. (Dining-Philosophers Problem. e.t.c.)</description>
    </item>
    <item>
      <title>빅오(Big-O) 표기법</title>
      <link>https://leverage-point.dev/posts/big-o-notation/</link>
      <pubDate>Sat, 05 Feb 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/big-o-notation/</guid>
      <description>알고리즘 성능 분석 측면의 접근을 통한 빅오 표기법이 필요한 이유</description>
    </item>
    <item>
      <title>Process Synchronization 3.</title>
      <link>https://leverage-point.dev/posts/os-process-synchronization-3/</link>
      <pubDate>Fri, 04 Feb 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/os-process-synchronization-3/</guid>
      <description>About Semaphore.</description>
    </item>
    <item>
      <title>Process Synchronization 2.</title>
      <link>https://leverage-point.dev/posts/os-process-synchronization-2/</link>
      <pubDate>Thu, 03 Feb 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/os-process-synchronization-2/</guid>
      <description>About critical section. Algorithm to critical section problem solve.</description>
    </item>
    <item>
      <title>Process Synchronization 1.</title>
      <link>https://leverage-point.dev/posts/os-process-synchronization-1/</link>
      <pubDate>Sat, 22 Jan 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/os-process-synchronization-1/</guid>
      <description>Process synchronization overview.</description>
    </item>
    <item>
      <title>CPU 스케줄링 3.</title>
      <link>https://leverage-point.dev/posts/os-cpu-scheduling-3/</link>
      <pubDate>Wed, 12 Jan 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/os-cpu-scheduling-3/</guid>
      <description>다양한 상황에서의 CPU 스케줄링 알고리즘에 대하여</description>
    </item>
    <item>
      <title>CPU 스케줄링 2.</title>
      <link>https://leverage-point.dev/posts/os-cpu-scheduling-2/</link>
      <pubDate>Sun, 09 Jan 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/os-cpu-scheduling-2/</guid>
      <description>일반적인 CPU 스케줄링 알고리즘에 대하여</description>
    </item>
    <item>
      <title>CPU 스케줄링 1.</title>
      <link>https://leverage-point.dev/posts/os-cpu-scheduling-1/</link>
      <pubDate>Thu, 06 Jan 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/os-cpu-scheduling-1/</guid>
      <description>CPU 스케줄링이란 무엇인가</description>
    </item>
    <item>
      <title>Process Management 2.(Cooperating Process)</title>
      <link>https://leverage-point.dev/posts/os-process-management-2/</link>
      <pubDate>Wed, 05 Jan 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/os-process-management-2/</guid>
      <description>IPC(Inter Process Communication)에 대하여</description>
    </item>
    <item>
      <title>Process Management 1. (Creation, Execution, Wait &amp; Exit)</title>
      <link>https://leverage-point.dev/posts/os-process-management-1/</link>
      <pubDate>Sat, 01 Jan 2022 00:00:00 +0900</pubDate>
      <guid>https://leverage-point.dev/posts/os-process-management-1/</guid>
      <description>프로세스 생성과 종료에 대하여 </description>
    </item>
  </channel>
</rss>
