-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS
- Metaphor
app fails to pull due to image name mismatch
#1801
Comments
More context here: https://github.com//pull/1797#issuecomment-1705810767
|
Thanks for reporting this issue @alechp: someone will review @cameronraysmith's PR soon. |
Source of the issue from #1801 (comment) is due to the I fixed this by updating the fullChartPath parameter in
to You can see this matches the generated value: The actual fix would be to update the This would also address the subsequent failure in After doing this, release throws a 409:
|
The following manual changes gets Github Actions workflow to pass all the way through release:
To:
To:
Conclusion
|
There's an active discussion about this on the Slack community at https://kubefirst.slack.com/archives/C03U34WJ7FW/p1694539096211389 |
Status update from @claywd on slack: @johndietz working on this |
Status update; blocked pending v2.3.0: Will test again after #1832 is merged |
Confirmed Metaphor is working now (tested with kubefirst v2.3.5) CC: @jarededwards @fharper @cameronraysmith |
Which version of kubefirst are you using?
2.2.17
Which cloud provider?
AWS
Which installation type?
CLI
Which distributed Git provider?
GitHub
What is the issue?
Problem
ghcr.io/<GITHUB_ORG>/metaphor:hash
ghcr.io/<GITHUB_ORG>/metaphor/metaphor:hash
(note the duplicative metaphor)Similar to the GCP issue here: #1774, @cameronraysmith submitted a fix for AWS here: #1797
I believe @claywd is currently looking into this (screenshots below for context)
Additional context
Related issues
AWS
- Failing while configuring vault (StatefulSet timeout) #1788Code of Conduct
The text was updated successfully, but these errors were encountered: