You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 9, 2022. It is now read-only.
...mainly because of PDNs's requirement for load balancers that support UDP.
apparently, digital ocean LBs don't.
however, i was able to get kubeprod working on DO by
a) creating a new do.jsonnet manifest
b) removing PDS
c) using the digitalocean external-dns provider
this is currently a bit hacky becasuse modifying the generic config autogen shape is not supported by kubeprod's cli.
But actually, using your platform's native DNS routing service actually seems like a better solution anyway whenever possible.
@sameersbn is there any interest among maintainers in supporting DO as a first-class platform?
If so, i'm happy to submit a PR to support this
also happy to provide docs for how to get DO working with generic, but seems like a a bit of a hack without ability to add things (eg, DO API token) to the generic config autogen.json.
The text was updated successfully, but these errors were encountered:
...mainly because of PDNs's requirement for load balancers that support UDP.
apparently, digital ocean LBs don't.
however, i was able to get kubeprod working on DO by
a) creating a new do.jsonnet manifest
b) removing PDS
c) using the
digitalocean
external-dns providerthis is currently a bit hacky becasuse modifying the
generic
config autogen shape is not supported by kubeprod's cli.But actually, using your platform's native DNS routing service actually seems like a better solution anyway whenever possible.
@sameersbn is there any interest among maintainers in supporting DO as a first-class platform?
If so, i'm happy to submit a PR to support this
also happy to provide docs for how to get DO working with generic, but seems like a a bit of a hack without ability to add things (eg, DO API token) to the generic config autogen.json.
The text was updated successfully, but these errors were encountered: