uselagoon / uselagoon/remote-controller
harbor credential rotation fails on occasion
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 2
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 5
Description
There is a condition where the remote-controller is performing the harbor credential rotation where it appears to succeed but then the secret doesn't pull the images correctly.
unsure of what the cause of the issue is, will require more investigation to determine where the problem is occurring.
logs indicate that the credentials are rotated, but for some reason they fail to authenticate with harbor
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the harbor credential rotation in the remote-controller and compare its logs with the subsequent image-pull authentication failure. Trace the rotation path using the reported logs to identify where the updated credentials stop being accepted. Done means the intermittent failure is isolated and a verified fix or a more precise failing component is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100