Set AWS loadbalancer scheme to internal when not selecting non internet-facing#1109
Conversation
|
@miclettej can you take a look as I'm fiddling in the frontend without a real clue what I'm doing again. |
|
Cluster Generation A/B Results: |
ef5f5e9 to
0f73151
Compare
|
Cluster Generation A/B Results: |
Signed-off-by: Naadir Jeewa <jeewan@vmware.com>
0f73151 to
f9fc71d
Compare
|
Cluster Generation A/B Results: |
miclettej
left a comment
There was a problem hiding this comment.
UI change looks good. Thank you for taking care of this.
Signed-off-by: Naadir Jeewa <jeewan@vmware.com>
f9fc71d to
ee21da5
Compare
|
Tested locally, ready for merge. |
|
Cluster Generation A/B Results: |
What this PR does / why we need it
Which issue(s) this PR fixes
Fixes #
This programatically encodes the workaround for the "This is a non-internet facing VPC" option not working in https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/1.3/vmware-tanzu-kubernetes-grid-13/GUID-mgmt-clusters-airgapped-environments.html#step-5-initialize-tanzu-kubernetes-grid-9
Describe testing done for PR
Tested created clusters via UI and config file with and without internet facing.
Release note
PR Checklist
Additional information
Special notes for your reviewer
I had to include a fixup to the Makefile to generate the OpenAPI client on Fedora with SELinux enabled.