Skip to content
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

Document what cloud prepare does on each platform #801

Open
skitt opened this issue Jul 15, 2022 · 9 comments
Open

Document what cloud prepare does on each platform #801

skitt opened this issue Jul 15, 2022 · 9 comments
Labels
documentation Improvements or additions to documentation

Comments

@skitt
Copy link
Member

skitt commented Jul 15, 2022

subctl cloud prepare is typically strongly tied to OpenShift, and documented as only supported on OpenShift (e.g. at least on some platforms it relies on MachineSet support). For non-OpenShift users, it would be useful to document what cloud prepare does on each platform, so that users can replicate its work manually.

@aswinsuryan
Copy link
Contributor

aswinsuryan commented Jul 15, 2022

These are the steps that need to be followed.

  1. Tag a node as gateway node.

kubectl label nodes <worker-node-name> "submariner.io/gateway=true" --overwrite

  1. Create a public IP and assign it to the VM of the node that was tagged as g/w node
az network public-ip create --name <public-ip-name> --resource-group <res-group>
az network nic ip-config update --name <name>  --nic-name <gw-vm-nic> --resource-group <res-group>  --public-ip-address <public-ip-name>
  1. Create a network security group for submariner gateway

az network nsg create --name <gw-nsg-name> --resource-group <rescource group>

  1. Create NSG (network security groups) security rules on your Azure to open NAT traversal ports (by default 4500/UDP) Nat discovery port (by default 4490/UDP) metrics port (by default 8080/TCP) for Submariner. This needs to be created in both inbound and outbound directions.
az network nsg rule create --resource-group <res-group> \
--nsg-name <gw-nsg-name> --priority <priority> \
--name <name> --direction Inbound --access Allow \
--protocol <Protocol> --destination-port-ranges <ipsec-port>

az network nsg rule create --resource-group <res-group> \
--nsg-name <gw-nsg-name> --priority <priority> \
--name <name> --direction Outbound --access Allow \
--protocol <Protocol> --destination-port-ranges <ipsec-port>
  1. Attach the security group to the g/w VM interface

az network nic update -g <res-group> -n <gw-vm-nic> --network-security-group <gw-nsg-name>

  1. Create NSG (network security groups) security rules on your Azure to open VXLAN port (by default 4800/UDP) on the existing security groups that is associated with the worker and the master
  az network nsg rule create --resource-group <res-group> \
--nsg-name <nsg-name> --priority <priority> \
--name <name> --direction Inbound --access Allow \
--protocol <Protocol> --destination-port-ranges <ipsec-port>
az network nsg rule create --resource-group <res-group> \
--nsg-name <nsg-name> --priority <priority> \
--name <name> --direction Outbound --access Allow \
--protocol <Protocol> --destination-port-ranges <ipsec-port>

@stale
Copy link

stale bot commented Nov 12, 2022

This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Nov 12, 2022
@dfarrell07
Copy link
Member

dfarrell07 commented Nov 22, 2022

The dependency on MachineSet will go away when we have LoadBalancer mode and a different way to choose nodes with better networking perf, which is triaged to start 0.15.

@stale stale bot removed the wontfix This will not be worked on label Nov 22, 2022
@stale
Copy link

stale bot commented Apr 2, 2023

This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Apr 2, 2023
@dfarrell07 dfarrell07 added the documentation Improvements or additions to documentation label Apr 4, 2023
@stale stale bot removed the wontfix This will not be worked on label Apr 4, 2023
@dfarrell07
Copy link
Member

It seems like we need a section of the website generally describing cloud prepare, what it does for all platforms.

@stale
Copy link

stale bot commented Aug 12, 2023

This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Aug 12, 2023
@sridhargaddam sridhargaddam removed the wontfix This will not be worked on label Sep 14, 2023
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further
activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jan 13, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 21, 2024
@dfarrell07 dfarrell07 removed the stale label Jan 23, 2024
@dfarrell07 dfarrell07 reopened this Jan 23, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further
activity occurs. Thank you for your contributions.

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further
activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Sep 26, 2024
@maayanf24 maayanf24 removed the stale label Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: Backlog
Development

No branches or pull requests

5 participants