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

Helm Chart #169

Closed
wants to merge 1 commit into from
Closed

Conversation

shanesiebken
Copy link

Is this a bug fix or adding new feature?
New Feature.

Initial Helm Chart for driver components.

What is this PR about? / Why do we need it?
Starting point for work on #99

New PR because I'm fighting with git to get CLA signed on my account email address. Sorry for the churn 👎

What testing is done?
Deployed in staging cluster and confirmed output. More testing should be added.

More work should likely be done on this - but it captures a good portion of the "default" configuration of the driver components, as well as some of the more advanced functionality found in other charts - affinity, selectors, etc.

@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
  • If you have done the above and are still having issues with the CLA being reported as unsigned, please email the CNCF helpdesk: [email protected]

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Jan 3, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: shanesiebken
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: leakingtapan

If they are not already assigned, you can assign the PR to them by writing /assign @leakingtapan in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 3, 2019
@k8s-ci-robot
Copy link
Contributor

Hi @shanesiebken. Thanks for your PR.

I'm waiting for a kubernetes-sigs or kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 297

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 50.352%

Totals Coverage Status
Change from base Build 292: 0.0%
Covered Lines: 572
Relevant Lines: 1136

💛 - Coveralls

1 similar comment
@coveralls
Copy link

Pull Request Test Coverage Report for Build 297

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 50.352%

Totals Coverage Status
Change from base Build 292: 0.0%
Covered Lines: 572
Relevant Lines: 1136

💛 - Coveralls

@leakingtapan
Copy link
Contributor

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 3, 2019
@leakingtapan
Copy link
Contributor

/retest

@leakingtapan
Copy link
Contributor

leakingtapan commented Jan 15, 2019

@shanesiebken we are refactoring the manifest to align with recent upstream change. Please refer #171 This PR will need to be updated once the that is closed

@leakingtapan
Copy link
Contributor

/cc @dkoshkin

@k8s-ci-robot
Copy link
Contributor

@leakingtapan: GitHub didn't allow me to request PR reviews from the following users: dkoshkin.

Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @dkoshkin

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@shanesiebken
Copy link
Author

No problem @leakingtapan. Sorry for the delay on this - I haven't had time to figure out how in the world to contact the team at CNCF, as my login / account on their site is totally messed up.

@leakingtapan
Copy link
Contributor

@shanesiebken have you tried emailing: [email protected]

@shanesiebken
Copy link
Author

I haven't - I'll try that first thing in the morning! Thanks for the suggestion!

@leakingtapan
Copy link
Contributor

/retest

@k8s-ci-robot
Copy link
Contributor

@shanesiebken: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
pull-aws-ebs-csi-driver-e2e-single-az 2c05016 link /test pull-aws-ebs-csi-driver-e2e-single-az

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@shanesiebken
Copy link
Author

@leakingtapan Got my CLA signed! Not sure if there's anything more I need to do on here to get this PR to update, but let me know if there is.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Feb 20, 2019
@leakingtapan
Copy link
Contributor

leakingtapan commented Feb 21, 2019

@shanesiebken Congrats! Our features have been involved a lot lately. Reviewing the code again for new changes

appVersion: "1.0"
description: A Helm chart for the AWS EBS CSI Driver (https://github.com/kubernetes-sigs/aws-ebs-csi-driver)
name: aws-ebs-csi-driver
version: 0.1.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update to 0.2.0 since it is the latest.

@@ -0,0 +1,166 @@
apiVersion: v1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we combined attacher and provisioner manifest few weeks back. Could you combine helm template as well?

There are a bunches of changes made along with the combine. I think its easier to create new helm templates referring the existing manifests

node:
image:
repository: quay.io/k8scsi/driver-registrar
tag: v1.0-canary
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should use v1.0.1 for all the sidecars

@leakingtapan
Copy link
Contributor

/close

@shanesiebken please reopen if you got a chance to finish the comment

@k8s-ci-robot
Copy link
Contributor

@leakingtapan: Closed this PR.

In response to this:

/close

@shanesiebken please reopen if you got a chance to finish the comment

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

huffmanca pushed a commit to huffmanca/aws-ebs-csi-driver that referenced this pull request Sep 23, 2020
…ckerfile.openshift.rhel7-baseimages-to-mach-ocp-build-data-config

Bug 1878163: Updating Dockerfile.openshift.rhel7 baseimages to mach ocp-build-data config
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants