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
Use custom DNS server without adding it to system #36
Use custom DNS server without adding it to system #36
Commits on May 13, 2022
Commits on May 14, 2022
-
SIVT 1.2 release - Initial commit
Signed-off-by: Sunil Shetty <sunilsh@vmware.com>
Commits on May 16, 2022
-
SIVT release 1.2 marketplace update link
Signed-off-by: Sunil Shetty <sunilsh@vmware.com> (cherry picked from commit 3aca59e)
Commits on May 19, 2022
-
Dependabot alert fixes on package-lock.json (vmware-tanzu#28)
Signed-off-by: Rashi Khandelwal <rashik@vmware.com>
-
Fix link to Azure reference architecture (vmware-tanzu#22)
Signed-off-by: Ian Zink <izink@pivotal.io>
-
Fixing Documentation issues (vmware-tanzu#31)
Signed-off-by: Tasmiya Bano <tbano@tbano-a01.vmware.com> Co-authored-by: Tasmiya Bano <tbano@tbano-a01.vmware.com>
Commits on May 25, 2022
-
Use custom DNS server without adding it to system
Currently, SIVT will fail if the DNS resolver it was configured with cannot resolve custom Avi FQDNs. This might not work for customers who want to use FQDNs that will only live on the DNS resolver that they provided to the UI. This commit fixes that by using `dns.resolver` and monkey-patching `urllib.connection.create_connection` to ensure that the resolver that the user provided is used during environment turn up. Signed-off-by: Carlos Nunez <ncarlos@vmware.com>
Commits on May 26, 2022
-
Ensure that patched create_connection is used
Signed-off-by: Carlos Nunez <ncarlos@vmware.com>
Commits on May 27, 2022
-
* Fix merge conflicts Signed-off-by: srinivasme21 <srinivasme@vmware.com> * Review and fix typos and formatting Signed-off-by: srinivasme21 <srinivasme@vmware.com> * Fix format Signed-off-by: srinivasme21 <srinivasme@vmware.com> * Update staging URLs to production Signed-off-by: srinivasme21 <srinivasme@vmware.com> * Fix release version in title Signed-off-by: srinivasme21 <srinivasme@vmware.com>
Commits on May 30, 2022
-
AWS Documentation fix for vmware-tanzu#20 (vmware-tanzu#33)
* Fixing Documentation issues Signed-off-by: Tasmiya Bano <tbano@tbano-a01.vmware.com> * Docmentation fix for AWS Signed-off-by: Tasmiya Bano <tbano@tbano-a01.vmware.com> Co-authored-by: Tasmiya Bano <tbano@tbano-a01.vmware.com>
-
Fix 'int is not iterable' during TMC validation (vmware-tanzu#37)
Users get the message above when TMC token validation fails. This pull request fixes that. Signed-off-by: Carlos Nunez <ncarlos@vmware.com>
Commits on May 31, 2022
-
Adding github workflows: SpecllCheck and LinkCheck
Signed-off-by: Sunil Shetty <sunilsh@vmware.com>
-
Implemented Github actions Spellcheck, Links-check, Orphaned-content …
…check, wrapped-link check Signed-off-by: Sunil Shetty <sunilsh@vmware.com>
-
Signed-Off-By: Carlos Nunez <ncarlos@vmware.com>
-
fix: propagate custom dns to kind bootstrapper
The bootstrapping cluster forwards `/etc/resolv.conf` to CoreDNS, which prevents FQDNs with domains in the custom DNS servers from resolving. This fixes that. Signed-off-by: Carlos Nunez <ncarlos@vmware.com>
-
fix: restore old /etc/resolv.conf before doing anything
Signed-off-by: Carlos Nunez <ncarlos@vmware.com>
-
Signed-off-by: Carlos Nunez <ncarlos@vmware.com>
-
fix: send in servers literally
Signed-off-by: Carlos Nunez <ncarlos@vmware.com>
Commits on Jun 1, 2022
-
Signed-off-by: Carlos Nunez <ncarlos@vmware.com>
-
Merge remote-tracking branch 'upstream/main' into fix/use-custom-dns-…
…server Signed-off-by: Carlos Nunez <ncarlos@vmware.com>