Add --kubernetes flag to make dapr invoke cmd support kubernetes

[imneov]

Description

Support the invoke cmd on kubernetes mode.

The process is similar:

1. Get the Pod corresponding to the App
2. Complete the specific communication through the SubResource("proxy") of RESTClient
3. Direct access to App's AppPort port or access to daprd's HttpPort port

                                      +-----------------+
                                      |                 |
                     AppPort          | +-------------+ |
         +----------------------------> |    APP      | |
  +----------+                        | +-------------+ |
  | dapr cli |                        |                 |
  +----------+                        | +-------------+ |
         +----------------------------> |    Daprd    | |
                    HttpPort          | +-------------+ |
                                      |                 |
                                      |            pod  |
                                      +-----------------+

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #[436] #[848]

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation

[tanvigour]

Can we add test case for this?

[imneov]

Can we add test case for this?

Sorry, just saw the reply.

Thank you tanvigour for review. I wrote part of the test code. There may be problems with code style or edge cases. Please review.

Welcome to add test cases.

[imneov]

There is a problem with using proxy to access the HttpPort, mainly because the address that daprd listens to is 127.0.0.1, and the proxy cannot access this port.

So now our project(tkeel-io/cli#74) uses portforward for invoke. The basic process is as follows:

1. Get the Pod corresponding to the App
2. Build a tunnel between the local and target pod through RESTClient's SubResource("portforward")
3. Access daprd's HttpPort port through the local tunnel port

This part of the implementation needs to modify portforward.go to implement random ports (#863).

[mukundansundar]

@imneov Can you signoff on your commits? https://github.com/dapr/cli/blob/master/CONTRIBUTING.md#developer-certificate-of-origin-signing-your-work

[mukundansundar]

@imneov Can you sign off all your commits ? https://github.com/dapr/cli/blob/master/CONTRIBUTING.md#developer-certificate-of-origin-signing-your-work

[mukundansundar]

@imneov Can you fix conflicts in the PR?

[imneov]

@imneov Can you fix conflicts in the PR?

Yes, I fix it.

[mukundansundar]

Thanks for the changes ... We will try to review this soon ...

[imneov]

@pravinpushkar HI~ Is there anything else I need to do?

[pravinpushkar]

@imneov Please fix the small lint issue. PR looks fine. We need to update this here also to be in sync - https://docs.dapr.io/reference/cli/dapr-invoke/

Do I need to submit a PR for docs?

Yes, If not done already then please create a doc issue and PR and link it here.
I have triggered the PR checks let's see.

[imneov]

Support the invoke cmd on kubernetes mode.

OK , Thanks for you reply. @pravinpushkar

There is doc issue(dapr/docs#2846) and PR(dapr/docs#2847)

[imneov]

@pravinpushkar Hi~ Is there any work I need to do?

[dapr-bot]

This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions!

[dapr-bot]

This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions!

[mukundansundar]

please add E2E for this feature.

[msfussell]

@mukundansundar - What is happening with this issue/PR?

[cicoyle]

@imneov - looks like there are some e2e failures, mind looking into and fixing those?
@dapr/maintainers-cli - looks like this PR has been open quite a while, we could use a review on this please :)

That being said, given the time constraint for this release, I will push this to the next release