Title: Switch to using the cert-manager DNS solver by default instead of HTTP · Issue #235 · commitdev/zero-aws-eks-stack · GitHub
Open Graph Title: Switch to using the cert-manager DNS solver by default instead of HTTP · Issue #235 · commitdev/zero-aws-eks-stack
X Title: Switch to using the cert-manager DNS solver by default instead of HTTP · Issue #235 · commitdev/zero-aws-eks-stack
Description: The HTTP solver is handy, and fast in most cases but I think we should move over to using the DNS validator by default. It can take longer sometimes due to DNS caching, but it is a bit less complex and there are things you just can’t do ...
Open Graph Description: The HTTP solver is handy, and fast in most cases but I think we should move over to using the DNS validator by default. It can take longer sometimes due to DNS caching, but it is a bit less complex...
X Description: The HTTP solver is handy, and fast in most cases but I think we should move over to using the DNS validator by default. It can take longer sometimes due to DNS caching, but it is a bit less complex...
Opengraph URL: https://github.com/commitdev/zero-aws-eks-stack/issues/235
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Switch to using the cert-manager DNS solver by default instead of HTTP","articleBody":"The HTTP solver is handy, and fast in most cases but I think we should move over to using the DNS validator by default. \r\nIt can take longer sometimes due to DNS caching, but it is a bit less complex and there are things you just can’t do with the HTTP version, like the chicken-and-egg situation if you need to migrate a domain but you can’t host the validator endpoint on the domain because you haven’t migrated it yet.\r\nThis should be easy enough because we already set up the DNS solver as a cluster issuer called `clusterissuer-letsencrypt-production-dns`. It would require changing the backend projects to use that by modifying the ingress annotation, and then need some testing to make sure it's working. If it works alright, the only change required to this repo would be updating the user-auth ingress to also use the DNS solver.","author":{"url":"https://github.com/bmonkman","@type":"Person","name":"bmonkman"},"datePublished":"2021-10-15T00:11:56.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/235/zero-aws-eks-stack/issues/235"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:c9cdd12e-afec-b0c3-39fc-e0a483e53d13 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B5BE:E60DD:227B5F3:2CEBD79:69818FDA |
| html-safe-nonce | 81cc40ad8d1167647dbe3a4b26a6ff8238aadc6de6545fc89d28af1ab20a9148 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCNUJFOkU2MEREOjIyN0I1RjM6MkNFQkQ3OTo2OTgxOEZEQSIsInZpc2l0b3JfaWQiOiIyOTA0ODEyOTU2NzQxMTExNzcwIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 4669faf121d152a49eb151a2a6de7de34c01bc1bb79a97c10fb49edd66930f55 |
| hovercard-subject-tag | issue:1026932186 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/commitdev/zero-aws-eks-stack/235/issue_layout |
| twitter:image | https://opengraph.githubassets.com/c2f47a8e4ca23b51c4059b0b32bf8af686b70f2417444a3a78733011a9c13cdd/commitdev/zero-aws-eks-stack/issues/235 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/c2f47a8e4ca23b51c4059b0b32bf8af686b70f2417444a3a78733011a9c13cdd/commitdev/zero-aws-eks-stack/issues/235 |
| og:image:alt | The HTTP solver is handy, and fast in most cases but I think we should move over to using the DNS validator by default. It can take longer sometimes due to DNS caching, but it is a bit less complex... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | bmonkman |
| hostname | github.com |
| expected-hostname | github.com |
| None | e137814e266030874fd2c86863529d0622b13889eeda04148c57654b6ea84ad6 |
| turbo-cache-control | no-preview |
| go-import | github.com/commitdev/zero-aws-eks-stack git https://github.com/commitdev/zero-aws-eks-stack.git |
| octolytics-dimension-user_id | 44272088 |
| octolytics-dimension-user_login | commitdev |
| octolytics-dimension-repository_id | 247773730 |
| octolytics-dimension-repository_nwo | commitdev/zero-aws-eks-stack |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 247773730 |
| octolytics-dimension-repository_network_root_nwo | commitdev/zero-aws-eks-stack |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | dd58d68a7813bbec9c91422c8c35f4af33832d70 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width