Support skip x509 check in UI when deploying to vSphere#1090
Support skip x509 check in UI when deploying to vSphere#1090miclettej merged 2 commits intovmware-tanzu:mainfrom
Conversation
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
2bf82e7 to
240d942
Compare
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
...kg/web/src/app/views/landing/vsphere-wizard/provider-step/vsphere-provider-step.component.ts
Outdated
Show resolved
Hide resolved
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
...kg/web/src/app/views/landing/vsphere-wizard/provider-step/vsphere-provider-step.component.ts
Show resolved
Hide resolved
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
718242c to
560a5c9
Compare
|
Cluster Generation A/B Results: |
e54e5bb to
3e9b1d5
Compare
|
Cluster Generation A/B Results: |
Provides an option in the UI to skip x509 check in UI when deploying to vSphere
*Note: User may still set environment variable VSPHERE_INSECURE=true. This would return insecure: true during the getVsphereThumbprint REST call, and the UI will avoid displaying the SSL thumbprint verification regardless of the Skip Verification checkbox in the UI being checked or not.
Which issue(s) this PR fixes
Fixes #1028
Describe testing done for PR
Built and ran CLI locally, tested UI interaction of bypassing x509 check and using default behavior against vCenter testbed. Confirmed that UI is writing VSPHERE_INSECURE to config file.
Release note
PR Checklist
Additional information
Special notes for your reviewer