-
Notifications
You must be signed in to change notification settings - Fork 373
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
[Windows] Support run antrea-agent directly from scripts #1013
Conversation
Thanks for your PR. The following commands are available:
These commands can only be run by members of the vmware-tanzu organization. |
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Support read kubeconfig from file for antrea-agent apiserver. Which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
/test-all |
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Support read kubeconfig from file for antrea-agent apiserver. Which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Support read kubeconfig from file for antrea-agent apiserver. Which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
/test-all |
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Support read kubeconfig from file for antrea-agent apiserver. Which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Support read kubeconfig from file for antrea-agent apiserver. Which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Support read kubeconfig from file for antrea-agent apiserver. Which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Support read kubeconfig from file for antrea-agent apiserver. Which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Support read kubeconfig from file for antrea-agent apiserver. Which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
/test-all |
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Support read kubeconfig from file for antrea-agent apiserver. Which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
/test-all |
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Support read kubeconfig from file for antrea-agent apiserver. Which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
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.
Is there any plan to validate this script in CI?
``` | ||
mkdir c:\k\antrea | ||
cd c:\k\antrea | ||
curl.exe -LO https://raw.githubusercontent.com/vmware-tanzu/antrea/master/hack/windows/Start.ps1 |
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.
do you think we should have Start.ps1
in the release assets and that it should take care of pulling / starting the correct version of Antrea?
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.
Yes, I think it's a good advice.
I can update upload_release_assets.yaml
in next patch to add following files in assets:
- Start.ps1
- antrea-agent-windows-x86_64.exe
- antrea-cni-windows-x86_64.exe
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.
Sounds good. You can look at it in a follow-up patch.
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Support read kubeconfig from file for antrea-agent apiserver. Which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
Yes @antoninbas , I'm working with Zhecheng to add CI for the scripts. |
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Support read kubeconfig from file for antrea-agent apiserver. Which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
@jianjuns @antoninbas Do we need to support this workflow? If I understand, it requires access to worker node. The script will download and install Antrea and run it as process on the node, which is different than running Antrea as POD. Lets have a offline meeting to discuss this. ? |
Currently suportbundle/log collection is not supported if antrea-agent is run as process directly. And we also don't provide a specific script for upgrade. In my opinion, in consideration of the different requirements among different platforms, the scripts we provide is more like a template to guide how to run antrea-agent as process if antrea-agent Pod is not allowed. It's hard to cover all functions as we support for Pod management. The platforms which integrated with Antrea may need custmize thire own scripts/solution based on the scripts/functions we provide. Looing forward tto hear he ideas from Jianjun and Antonin. |
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.
In commit message:
Support read kubeconfig from file for antrea-agent apiserver.
Which is needed when antrea-agent is running as process.
Support -> Supports
Which -> which
I think process mode is not the recommended way. |
Actually AKS engine folks asked if we can remove wins dependency as they don't want to add lot of components on windows host. However, if wins dependency is must and adding a script is the only alternative, than I would prefer to reach out to them again and mention why wins is needed. We would prefer not to add antrea as a process. |
If that is the case, please talk to AKS guys again. Definitely I want not to support process mode. But on the other hand, I feel this PR has nothing wrong. We just document a manual way to run Antrea agent. Does not mean we commit anything. |
I agree with Jianjun. Let's hold off on adding additional support for this process mode though (e.g. support bundle). Maybe @ruicao93 can emphasize the limitations of this mode in the doc as well. |
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Supports read kubeconfig from file for antrea-agent apiserver, which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
Thanks for your PR. The following commands are available:
|
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Supports read kubeconfig from file for antrea-agent apiserver, which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Supports read kubeconfig from file for antrea-agent apiserver, which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
Done. |
Sure, I will add the limitations in doc. |
/test-all |
/test-windows-conformance |
1 similar comment
/test-windows-conformance |
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.
LGTM
) Currently Antrea runs antrea-agent and kube-proxy from management Pods. But there is still need to run these two components directly using scripts. This patch: - Adds scripts help to install and run antrea-agent and kube-proxy. - Supports read kubeconfig from file for antrea-agent apiserver, which is needed when antrea-agent is running as process. Signed-off-by: Rui Cao <rcao@vmware.com>
Currently Antrea runs antrea-agent and kube-proxy from management
Pods. But there is still need to run these two components directly
using scripts. This patch:
which is needed when antrea-agent is running as process.
Signed-off-by: Rui Cao rcao@vmware.com