GitLab

better flag parse testing

ingress basic implementation

allow google provider to send requests in batches

create shared_test and scope service tests

add test command for convinience

* 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

consistently use CoreV1() instead of Core()

add useful badges to the readme

* add makefile with coverage

* fix syntax, go get gocovmerge

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

Extract Status.LoadBalancer.Hostname from service annotations

Add simple makefile, with `make verify` task

Add .gitignore, based on kubernetes/kubernetes

Document existing kops dns-controller annotations

On AWS, the loadbalancer is / will be / should be set up in the
hostname.

verify runs the same verification as the CI runs.

Trimmed to remove ignores that are obviously kubernetes specific