blueBlue0102 commented on PR #181:
URL: https://github.com/apache/yunikorn-release/pull/181#issuecomment-2313102416

   I appreciate your clarification about the intended use of the helm charts in 
the release repo. However, I believe this change could still be beneficial for 
newcomers to the project who might not yet be familiar with the intended 
workflow.
   
   As someone who was new to the project myself, I encountered confusion when 
exploring the yunikorn-release repo. I was puzzled by the fact that `helm 
install yunikorn yunikorn/yunikorn --namespace yunikorn` worked directly, while 
`helm install yunikorn helm-charts/yunikorn --namespace yunikorn` did not. The 
root cause of this issue was the non-existent `latest` tag.
   
   This experience aligns with the issue described in 
[YUNIKORN-2696](https://issues.apache.org/jira/browse/YUNIKORN-2696), which 
mentions "image tags are latest which is not available on docker hub". It seems 
I'm not alone in facing this challenge.
   
   While I now understand that these charts are primarily for development of 
the charts themselves, not all newcomers may immediately grasp this 
distinction. The proposed change aims to reduce confusion for those who, like 
myself, might explore the release repo as part of their initial project 
familiarization.
   
   By providing clearer indicators or placeholders for version tags, we can 
help prevent similar misunderstandings and smooth the onboarding process for 
new contributors, even if they're just exploring the repo structure.
   
   Do you think there might be value in adding a note to the README or the 
chart documentation to clarify the intended use of these charts? This could 
further help guide newcomers in the right direction.


-- 
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]

Reply via email to