Skip to content

Commit

Permalink
chore: Update content
Browse files Browse the repository at this point in the history
  • Loading branch information
younsl committed Jun 8, 2024
1 parent 460d881 commit 830dc60
Show file tree
Hide file tree
Showing 2 changed files with 28 additions and 13 deletions.
15 changes: 8 additions & 7 deletions content/about/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,13 +24,14 @@ May 30, 2023 ― Present <small>(1 yr 1 mo)</small>
AWS, GCP, Kubernetes, Observability, CI/CD, Terraform, Infrastructure Ops

- Manage and operate 6 EKS clusters in a multi-stage environment: experienced EKS versions v1.24 to v1.27.
- Operate Kubernetes policy engine <sup>Kyverno</sup> and Node Termination Handler.
- Operate Kubernetes policy engine <sup>Kyverno</sup> and Node Termination Handler. [[1](/blog/k8s/kyverno/)] [[2](/blog/k8s/nth/)]
- Improve scalability by applying pod autoscaling based on Throughput Per Seconds metric using KEDA in the production environment. [[1](/blog/k8s/keda/)]
- Automate repetitive operational tasks.
- Operate CI/CD pipeline based on Github Actions Workflow and ArgoCD.
- Build and operate Github Enterprise Server, Github Enterprise backup utilities and Actions Runner Controller.
- Build and operate MSK Cluster and OpenSearch Cluster.
- Migrate github enterprise backup server <sup>[backup-utils](https://github.com/github/backup-utils)</sup> workload from EC2 to EKS CronJob for leveraging dedicated EKS cluster.
- Develop and release [backup-utils-chart](https://github.com/younsl/charts/tree/main/charts/backup-utils) project as a maintainer.
- Build and operate MSK Cluster and OpenSearch Cluster. [[1](/blog/kafka/)] [[2](/blog/elasticsearch-admin-guide/)]
- Build and operate Github Enterprise Server, Github Enterprise backup utilities and Actions Runner Controller. [[1](/blog/ghe-backup-utils/)] [[2](/blog/k8s/actions-runner-admin-guide/)]
- Containerize github enterprise backup server <sup>[backup-utils](https://github.com/github/backup-utils)</sup> and migrate workload from EC2 to kubernetes cronJob for leveraging dedicated EKS cluster.
- Develop and release helm chart for backup-utils as a maintainer. [[1](https://github.com/younsl/charts/tree/main/charts)]
- Provision and operate multi-account AWS infrastructure using terraform modules.
- Integrate private networking between GCP and AWS to connect GCP Service APIs from EKS Pods.

Expand All @@ -41,8 +42,8 @@ Sep 5, 2022 ― Apr 7, 2023 <small>(7 mos)</small>

AWS, Kubernetes, Istio, Observability, CI/CD, Terraform, MLOps, Infrastructure Ops

- Acquired electronic finance business license <sup>[#2022-483](https://www.fsc.go.kr/po040200/79214?srchCtgry=&curPage=&srchKey=&srchText=&srchBeginDt=&srchEndDt)</sup> after building multi-account AWS infrastructure for 3 months from September to December 2022.
- Managed and operated 2 EKS clusters in a multi-stage environment: experienced EKS versions v1.24 to v1.25. <sup>[](https://docs.aws.amazon.com/ko_kr/eks/latest/userguide/kubernetes-versions.html#kubernetes-release-calendar)</sup>
- Acquired electronic finance business license #2022-483 after building multi-account AWS infrastructure for 3 months from September to December 2022. [[1](https://www.fsc.go.kr/po040200/79214?srchCtgry=&curPage=&srchKey=&srchText=&srchBeginDt=&srchEndDt)]
- Managed and operated 2 EKS clusters in a multi-stage environment: experienced EKS versions v1.24 to v1.25. [[1](https://docs.aws.amazon.com/ko_kr/eks/latest/userguide/kubernetes-versions.html#kubernetes-release-calendar)]
- Provisioned and operated multi-stage AWS infrastructure using terraform.
- FinOps: Optimized multi-account infrastructure and reduced monthly AWS cost from $6800 to $4800, 30% monthly cost savings from Jan 2023 to Mar 2023.

Expand Down
26 changes: 20 additions & 6 deletions content/blog/k8s/nri-bundle/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -344,17 +344,31 @@ kube-state-metrics:

#### Deployment 히스토리 보관 수 조정

```diff
# deployment.yaml
Deployment `spec` 설정 중 하나인 `revisionHistoryLimit`는 Kubernetes에서 Deployment의 롤아웃 기록을 보관할 최대 개수를 설정하는 속성입니다. 기본적으로 `10`개의 이전 버전이 보관되며, 이 제한을 초과하면 가장 오래된 배포 기록부터 삭제됩니다.

```yaml
apiVersion: apps/v1
kind: Deployment
...
metadata:
# ...
spec:
- revisionHistoryLimit: 10
+ revisionHistoryLimit: 0
revisionHistoryLimit: 10
```
`revisionHistoryLimit`을 기본값 `10``0`으로 줄이는 경우, **20%의 데이터를 절감**할 수 있습니다. 대신 Deployment의 률백이 필요없는 경우에만 `revisionHistoryLimit``0`으로 지정하도록 합니다.
이는 시스템의 리소스를 효율적으로 사용하고 필요시 이전 버전으로 롤백할 수 있는 기능을 제공합니다.
&nbsp;
`revisionHistoryLimit`을 기본값 `10` → `0`으로 줄이는 경우, **20%의 데이터를 절감**할 수 있습니다. 대신 Deployment의 롤백이 필요없는 경우에만 `revisionHistoryLimit`을 `0`으로 지정하도록 합니다.

```yaml
apiVersion: apps/v1
kind: Deployment
metadata:
# ...
spec:
revisionHistoryLimit: 0
```

&nbsp;

Expand Down

0 comments on commit 830dc60

Please sign in to comment.