Unable to pull down crds. Could it be due to the Cloudflare outages/glitches today?
- Dominant language
- Mustache
- Stars
- 1.3k
- Forks
- 1.1k
- Avg merge
- 22m
- Merged PRs (30d)
- 5
Description
**Describe the bug**
Unable to pull down crds. could it be due to the Cloudflare outages/glitches today?
**Steps to reproduce**
Tried both options. One with one forward slash e.g. `/crds`. And one as documented in the install docs with two slashes e.g. `//crds`
```
$ kubectl apply -k "github.com/aws/eks-charts/stable/aws-load-balancer-controller//crds?ref=master"
error: failed to run '/opt/homebrew/bin/git fetch --depth=1 https://github.com/aws/eks-charts/stable/aws-load-balancer-controller master': remote: Not Found
fatal: repository 'https://github.com/aws/eks-charts/stable/aws-load-balancer-controller/' not found
: exit status 128
$ kubectl apply -k "github.com/aws/eks-charts/stable/aws-load-balancer-controller/crds?ref=master"
error: hit 27s timeout running '/opt/homebrew/bin/git fetch --depth=1 https://github.com/aws/eks-charts master'
```
**Expected outcome**
crds should be applied. has been working up to yesterday. failed when tried today.
**Environment**
* Chart name: aws-load-balancer-controller
* Chart version: what's ever on the master branch
* Kubernetes version: 1.33
* Using EKS (yes/no), if so version? Yes, AWS EKS
**Additional Context**:
Contributor guide
Research direction
Begin with the two kubectl apply -k commands and compare their git fetch targets and timeout behavior. Check whether the aws-load-balancer-controller path and master reference are reachable, then inspect the install documentation referenced in the report. Done means determining why the CRDs cannot be fetched and recording the supported outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, git, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100