Skip to content
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

Charts[GKE-BUG] Allow the chart to be deployed with different release-name #388

Closed
Tracked by #368
leninmehedy opened this issue Oct 6, 2023 · 3 comments · Fixed by #412
Closed
Tracked by #368

Charts[GKE-BUG] Allow the chart to be deployed with different release-name #388

leninmehedy opened this issue Oct 6, 2023 · 3 comments · Fixed by #412
Assignees
Labels

Comments

@leninmehedy
Copy link
Member

leninmehedy commented Oct 6, 2023

Currently it assumes that the helm chart is deployed with release name fst. However, we should be able to override this with env variable RELEASE_NAME. For example,

make deploy-network RELEASE_NAME=fst2

@github-project-automation github-project-automation bot moved this to 🆕 New in FST Suite Oct 6, 2023
@leninmehedy leninmehedy self-assigned this Oct 6, 2023
@leninmehedy leninmehedy changed the title Charts[GKE-BUG] Allow the same chat to be deployed multiple times with different release-name Charts[GKE-BUG] Allow the chart to be deployed with different release-name Oct 6, 2023
@leninmehedy
Copy link
Member Author

#410 blocks this

@leninmehedy
Copy link
Member Author

Fix is added here: hashgraph/hedera-mirror-node-explorer#726

@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in FST Suite Oct 16, 2023
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.12.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment