hashicorp / hashicorp/vault-helm
Access denied to helm.releases.hashicorp.com
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 898
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
**Describe the bug**
Our IP address is: `95.47.238.105` and we are located in `Uzbekistan (UZ), Tashkent`. We faced with problem to pull releases from
helm.releases.hashicorp.com. Information about our IP pull: https://apps.db.ripe.net/db-web-ui/query?searchtext=95.47.238.105
Could you please add our address to white list.
**To Reproduce**
Steps to reproduce the behavior:
1. Install chart
2. Run vault command
3. See error (vault logs, etc.)
Other useful info to include: vault pod logs, `kubectl describe statefulset vault` and `kubectl get statefulset vault -o yaml` output
**Expected behavior**
A clear and concise description of what you expected to happen.
**Environment**
* Kubernetes version:
* Distribution or cloud vendor (OpenShift, EKS, GKE, AKS, etc.):
* Other configuration options or runtime services (istio, etc.):
* vault-helm version:
Chart values:
```yaml
failed to fetch Helm repository index: failed to cache index to temporary file: failed to fetch https://helm.releases.hashicorp.com/index.yaml : 403 Forbidden
```
**Additional context**
Add any other context about the problem here.
Contributor guide
Research direction
Start by investigating the 403 response when fetching https://helm.releases.hashicorp.com/index.yaml and reviewing the reported IP address and RIPE information. The issue provides no chart version, Kubernetes environment, logs, or repository files; done would require determining whether access can be changed and confirming that Helm can fetch the repository index.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100