aws-ebs-csi-driver
aws-ebs-csi-driver copied to clipboard
kubernetes-sigs
Feature: Add Helm Chart to ArtifactHub.io
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
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
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.
I am still waiting for the information that is needed for setting up the org.
I haven't received any information from project owners as to the information that would be needed for artifacthub.io
@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. 😉
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...
@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:
@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.
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
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
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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