• 개인정보 보호법 시행령
• 제15조의3(개인정보 이용ㆍ제공 내역의 통지)
• 배치에러 too many missed start times. Set or decrease .spec.startingDeadlineSeconds or check clock skew
  • 배치 Job 을 cronJob 으로 돌리다가 위와 같은 에러가 발생. 이게 예약된 시간에 Job 이 실행되지 않아서 발생한 에러.
• K8S

Reclaim Policy 는 PersistentVolume 을 삭제할 때 어떻게 할 지 정하는 정책.

• Retain : 삭제해도 PV 은 삭제되지 않고 남아있음.
• Recycle : 삭제하면 PV 을 삭제하고 디렉토리를 비움.
• Delete : 삭제하면 PV 을 삭제하고 디렉토리도 삭제함.

AWS EFS 에 PVC 마운트 할려는데 DNS resolusion 에러 발생. efs-helper 로 region 찾는데 이게 잘못 설정되어있어서 발생하는 문제인듯?

reference : https://repost.aws/questions/QUvJFK8DpaQH631PQH8kfUGw/cannot-get-a-vpc-peered-efs-accesspoint-to-mount

OK, 100% the issue is that the EFS mount helper doesn’t know the right region. When I update efs-utils.conf

다시 체크해봤는데 VPC 가 다른 곳으로 설정되어 있었음. 그래서 DNS resolution 이 되지 않았던 거임. EFS 가 VPC 내부에서만 접근 가능한데, 다른 VPC 에서 접근하려면 VPC Peering 이 필요함.

ghkdqhrbals ~ % nslookup fs-....efs.ap-northeast-2.amazonaws.com
...

** server can't find fs-....efs.ap-northeast-2.amazonaws.com: NXDOMAIN

ghkdqhrbals ~ % nslookup fs-....efs.ap-northeast-2.amazonaws.com 
...

Non-authoritative answer:
Name:	fs-....efs.ap-northeast-2.amazonaws.com

• grafana persistence=true 시 admin password renew X. 옛날 admin password 가 남아있음.

  You have persistence enabled, so old/previous admin password is there. Disable persistence, so you will loose dashboard, configs, passwords, so password from that env variable will be applied. You may try to enable persistence later. https://community.grafana.com/t/unable-to-login-as-admin-in-grafana/119864

  PV Delete 변경하고 제거한 뒤 다시 생성해야함

• Personal Information Protection Act Enforcement Decree
• Article 15-3, Notice of personal information use and provision history
• Batch error: too many missed start times. Set or decrease .spec.startingDeadlineSeconds or check clock skew
  • This error occurred while running a batch job as a cronJob. It happens when the job is not executed at the scheduled time.
• K8S

Reclaim Policy defines what to do when a PersistentVolume is deleted.

• Retain: even if deleted, the PV is not deleted and remains.
• Recycle: when deleted, the PV is deleted and the directory is emptied.
• Delete: when deleted, the PV and the directory are both deleted.

While trying to mount a PVC to AWS EFS, a DNS resolution error occurred. It seems to be a problem where the EFS helper tries to find the region, but the region is configured incorrectly.

reference: https://repost.aws/questions/QUvJFK8DpaQH631PQH8kfUGw/cannot-get-a-vpc-peered-efs-accesspoint-to-mount

OK, 100% the issue is that the EFS mount helper doesn’t know the right region. When I update efs-utils.conf

I checked again, and the VPC was configured to a different place. That was why DNS resolution did not work. EFS can only be accessed inside the VPC, and if you want to access it from another VPC, VPC Peering is required.

ghkdqhrbals ~ % nslookup fs-....efs.ap-northeast-2.amazonaws.com
...

** server can't find fs-....efs.ap-northeast-2.amazonaws.com: NXDOMAIN

ghkdqhrbals ~ % nslookup fs-....efs.ap-northeast-2.amazonaws.com
...

Non-authoritative answer:
Name:	fs-....efs.ap-northeast-2.amazonaws.com

• When Grafana persistence=true, the admin password is not renewed. The old admin password remains.

  You have persistence enabled, so old/previous admin password is there. Disable persistence, so you will loose dashboard, configs, passwords, so password from that env variable will be applied. You may try to enable persistence later. https://community.grafana.com/t/unable-to-login-as-admin-in-grafana/119864

  Change PV to Delete, remove it, and create it again.