Open skitt opened 2 years ago
These are the steps that need to be followed.
kubectl label nodes <worker-node-name> "submariner.io/gateway=true" --overwrite
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>
az network nsg create --name <gw-nsg-name> --resource-group <rescource group>
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>
az network nic update -g <res-group> -n <gw-vm-nic> --network-security-group <gw-nsg-name>
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>
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.
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.
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.
It seems like we need a section of the website generally describing cloud prepare, what it does for all platforms.
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.
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.
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.
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.
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 onMachineSet
support). For non-OpenShift users, it would be useful to document whatcloud prepare
does on each platform, so that users can replicate its work manually.