Fix wrong entry in changelog

Update changelog to v0.5.8

Rfc2136 provider

Correctly populate target health check on existing records

Document how to use a different security context

Added linode to supported cloud providers

Continue even if node listing fails

Allow AWS batching to fully sync on each run

Replace glog with a noop logger

Fix handling of custom TTL values with Google DNS.

This is an update to the order in which we have the new mock methods.

Removed comment and added comment to exported mock helper.

Updating CHANGELOG.md to v0.5.6

# Conflicts:
#	Gopkg.lock
#	Gopkg.toml

Fix Host field in HTTP request when using pdns provider

This is to add two new tests which will cover the new logic where the
submit route53 changes function can error if any one of the updates
fails for any given batch in any given zone. Additionally, there is now
a test to check that the application does not try and create a set of
entries if the total number of changes associated with a given name is
greater than the total number of allowed changes per batch.

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...

* 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

The Host field of the HTTP request is set incorrectly when passing
the configured server.  The underlying HTTP library experts a hostname
to be passed.  When passing it a string of the form 'http://pdns.example.com

'
this gets converted into 'http:' (stripping everything from the first
slash onward).  However setting the Host field in the pdnsClientConfig
object is not needed because the underlying library will then parse the
hostname from the URL.

Fixes #661
Signed-off-by: Bartel Sielski <bartel.sielski@gmail.com>

CRD source based on getting endpoints from CRD

Alibaba Cloud Provider add zone info to deployment