I changed job roles and hence working on wksctl more than a year ago, but I forgot to remove myself.

* Remove Bryan Boreham, Dennis, Filip, and Dimitri as maintainers.
* Update google key in tests to pull google images.

- Capei v0.2.5 has some fixes about removing and re-adding the same node
  https://github.com/weaveworks/cluster-api-provider-existinginfra/pull/67

* upgrade capei deps

* ignore .idea folder

* updated k8s.io/kube-openapi dep

* attempt to fix github.com/googleapis/gnostic issue

* added github.com/googleapis/gnostic@v0.5.4

* removed googleapis/gnostic replace from go.mod

* Change versions 1.17.13 - 1.19.8, 1.19.3 - 1.20.4

* additional k8s versions changes. 1.17.x -> 1.19.8

* additional k8s versions fixes

* Testing CAPEI version v0.2.2

* Added 5m sleep

* Calling footloose command directly

* Update kubectl used in CircleCI to 1.20

* Update kubectl to v1.19.8 and ensure is executable

* Update tests to use CAPEI 0.2.2

* Ensure the apply test uses a specific k8s version

* Revert version change to upgradeKubeadmConfig chk

* Default k8s v1.18.16 from 1.19.8 timing fix

* Change coredns back to 1.6.7 for testing

* Revert debug code

* Updated CAPEI dep with version v0.2.3 including changes to support k8s 1.20

* Update test to v.1.18.15 to fix kubelet timeout

* Remove CAPEI build step from CircleCI

* Add version for each machine in multi-master test

* Updated capei dep with latest commit from master

* Update test version of etcd to 3.4.3

* Update CAPEI img in multimaster_test.go to new ver

* Updated capei dep with v0.2.4
Co-authored-by: Mark Emeis <mark.emeis@weave.works>

allow kubernetes v1.20

* Create footloose cluster with eks-d flavor

* Update examples for CAPEI plus eks-d

* Clean up ExistingInfraCluster.DeprecatedKeyPath. It was causing a seed node repave as later node plan creation did not set it

* Update ubuntu vagrant to allow traffic on 6443

* Increase machine memory to 4 gb

* point at current existininfra
Co-authored-by: Jerry Jackson <jerry@weave.works>

Co-authored-by: Jerry Jackson <jerry@weave.works>

Github deprecated some env things:
- https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

New golangci-lint looks like it fixes this
- https://github.com/golangci/golangci-lint-action/issues/127#issuecomment-729139550

- We accidentally deleted some implicit fw rules from gcp
- Add them back here in the terraform scripts

Set cluster, context and user to wks-<cluster-name>

* Work with new capei provider
* Fix wksctl os to correctly handle file and flux configuration
* switch to marking workload clusters in spec
* Set up machine info pool in wksctl to pass to controller in existinginfra
* Removes the requirement for a wks-controller.yaml
  The wks controller comes from the existinginfra provider.  We no longer
  need it in the repository when creating a cluster.
* inline files in cluster manifest for integration tests
* plumb inline ssh key through PEM file processing
* set version on cluster for apply_test
* Re-enables k8s 1.16 cluster support
* Plumb Context through 'plan' steps
  Doesn't do anything different as yet, but this will be useful for
  tracing, or for cancelling a command.
* point to new version of existinginfra and allow for the new context parameter in CreateSeedNodeSetupPlan
* store correct versions in local repo
* add explicit kubernetes version to multimaster test
* pin correct image in apply_test and multimaster_test
Co-authored-by: Jerry Jackson <jerry@weave.works>
Co-authored-by: Mark Emeis <mark.emeis@weave.works>
Co-authored-by: Simon Howe <simon@weave.works>
Co-authored-by: Bryan Boreham <bjboreham@gmail.com>

Annotate seed node via file

It can contain shell characters such as single quote and !, so put
the contents in a file before calling `kubectl annotate`.

Interestingly there is no option in `kubectl` to take the value from
a file, so we still have to `cat` it on the command-line.

Done in http://github.com/weaveworks/cluster-api-provider-existinginfra/pull/30

Plumb Context through 'plan' steps

Doesn't do anything different as yet, but this will be useful for
tracing, or for cancelling a command.

Ignore kubectl error during multimaster test

We often get "etcdserver: leader changed" responses from kubectl, which
can be ignored.
Rather than special write special code for that one error, just log and
ignore all errors on 'kubectl get nodes'.

Remove spurious 'test.yaml'

Tidy the CAPEI image name used in multimaster_test

Add 'status' subresource to CRD definitions

* Use a const instead of repeating the name.
* Keep it named `cluster-api-existinginfra-controller` instead of
renaming it to `wksctl-controller`

* fix erroneous image name and machines filename
* ensure all test calls turn on debugging.