- 21 Jan, 2020 1 commit
-
-
k.siemer authored
-
- 15 Jan, 2020 1 commit
-
-
Tariq Ibrahim authored
-
- 08 Jan, 2020 1 commit
-
-
Jaromir Vanek authored
-
- 06 Jan, 2020 1 commit
-
-
Tariq Ibrahim authored
-
- 28 Nov, 2019 1 commit
-
-
Tongyao Si authored
-
- 19 Nov, 2019 1 commit
-
-
saidst authored
-
- 02 Nov, 2019 1 commit
-
-
Vincent Desjardins authored
The parameter is google-batch-change-interval. Default value is 2s.
-
- 01 Nov, 2019 1 commit
-
-
Nick Jüttner authored
* Move into kubernetes-sigs organization * Disable labeler action for forks
-
- 31 Oct, 2019 1 commit
-
-
Vincent Desjardins authored
The parameter is google-batch-change-size. Default value is 1000.
-
- 22 Aug, 2019 1 commit
-
-
Corey O'Brien authored
-
- 19 Jul, 2019 1 commit
-
-
Jason-ZW authored
-
- 17 Jul, 2019 2 commits
-
-
Martin Linkhorst authored
-
xunpan authored
-
- 05 Jul, 2019 1 commit
-
-
Jonas Michel authored
-
- 01 Jul, 2019 1 commit
-
-
Dave Grizzanti authored
-
- 27 Jun, 2019 1 commit
-
-
Dave Grizzanti authored
-
- 22 May, 2019 1 commit
-
-
Curtis Mattoon authored
-
- 10 May, 2019 3 commits
-
-
Dave Grizzanti authored
-
Dave Grizzanti authored
-
Dave Grizzanti authored
-
- 28 Apr, 2019 1 commit
-
-
Reinier Schoof authored
-
- 26 Apr, 2019 1 commit
-
-
mburtless authored
-
- 22 Apr, 2019 2 commits
- 31 Mar, 2019 1 commit
-
-
David Schneider authored
The number of objects returned by the infoblox api is limited to 1000 objects (see https://ipam.illinois.edu/wapidoc). If there are more then 1000 objects the API returns an error. By setting max-results one can raise the limit.
-
- 18 Mar, 2019 1 commit
-
-
Christian Glombek authored
The --istio-ingress-gateway flag may now be specified multiple times.
-
- 15 Mar, 2019 1 commit
-
-
David Schneider authored
-
- 19 Feb, 2019 2 commits
-
-
Dimitrij Klesev authored
-
Dimitrij Klesev authored
-
- 24 Jan, 2019 1 commit
-
-
njuettner authored
-
- 17 Jan, 2019 1 commit
-
-
Joe Hohertz authored
number of retries that API calls will attempt before giving up. This somewhat mitigates the issues discussed in #484 by allowing the current sync attempt to complete vs. failing and starting anew. Defaults to 3, which is what the aws-sdk-go defaults to where not specified. Signed-off-by:
Joe Hohertz <joe@viafoura.com>
-
- 16 Jan, 2019 1 commit
-
-
njuettner authored
-
- 07 Dec, 2018 1 commit
-
-
Cesar Wong authored
-
- 17 Oct, 2018 1 commit
-
-
Anand Patel authored
-
- 27 Sep, 2018 1 commit
-
-
Martin Linkhorst authored
-
- 24 Sep, 2018 1 commit
-
-
Vladislav Troinich authored
-
- 06 Sep, 2018 3 commits
-
-
Peter Bale authored
This is to change the way batching works when using the aws provider. Originally, batching would take the first n records you want to update and perform the desired actions on those records as part of a sync. It would then wait for the configured sync period and take the first n records again and sync them. The issue with this is that when you are using the TXT registry with a custom prefix, the updates can sync a TXT record and not the accompanying A/CNAME record. This causes external-dns to get out of sync with what is created and what the current state actually is. This update uses the same idea of batching, however, rather than stopping after the first batch until the next run, batching will now have a separate batch interval which controls the interval between each batch in the same sync period. This allows external-dns to fully sync with route53 as part of each sync and can then know that the state is complete. Fixes https://github.com/kubernetes-incubator/external...
-
Jonas Michel authored
* add Istio Gateway Source * add documentation for Istio Gateway Source * make both istio namespace and ingress gateway service configurable * prefix gateway types, constructors, and flags with 'istio-' * fix: add missing sources to source flag docs
-
Vladislav Troinich authored
-
- 28 Aug, 2018 1 commit
-
-
Li Yi authored
-