-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Add support of Azure Blob storage to VFS #10258
Conversation
Hi @kenji-cloudnatix. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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. |
cd8f8d9
to
f9000f6
Compare
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a great start for merging the big PR. Just a few nits from me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the quick review, @hakman ! Changed AzureBlobPath
to implement HashHash
. Also inlined the cost as suggested.
3807d9d
to
4418dd5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review, @rifelpet !
This looks good to me but I'll wait for input from others before merging. We can bring it up at the Kops office hours tomorrow |
I am also OK with this. |
Thanks, both! How should I merge? Rebase and squash all the commits into one? |
We will have a short review on Friday during office hours and probably the final LGTM. |
The schema is "azureblob". azureClient provides two ways to set up credential. One approach is to use an account key stored in env var. This approach is used when accessing Blob from kops CLI. The second approach is to retrieve credentials from Instance Metadata Service. This works only when azureClient is created on a VM that has sufficient privilege to access a specified blob. This approach is used from nodeup, etcd-manager, etc.
8162578
to
4555c0b
Compare
Sounds good! Squashed. Will also join the office hour. |
Perfect. Thanks! |
/cc @justinsb |
} | ||
|
||
if u.Scheme != "azureblob" { | ||
return nil, fmt.Errorf("invalid Azure Blob schem: %q", p) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: scheme
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah thanks for catching! Will create a small PR to fix.
This looks great - so excited to see this - thanks @kenji-cloudnatix and all the reviewers :-) /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justinsb, kenji-cloudnatix 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 |
The schema is "azureblob".
azureClient provides two ways to set up credential. One approach is to
use an account key stored in env var. This approach is used when
accessing Blob from kops CLI. The second approach is to retrieve
credentials from Instance Metadata Service. This works only when
azureClient is created on a VM that has sufficient privilege to access
a specified blob. This approach is used from nodeup, etcd-manager,
etc.