- 25 Jun, 2017 1 commit
-
-
ideahitme authored
-
- 16 Jun, 2017 2 commits
-
-
Nick Jüttner authored
* CloudFlare Provider * updating glide * gofmt cloudflare_test.go * Unset envs to test NewCloudFlareProvider * More tests * fix(cloudflare): fix compiler errors resulting from merge * Typo * Undo vendor changes * decrease api calls, fix some nits * Cloudflare iteration (#2) * reduce the number of API calls * match by type and name for record id * improve coverage and fix the bug with suitable zone * tests failed due to wrong formatting * add cloudflare integration to the main * vendor cloudflare deps * fix cloudflare zone detection + tests * fix conflicting test function names
-
Nick Jüttner authored
* Initial Digital Ocean as a new provider * chore: vendor dependencies * Remove zone parameter from ApplyChanges and Records * fix(digitalocean): fix correct imports, unshadow a variable * fix(digitalocean): respect domain-filter if provided * add changes to digital ocean provider from PR review (#3) * fix tests and bugs in find suitable zones for digital ocean (#5) * tests failed due to wrong formatting * add digitalocean integration to the main and more tests * fix suitable zone for digital ocean
-
- 15 Jun, 2017 1 commit
-
-
Martin Linkhorst authored
* fix: Load all known Kubernetes Auth Plugins * chore: vendor CoreOS' oidc library
-
- 13 Jun, 2017 1 commit
-
-
Yerken authored
-
- 02 Jun, 2017 1 commit
-
-
Peter Huene authored
* vendor Azure Go SDK (#210) * vendor the Azure Go SDK and dependencies * add initial Azure DNS provider implementation (#210) * add 'azure' value to 'provider' command line option * add 'azure-config-file' command line option * add 'azure-resource-group' command line option * implement initial Azure DNS provider note: azure provider is not yet fully implemented (does not query for existing records). tests and documentation are forthcoming. * add a tutorial for the Azure provider (#210) * add tutorial for using ExternalDNS with Azure DNS * finish implementation of Azure DNS provider (#210) * implement the Records method for the Azure DNS provider * refactor Azure API interface for future tests (#210) * make Azure provider use an interface for future unit tests * add unit tests for the Azure provider (#210) * test retrieving Azure DNS records. * test updating and deleting Azure DNS records. * test dry run for the Azure provider (i.e. noop).
-
- 30 May, 2017 1 commit
-
-
Martin Linkhorst authored
-
- 29 May, 2017 1 commit
-
-
Ian Smith authored
* Expose inmemory provider to cli So we can test `--source fake` without needing to touch AWS/Google. * Add FakeSource `external-dns --provider inmemory --source fake --dry-run --once` OR `external-dns --provider aws --source fake --fqdn-template <hostname suffix> --dry-run --once` NB: `--fqdn-template` because otherwise we'll default to creating, e.g., `abcd.example.com`, which `--provider aws` filters out because you likely don't have a Zone for `example.com.` Could also be resolved by removing the need to use a real provider; the inmemory provider, perhaps, though it's not entirely hooked up. Closes kubernetes-incubator/external-dns#22 * Style feedback from Travis CI * Improve optionality of kubernetes client * ref(sources): refactor source registration and lookup to be lazy. * Revert "ref: refactor source registration/lookup to be lazily initialized"
-
- 22 May, 2017 1 commit
-
-
Martin Linkhorst authored
* chore: add instrumented HTTP client library * feat: add client-side metrics to outgoing HTTP clients
-
- 05 May, 2017 1 commit
-
-
Martin Linkhorst authored
* feat: add and use a deduplicating source * chore: add log entry when endpoint was deduplicated
-
- 27 Apr, 2017 1 commit
-
-
Martin Linkhorst authored
* feat(config): change defaults, switch flag processing to kingpin * chore: vendor kingpin as a dependency * feat(config): auto-detect cluster config from the environment * chore: clean up definition of flags * chore: sanitize flags even further * chore: update changelog with latest flags changes * fix(aws): fix messed up test name
-
- 26 Apr, 2017 1 commit
-
-
Yerken authored
* minor improvements to logging * chore(*): change log.Infoln to log.Info * fix: fix incorrect example code
-
- 25 Apr, 2017 1 commit
-
-
Martin Linkhorst authored
* feat(google): auto-detect and multiple zone support * chore: run gofmt with the simplified command * fix: pass desired domain to google provider * feat(google): correctly auto-detect records for sub-zones * chore: update changelog with support for multiple zones in google * fix(google): don't append traling dot to TXT records * ref(provider): extract hostname sanitization to general provider
-
- 18 Apr, 2017 2 commits
-
-
Yerken authored
* add --fqdn-template * add missing , * gofmt * no endpoint creation on empty fqdntemplate * improve test coverage * gofmt simple on service_test.go and ingress_test.go * import package order changed * gofmt * refactor to generate template in the source init * refactor for err handling * fix service tests * fix wrong check, check for priorities, mate > template * fix tests, check for controller annotation in the right place * add to changelog * add flag description, improve testing, reorganize imports * review changes: log the error, use text/template, change func interface
-
Henning Jacobs authored
-
- 13 Apr, 2017 1 commit
-
-
Martin Linkhorst authored
* feat(aws): support multiple hosted zones and automatic lookup * chore: run gofmt with the simplified command * fix(aws): add missing method from google provider * fix: remove superflous parameter from google provider * feat: make domain configurable via flag * fix(aws): remove unused constant * fix(aws): don't log actions that were filtered out * feat(aws): detect best possible zone to put dns entries in * fix(aws): log error instead of failing if a change batch fails * chore: update changelog with support for multiple zones
-
- 12 Apr, 2017 2 commits
-
-
Yerken authored
-
Martin Linkhorst authored
* feat(plan): allow plans to be parameterized via policies * fix(controller): set a policy in the controller tests * chore: allow go tip to fail * chore: update changelog to include policies * fix(plan): store a pointer to changes * fix(controller): don't get address of a pointer
-
- 11 Apr, 2017 1 commit
-
-
Yerken authored
* kickoff txt registry * fix inmemory dns provider to include recordtype info for validation * Merge master * fix ununsed variable in inmemory provider * add tests for records * add test for no prefix name formatter * implement apply changes with tests * add flag to enable txt registry * add txt registry to main * improve sort testing * filter out non-owned records * NewEndpoint(...) requires record type * use newendpoint in aws_test, fix tests * change suitable type implementation * fix the test for compatibility component * change inmemory provider to include recordtype and use suitable type * fix comments, CNAME should target hostname * name mapper do not use pointer on struct * txt prefix - just concatenate, remove spew, fix txt record label * allow TXT records as result from dns provider * add changelog * fix tests * TXT records need to be enclosed in double quotes
-
- 10 Apr, 2017 1 commit
-
-
Martin Linkhorst authored
-
- 07 Apr, 2017 2 commits
-
-
Yerken authored
* define registry interface * init in-memory registry * remove ununsed variable, added comments * add inmemory registry tests * introduce DNSRecord struct * use noop registry * remove zone from registry fields * replace provider with registry in controller * move noop registry interface check to test * remove ownerid from noop registry * fix: remove dangling empty line * return provider records directly with noop * adjust according to pr review * fix noop tests
-
Martin Linkhorst authored
* feat: expose basic go metrics via prometheus * chore: vendor dependencies * feat(metrics): combine healthz and metrics into single endpoint * ref(metrics): rename metrics port to address * docs(metrics): update changelog to include metrics feature * ref(metrics): consistently rename port to address
-
- 04 Apr, 2017 1 commit
-
-
Martin Linkhorst authored
-
- 17 Mar, 2017 1 commit
-
-
Martin Linkhorst authored
-
- 16 Mar, 2017 1 commit
-
-
Martin Linkhorst authored
* fix(dnsprovider): do not always initialize each DNS provider * fix(dnsprovider): fix unnecessary error return value * ref(dnsprovider): drop the store and use a simple switch for lookup
-
- 14 Mar, 2017 2 commits
-
-
Martin Linkhorst authored
-
Martin Linkhorst authored
-
- 13 Mar, 2017 1 commit
-
-
Martin Linkhorst authored
* ref(source): use constructor methods to create sources * fix: import and use missing package * fix(source): fix merge conflict with master branch
-
- 12 Mar, 2017 1 commit
-
-
Mikkel Oscar Lyderik Larsen authored
-
- 09 Mar, 2017 1 commit
-
-
Martin Linkhorst authored
-
- 07 Mar, 2017 1 commit
-
-
Martin Linkhorst authored
-
- 06 Mar, 2017 2 commits
-
-
Martin Linkhorst authored
-
Martin Linkhorst authored
-
- 02 Mar, 2017 2 commits
- 01 Mar, 2017 2 commits
-
-
Martin Linkhorst authored
* feat(google): add ability to apply changes generated from a plan * feat(controller): first implementation of controller * feat: allow to configure in-cluster and kubeconfig * fix(controller): call RunOnce at the right time and in a loop * feat(google): add dryRun attribute to Google DNS provider * fix: use hosted zone id instead of DNS name * fix(google): stupidly filter by A records for now * feat: allow specifying the google project and zone * feat: provide a dry-run flag which defaults to false * chore: vendor new dependencies * fix(config): fix failing tests for config object * ref(controller): return plain value of ApplyChanges * ref: simplify how to get a valid kubernetes client
-
Justin Santa Barbara authored
Types that we want to work using apimachinery typically go into pkg/apis/X, and the validation goes into pkg/apis/X/validation. We then add versions into e.g. pkg/apis/X/v1alpha1, but this feels premature at the moment. Changing this later is annoyingly difficult, especially in terms of validation and dependencies. We will want the apimachinery, so that we can configure from a configuration file that is versioned. Hopefully dns-controller won't end up so complicated that we will require it, but I think there is also value in following the "standard" patterns for controllers that are emerging from e.g. ingress. For a fairly simple example of an API, please consult https://github.com/kubernetes/kubernetes/tree/master/pkg/apis/certificates
-
- 21 Feb, 2017 3 commits