-
Notifications
You must be signed in to change notification settings - Fork 0
chore: 새로운 프로젝트에 맞는 값 변경 (#69) #70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -16,7 +16,7 @@ certManager: | |
|
|
||
| # DNS-01 Challenge (CloudDNS) | ||
| cloudDNS: | ||
| projectId: "dev-pinhouse" | ||
| projectId: "dev-pinhouse-2" | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
# Description: Verify GCP project readiness for Cert Manager and External Secrets
PROJECT_ID="dev-pinhouse-2"
echo "=== Checking if project exists ==="
gcloud projects describe "$PROJECT_ID" --format="value(projectId)" 2>/dev/null || echo "Project not found"
echo -e "\n=== Checking required APIs ==="
gcloud services list --enabled --project="$PROJECT_ID" --filter="name:(dns.googleapis.com OR secretmanager.googleapis.com)" --format="table(name)" 2>/dev/null
echo -e "\n=== Checking Secret Manager secrets with Dev_BE_ prefix ==="
gcloud secrets list --project="$PROJECT_ID" --filter="name~^Dev_BE_" --format="table(name)" 2>/dev/null
echo -e "\n=== Checking Secret Manager secrets for monitoring ==="
gcloud secrets list --project="$PROJECT_ID" --filter="name~^Dev_MONITORING_" --format="table(name)" 2>/dev/null
echo -e "\n=== Checking Swagger auth secret ==="
gcloud secrets list --project="$PROJECT_ID" --filter="name=Dev_SWAGGER_BASIC_AUTH" --format="table(name)" 2>/dev/nullRepository: PinHouse/PinHouse_CLOUD Length of output: 309 🏁 Script executed: # Check the values-dev.yaml file and surrounding context
cd k8s-helm/platform-chart || exit 1
wc -l values-dev.yaml
echo "---"
head -30 values-dev.yamlRepository: PinHouse/PinHouse_CLOUD Length of output: 565 🏁 Script executed: # Search for External Secrets configuration and Secret Manager references
grep -n -i "secret\|externalsecret" k8s-helm/platform-chart/values-dev.yaml | head -40Repository: PinHouse/PinHouse_CLOUD Length of output: 1066 🏁 Script executed: # Read the External Secrets configuration section
sed -n '178,262p' k8s-helm/platform-chart/values-dev.yamlRepository: PinHouse/PinHouse_CLOUD Length of output: 2402
Cert Manager의 DNS-01 Challenge와 External Secrets에서 GCP Secret Manager의 시크릿을 사용하기 위해 다음이 필수적으로 필요합니다:
이 사항들이 구성되지 않으면 Helm 배포 후 시크릿 동기화가 실패하고 애플리케이션이 정상 작동하지 않습니다. 🤖 Prompt for AI Agents |
||
|
|
||
| # 게이트웨이 | ||
| gateway: | ||
|
|
@@ -185,7 +185,7 @@ externalSecrets: | |
| spec: | ||
| provider: | ||
| gcpsm: | ||
| projectID: dev-pinhouse | ||
| projectID: dev-pinhouse-2 | ||
|
|
||
| secrets: | ||
| - name: backend-secret-kv | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,3 +5,4 @@ kind: Kustomization | |
| resources: | ||
| - frontend | ||
| - backend | ||
| - admin | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,3 +5,4 @@ kind: Kustomization | |
| resources: | ||
| - frontend | ||
| - backend | ||
| - admin | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: PinHouse/PinHouse_CLOUD
Length of output: 439
필수 해결: Artifact Registry 저장소를 찾을 수 없습니다
dev-pinhouse-2프로젝트asia-northeast3영역에서 다음 저장소들이 존재하지 않습니다:pinhouse-dev-admin(admin 이미지)pinhouse-dev-be(backend 이미지)pinhouse-dev-fe(frontend 이미지)배포 시 이미지 풀이 실패하므로, Artifact Registry 저장소를 생성하고 이미지를 먼저 푸시한 후 배포를 진행해야 합니다.
🤖 Prompt for AI Agents