Feature: automatically add {{ .Release.Name }}-server to DJANGO_ALLOWED_HOSTS
Open
enhancement
good first issue
- Dominant language
- Go Template
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
A `ClusterIP` service `{{ .Release.Name }}-server` is created for Kubernetes cluster internal network access to CUBE's HTTP API. Internal access is important for liveliness probes and testing. This only works if `DJANGO_ALLOWED_HOSTS` is properly configured to allow the host to be `{{ .Release.Name }}-server`.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the chart templates that define the ClusterIP service and DJANGO_ALLOWED_HOSTS, then render the Kubernetes manifests to verify that {{ .Release.Name }}-server is allowed as a host for internal API access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100