We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.

Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist")

If this message is too spammy, please complain to ixdy.

Labelling this PR as size/XS

Have submitted my CLA using the correct email already.

This looks good. You need to have your email in your github account I think.

@brendandburns Yes, I have already add my email in my github account. And with CLA signed. Not sure what to do next?

@brendandburns How should I do next? Any suggestion?

@xinxiaogang I don't see your email when I look at your profile, so maybe it's not public?

I manually validate the CLA for this PR, but we should figure out why the automation doesn't see it.

Also you need to run:

hack/update-generated-docs.sh

@brendandburns I have my email configured in my profile as below:
xnxin@ebay.com Primary Public
Is this correct?

@xinxiaogang odd, when I look at https://github.com/xinxiaogang

I don't see your mail, but when I look at https://github.com/brendandburns

I see mine, so I think something must not be quite right?

@k8s-bot ok to test

@k8s-bot ok to test
@k8s-bot test this

pr builder appears to be missing, activating due to 'lgtm' label.

GCE e2e test build/test passed for commit 83df275.

• Build Log
• Test Artifacts
• Internal Jenkins Results

@k8s-bot unit test this please

Automatic merge from submit-queue