Closed shlomibendavid closed 8 months ago
Hi @shlomibendavid 👋
Without having access to the source code repository, we may not be able to verify the ownership of the k8s-ssh
software. Publishing the source is not a requirement at all, but usually when it's not available the publishing organization provides some other links that can help us with the verification process.
Hi Sergio,
Thanks for your email. You can verify it from the following URL: https://github.com/shlomibendavid/helm-charts In this URL, you can find the package tarball.
BR, Shlomi Ben-David
On Mon, Mar 4, 2024 at 3:58 AM Sergio Castaño Arteaga < @.***> wrote:
Hi @shlomibendavid https://github.com/shlomibendavid 👋
Without having access to the source code repository, we may not be able to verify the ownership of the k8s-ssh software. Publishing the source is not a requirement at all, but usually when it's not available the publishing organization provides some other links that can help us with the verification process.
— Reply to this email directly, view it on GitHub https://github.com/artifacthub/hub/issues/3680#issuecomment-1976051349, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEDX276AMFAEOBK3APU6XJ3YWQZUPAVCNFSM6AAAAABECXDXJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZWGA2TCMZUHE . You are receiving this because you were mentioned.Message ID: @.***>
Hi!
But that's just the chart :)
Please remember that to mark a chart as official, the publisher must own the software the chart relies on (in this case, the k8s-ssh
software, which I guess lives in the private repo you linked). In the chart we can only see a reference to a container image, but nothing else that allows us to verify that the software on that image is owned by you.
Hope I've explained myself better this time 😇
Hi Sergio,
There is a simple bash script (entrypoint.sh) in my image that operates. The image is exposed widely, and you can download it (I'm managing it; a screenshot is attached):
docker pull shlomibendavid/k8s-ssh:0304240306
You can check the script and see that I'm the author.
Hope that it's ok... else... I will appreciate your guidance for other options.
Thanks in advance, Shlomi Ben-David
On Mon, Mar 4, 2024 at 10:25 AM Sergio Castaño Arteaga < @.***> wrote:
Hi!
But that's just the chart :)
Please remember that to mark a chart as official, the publisher must own the software the chart relies on (in this case, the k8s-ssh software, which I guess lives in the private repo you linked). In the chart we can only see a reference to a container image, but nothing else that allows us to verify that the software on that image is owned by you.
Hope I've explained myself better this time 😇
— Reply to this email directly, view it on GitHub https://github.com/artifacthub/hub/issues/3680#issuecomment-1976837429, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEDX272MCMZFJ5KZ3P5MK2TYWSG6XAVCNFSM6AAAAABECXDXJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZWHAZTONBSHE . You are receiving this because you were mentioned.Message ID: @.***>
That's ok, thanks, I've just taken a look at it 🙂
The chart is now marked as official, you should see it in a few minutes!
In Artifact Hub, the
official
status means that the publisher owns the software a package primarily focuses on. If we consider the example of a chart used to install Consul, to obtain theofficial
status the publisher should be the owner of the Consul software (HashiCorp in this case), not just the chart. Similarly, a Tekton task used to perform operations on Google Cloud would need to be published by Google to be marked asofficial
. In the case of a MySQL operator, only one published by MySQL/Oracle would be consideredofficial
.The
official
status can be granted at the repository or package level. When it is granted for a repository, all packages available on it will display theofficial
badge, so all packages in the repository must be official. If only some of the packages in your repository are official, please list them in theOfficial packages
field below.artifacthub.io
): shlomibendavidBefore applying for this status, please make sure your repository complies with the following requirements:
README.md
file with some documentation that can be displayed on Artifact Hub.