Upgrade Headlamp version to 0.15.1

[yolossn]

No description provided.

[linux-foundation-easycla]

• ❌ The commit (c13a64b). This user is missing the User's ID, preventing the EasyCLA check. Consult GitHub Help to resolve.For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

Hi @yolossn. 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 /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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: yolossn
Once this PR has been reviewed and has the lgtm label, please assign afbjorklund for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[minikube-bot]

Can one of the admins verify this patch?

[spowelljr]

CLA needs to be signed

[afbjorklund]

What is up with all the headlamp spam ?

https://github.com/kubernetes/minikube/pulls?q=is%3Apr+headlamp

• Upgrade Headlamp version to 0.15.0 #15817

[yolossn]

What is up with all the headlamp spam ?

Sorry for the inconvenience, We recently had our organization moved from kinvolk to headlamp-k8s and one of the Github Actions setup to automate the process of creating the Update PR picked up the wrong configurations. We have fixed it and will make sure it works properly going forward. The same has been mentioned here. Once again sorry for the spam.

[yolossn]

@spowelljr I signed the CLA multiple times but the status is not updated. Is there something that I am missing?

[spowelljr]

/check-cla

[spowelljr]

Your commit email is with sannagaraj@microsoft.com but your commit on #15869 is using nssvlr@gmail.com so I'm assuming you signed the CLA with the latter. If you could change the commit to use the email you signed the CLA with it should resolve.

[yolossn]

Your commit email is with sannagaraj@microsoft.com but your commit on #15869 is using nssvlr@gmail.com so I'm assuming you signed the CLA with the latter. If you could change the commit to use the email you signed the CLA with it should resolve.

I signed the CLA with both the emails but still faced the same issue. I tried changing both the commits to use the same commit email sannagaraj@microsoft.com and still CLA fails on this one and passes on #15869.

[spowelljr]

I'm not too sure, if you make another branch and commit with the microsoft email and then create a PR as a test I'd be curious if it passes or not. If it does maybe closing this PR and reopening could resolve it. If it doesn't then there seems there would be an issue with the microsoft email and the CLA check.

[yolossn]

I'm not too sure, if you make another branch and commit with the microsoft email and then create a PR as a test I'd be curious if it passes or not. If it does maybe closing this PR and reopening could resolve it. If it doesn't then there seems there would be an issue with the microsoft email and the CLA check.

Thanks for the pointer, I created a new PR as you suggested and the CLA passed, so Ill close this PR and open a new one.

[yolossn]

Opened a new PR for the same.