Feature: Add Helm Chart to ArtifactHub.io

[Chili-Man]

Is your feature request related to a problem? Please describe.
Make this helm chart more discoverable.

Describe the solution you'd like in detail
By integrating with Artifacthub.io, it will make the Helm chart more easy to discover

Describe alternatives you've considered
I found my way through here after some searching

Additional context

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[wongma7]

/lifecycle frozen

still relevant

[krmichel]

/assign

[krmichel]

This is waiting on information for creating the organization on artifacthub.io. They require a name for the org and can optionally have display name, home URL, and description. @ayberk indicated that he would follow up on obtaining the information.

[pierluigilenoci]

Has anything moved forward around here? ❤️

[krmichel]

I am still waiting for the information that is needed for setting up the org.

[pierluigilenoci]

@ayberk could you please follow up on this?

[pierluigilenoci]

@wongma7 @krmichel @nirmalaagash could you please take a look?

[pierluigilenoci]

@krmichel any news?

[krmichel]

I haven't received any information from project owners as to the information that would be needed for artifacthub.io

[pierluigilenoci]

@krmichel maybe make sense to move the chart here: https://github.com/aws/eks-charts
In this way, the chart would be together with the others from AWS and would automatically be on Artifactory. 😉

[pierluigilenoci]

Or you can ask @jaypipes and @kishorj how to do it. 😛

[jaypipes]

I'm sad to say I actually didn't know anything about artifacthub.io until I saw @pierluigilenoci's comment this morning. :(

It looks like a cool thing that we should definitely publish Helm charts to! Even if just as a mirror from source artifact repositories either on Github Pages or ECR Public.

I agree that a good solution (if @wongma7 is OK with it) is to sync the aws-ebs-csi-driver Helm chart contents from this source code repository into the github.com/aws/eks-charts repository. There is a sync script in the AWS node termination handler project and it works pretty well.

/cc @bwagner5

As an aside, I found a Helm chart called "aws-ebs-csi-driver" from particle.io listed on ArtifactHub.io:

https://artifacthub.io/packages/helm/particuleio/aws-ebs-csi-driver

We may want/need to reach out to particle.io after getting aws-ebs-csi-driver into eks-charts to make sure that there isn't any confusion when two identically-named Helm charts are eventually listed on ArtifactHub.io...

[pierluigilenoci]

@jaypipes ArtifactHub is a public archive where everyone can publish, there is little to do. However, consider that in the case of homonymy it is clearly written, for each chart, to which organization it belongs.

Eg:

Or in the specific case of AWS...

Official (with even the logo and GitHub org):

External:

[pierluigilenoci]

@jaypipes any news about this?

[jaypipes]

@jaypipes any news about this?

@pierluigilenoci apologies I have no news on this. I need to chat with @wongma7 about getting the Helm chart mirrored into the eks-charts repo.

[pierluigilenoci]

/remove-lifecycle frozen

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[pierluigilenoci]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[pierluigilenoci]

/remove-lifecycle stale

[omidraha]

Is it published to artifacthub.io?

I want to install aws-ebs-csi-driver with Helm and Pulumi , and I want to know available parameters:

csi = kubernetes.helm.v3.Release(
        f"aws-ebs-csi-driver{DEPLOY_NAME_PREFIX}",
        kubernetes.helm.v3.ReleaseArgs(
            chart="aws-ebs-csi-driver",
            version="2.20.0",
            repository_opts=kubernetes.helm.v3.RepositoryOptsArgs(
                repo="https://kubernetes-sigs.github.io/aws-ebs-csi-driver"
            ),
            namespace=namespace.metadata.name,
            values={
                "logLevel": "debug",
                "replicaCount": "1",
                "region": "us-west-2",
            },
        ),
        pulumi.ResourceOptions(
            provider=provider,
            parent=namespace,
        )
    )

#1057

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[pierluigilenoci]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[pierluigilenoci]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[pierluigilenoci]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[pierluigilenoci]

/remove-lifecycle stale

[ElijahQuinones]

Hi @pierluigilenoci,

Looking into this I found that the EBS CSI Driver has been listed: https://artifacthub.io/packages/helm/aws-ebs-csi-driver/aws-ebs-csi-driver is there any specific addtional request that is keeping this issue open ?

[pierluigilenoci]

@ElijahQuinones This is not official. It is published by Levi Hoover, who I have no idea who he is.
There are five charts listed, but none of them is official. https://artifacthub.io/packages/search?ts_query_web=aws-ebs-csi-driver
Ref: #586 (comment)