Fix resources isues 8
This commit is contained in:
@@ -56,3 +56,5 @@ spec:
|
||||
# See infrastructure/cicd/gitea/values.yaml for ingress configuration
|
||||
# NOTE: Mail ingress is deployed separately via mailu-helm resource
|
||||
# to avoid 503 errors when Mailu is not running
|
||||
# NOTE: Monitoring ingress is deployed separately via SigNoz Helm chart
|
||||
# See infrastructure/monitoring/signoz/signoz-values-prod.yaml for monitoring configuration
|
||||
|
||||
@@ -25,3 +25,5 @@ patches:
|
||||
value: "https://localhost,https://localhost:3000,https://localhost:3001,https://127.0.0.1,https://127.0.0.1:3000,https://127.0.0.1:3001,https://bakery-ia.local,https://registry.bakery-ia.local,https://gitea.bakery-ia.local,http://localhost,http://localhost:3000,http://localhost:3001,http://127.0.0.1,http://127.0.0.1:3000"
|
||||
# NOTE: Gitea and Registry ingresses are managed by Gitea Helm chart (infrastructure/cicd/gitea/values.yaml)
|
||||
# NOTE: Mail ingress (mail.bakery-ia.dev) is deployed separately via mailu-helm Tilt resource
|
||||
# NOTE: Monitoring ingress (monitoring.bakery-ia.local) is deployed separately via SigNoz Helm chart
|
||||
# See infrastructure/monitoring/signoz/signoz-values-dev.yaml for monitoring configuration
|
||||
|
||||
@@ -37,4 +37,6 @@ patches:
|
||||
value: "http01"
|
||||
# NOTE: Gitea and Registry ingresses are managed by Gitea Helm chart
|
||||
# See infrastructure/cicd/gitea/values-prod.yaml for production ingress configuration
|
||||
# NOTE: mail.bakewise.ai is handled by separate mailu ingress
|
||||
# NOTE: mail.bakewise.ai is handled by separate mailu ingress
|
||||
# NOTE: monitoring.bakewise.ai is handled by separate SigNoz ingress
|
||||
# See infrastructure/monitoring/signoz/signoz-values-prod.yaml for monitoring ingress configuration
|
||||
Reference in New Issue
Block a user