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

Feature: Add Helm Chart to ArtifactHub.io #586

Open
Chili-Man opened this issue Oct 13, 2020 · 32 comments
Open

Feature: Add Helm Chart to ArtifactHub.io #586

Chili-Man opened this issue Oct 13, 2020 · 32 comments
Assignees

Comments

@Chili-Man
Copy link

Chili-Man commented Oct 13, 2020

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
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 11, 2021
@wongma7
Copy link
Contributor

wongma7 commented Jan 11, 2021

/lifecycle frozen

still relevant

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 11, 2021
@krmichel
Copy link
Contributor

/assign

@krmichel
Copy link
Contributor

krmichel commented Mar 26, 2021

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
Copy link

Has anything moved forward around here? ❤️

@krmichel
Copy link
Contributor

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

@pierluigilenoci
Copy link

@ayberk could you please follow up on this?

@pierluigilenoci
Copy link

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

@pierluigilenoci
Copy link

@krmichel any news?

@krmichel
Copy link
Contributor

krmichel commented Jan 5, 2022

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

@pierluigilenoci
Copy link

@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
Copy link

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

@jaypipes
Copy link

jaypipes commented Jan 6, 2022

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
Copy link

@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:

Screenshot 2022-01-06 at 17 38 08

Or in the specific case of AWS...

Official (with even the logo and GitHub org):
Screenshot 2022-01-06 at 17 36 21

External:
Screenshot 2022-01-06 at 17 36 03

@pierluigilenoci
Copy link

@jaypipes any news about this?

@jaypipes
Copy link

@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
Copy link

/remove-lifecycle frozen

@k8s-ci-robot k8s-ci-robot removed the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Dec 22, 2022
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 22, 2023
@pierluigilenoci
Copy link

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 22, 2023
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 20, 2023
@pierluigilenoci
Copy link

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 21, 2023
@omidraha
Copy link

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
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 25, 2024
@pierluigilenoci
Copy link

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 30, 2024
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 29, 2024
@pierluigilenoci
Copy link

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 30, 2024
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 29, 2024
@pierluigilenoci
Copy link

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 30, 2024
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 28, 2024
@pierluigilenoci
Copy link

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 28, 2024
@ElijahQuinones
Copy link
Member

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
Copy link

@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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants