blueBlue0102 commented on PR #181: URL: https://github.com/apache/yunikorn-release/pull/181#issuecomment-2314606733
I fully understand that this project is not intended for end users or required for development setup. However, I believe there's still value in addressing this issue. New developers seeking to understand how YuniKorn is deployed in Kubernetes are likely to examine the helm charts in yunikorn-release, and may attempt to deploy using these charts directly. During my work on resolving [YUNIKORN-2626](https://issues.apache.org/jira/browse/YUNIKORN-2626) (my first issue with YuniKorn), which involved adding a flag in the helm chart to toggle the web UI container, I needed to test the installation locally. This process led me to spend time troubleshooting pod startup failures caused by the 'latest' tag. From my experience, the 'latest' tag appears to be a reasonable default, which caused some confusion. I believe future newcomers editing the helm charts might encounter similar issues. This aligns with the author of [YUNIKORN-2696](https://issues.apache.org/jira/browse/YUNIKORN-2696), who noted "image tags are latest which is not available on docker hub" - likely noticing the misleading nature of the 'latest' tag. Therefore, I maintain that even for a "tooling for creating a release", "meta-project", or "template", striving for an out-of-the-box experience would be beneficial. The proposed change only requires adjusting the default image tag value, a low-cost modification. To be clear, I'm not suggesting that this project should continually aim for an out-of-the-box experience. Rather, I believe we should at least prevent potential confusion caused by the 'latest' tag. While I respect the decision to close the PR, I hope this clarification helps illustrate the potential value of this small change in improving the experience for new contributors exploring the project structure. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
