File: charts/preview-router/values.yaml:10
repository: 178674732984.dkr.ecr.us-east-1.amazonaws.com/preview-routerIssue: Hardcoded internal ECR account ID
Fix: Should use global.registry.url pattern
File: charts/preview-router/values.yaml:31-32
fallbackUrl: "https://judge.testifysec-demo.xyz/"
domainSuffix: "preview.testifysec-demo.xyz"Issue: Hardcoded demo domain
Fix: Should use global.domain pattern
Files: Multiple (60, 66, 176)
- host: login.testifysec.localhost
kratosBrowserUrl: "http://kratos.testifysec.localhost"Issue: Hardcoded localhost domain Fix: Should be configurable from parent chart's domain setting
Files: Multiple (66, 77, 92)
- host: "judge.testifysec.localhost"Issue: Hardcoded localhost domain Fix: Should use ingress.hosts pattern from parent
Files: Multiple (121, 128, 207-271, 309)
base_url: https://kratos.testifysec.localhost
ui_url: https://login.testifysec.localhost/*
domain: testifysec.localhostIssue: Extensive hardcoded localhost domains Fix: Should template from global.domain
Files: Multiple (30, 238, 275, 295-299, 437, 458, 474, 476)
domain: testifysec-demo.xyz
url: "https://login.testifysec-demo.xyz/login"
issuer: https://dex.testifysec-demo.xyzIssue: Demo domain used as default Fix: Should have empty/generic default or use localhost
File: charts/archivista/values.yaml:96
- host: archivista.testifysec.localhostIssue: Hardcoded localhost domain Fix: Should use parent domain setting
File: charts/judge-api/values.yaml:136
- host: judge-api.testifysec.localhostIssue: Hardcoded localhost domain Fix: Should use parent domain setting
Files: fulcio, dex, tsa, dapr Chart.yaml dependencies
image: gcr.io/projectsigstore/fulcio@sha256:...
image: ghcr.io/dexidp/dex:v2.39.0
registry: ghcr.io/daprStatus: ✅ OK - These are legitimate upstream public registries
Files: kratos, archivista values.yaml
registry: YOUR_ACCOUNT_ID.dkr.ecr.us-east-1.amazonaws.comStatus: ✅ OK - Clear placeholders for documentation
File: charts/judge/values.yaml:111 (comment)
# - Account: 709825985650 (AWS Marketplace - hardcoded)Status: ✅ OK - Official AWS Marketplace account number
Files:
charts/preview-router/test/*charts/preview-router/examples/*charts/judge/demo-values.yamlcharts/judge/tests/*
Status: ✅ OK - Test/example files, not deployed
Strategy: Keep chart defaults unchanged, override at deployment level
All hardcoded values can be overridden through values files without modifying charts:
# values/production.yaml - Complete override example
global:
domain: mycompany.com
# 1. preview-router - Override ECR registry
preview-router:
image:
repository: YOUR_ACCOUNT_ID.dkr.ecr.us-east-1.amazonaws.com/preview-router
config:
fallbackUrl: "https://judge.mycompany.com/"
domainSuffix: "preview.mycompany.com"
# 2. kratos-selfservice-ui-node - Override ingress hosts
kratos-selfservice-ui-node:
ingress:
hosts:
- host: login.mycompany.com
paths:
- path: /
pathType: ImplementationSpecific
tls:
- hosts:
- login.mycompany.com
secretName: login-tls-secret
kratosBrowserUrl: "https://kratos.mycompany.com"
# 3. judge-web - Override ingress hosts
judge-web:
ingress:
hosts:
- host: "judge.mycompany.com"
tls:
- hosts:
- judge.mycompany.com
secretName: judge-tls-secret
# 4. kratos - Override all domain references
kratos:
ingress:
public:
hosts:
- host: kratos.mycompany.com
admin:
hosts:
- host: kratos-admin.mycompany.com
kratos:
config:
selfservice:
default_browser_return_url: https://judge.mycompany.com
allowed_return_urls:
- https://login.mycompany.com
- https://kratos.mycompany.com
- https://judge.mycompany.com
serve:
public:
base_url: https://kratos.mycompany.com
# 5. judge (parent) - Override demo domain
istio:
domain: mycompany.com
# 6. archivista - Override ingress host
archivista:
ingress:
hosts:
- host: archivista.mycompany.com
# 7. judge-api - Override ingress host
judge-api:
ingress:
hosts:
- host: judge-api.mycompany.comKey Pattern: Chart defaults provide localhost/demo values for quick starts. Production deployments override through values hierarchy.
Total Issues: 7 charts with hardcoded values Priority: Medium - Can be fully overridden at deployment level Impact: Users must provide comprehensive values overrides for production Solution: Document override pattern, keep chart defaults for development ease