Rebase to latest upstream release

.ci-operator.yaml

@@ -0,0 +1,4 @@
+build_root_image:
+  name: release
+  namespace: openshift
+  tag: rhel-8-release-golang-1.17-openshift-4.11

.dockerignore

@@ -1,5 +1,15 @@
-generatedconfigs/
-.env
-kubeconfig
-minikube.kubeconfig
-.travis.yml
+# Ignore everything
+**
+
+# Allow only these
+!/api/**
+!/azure/**
+!/controllers/**
+!/exp/**
+!/feature/**
+!/pkg/**
+!/version/**
+!/util/**
+!/main.go
+!/go.mod
+!/go.sum

.gitignore

@@ -4,12 +4,14 @@
 *.dll
 *.so
 *.dylib
+bin
 
 # Test binary, build with `go test -c`
 *.test
 
 # Output of the go coverage tool, specifically when used with LiteIDE
 *.out
+coverage.*
 
 # Ansible
 *.retry
@@ -23,25 +25,53 @@
 envfile
 
 # kubeconfigs
-/kind.kubeconfig
-/minikube.kubeconfig
-/kubeconfig
+kind.kubeconfig
+minikube.kubeconfig
+kubeconfig
 
-# binaries
-/manager
-/clusterctl
-/clusterazureadm
-bin/
+# ssh keys
+.ssh*
 
 # Example and binary output directory
 /out
 
-# bazel
-/bazel-bin
-/bazel-cluster-api-provider-azure
-/bazel-genfiles
-/bazel-out
-/bazel-testlogs
-
 # vscode
 .vscode
+*.code-workspace
+
+# goland
+.idea
+
+# Ignore output manifests
+config/samples
+manager_image_patch.yaml-e
+manager_pull_policy.yaml-e
+
+# Bazel
+bazel-*
+
+# Tilt files.
+.tiltbuild
+/tilt.d
+tilt-settings.json
+tilt_config.json
+
+# e2e output
+test/e2e/junit.e2e_suite.*.xml
+test/e2e/capz-e2e-*.yaml
+test/e2e/config/azure-dev-envsubst.yaml
+test/e2e/logs/*
+_artifacts
+
+# E2E test templates
+test/e2e/data/infrastructure-azure/v1beta1/cluster-template*.yaml
+
+# boilerplate_test output
+hack/boilerplate/__pycache__
+hack/boilerplate/*.pyc
+
+# Helm chart caching
+.helm/
+
+# release notes
+_releasenotes

.golangci.yml

@@ -0,0 +1,53 @@
+run:
+  deadline: 5m
+  skip-dirs:
+    - mock*
+  skip-files:
+  - "zz_generated.*\\.go$"
+  - ".*conversion.*\\.go$"
+linters:
+  disable-all: true
+  enable:
+    - deadcode
+    - errcheck
+    - errorlint
+    - goconst
+    - gocyclo
+    - godot
+    - gofmt
+    - goimports
+    - golint
+    - gosec
+    - gosimple
+    - govet
+    - ineffassign
+    - interfacer
+    - misspell
+    - nakedret
+    - prealloc
+    - staticcheck
+    - structcheck
+    - unconvert
+    - unused
+    - varcheck
+    - whitespace
+  # Run with --fast=false for more extensive checks
+  fast: true
+issues:
+  exclude-rules:
+    - path: internal/test/
+      linters:
+        - golint
+    - path: cloudtest\.go
+      linters:
+        - golint
+    - path: api/v1alpha3/types\.go
+      linters:
+        - golint
+    - path: _test\.go
+      linters:
+        - unused
+  include:
+  - EXC0002 # include "missing comments" issues from golint
+  max-issues-per-linter: 0
+  max-same-issues: 0

.markdownlinkcheck.json

@@ -0,0 +1,10 @@
+{
+    "ignorePatterns": [{
+        "pattern": "^https://calendar.google.com/calendar"
+    }],
+    "timeout": "5s",
+    "retryOn429": true,
+    "retryCount": 5,
+    "fallbackRetryDelay": "30s",
+    "aliveStatusCodes": [200, 206]
+}

.tiltignore

@@ -0,0 +1 @@
+templates

CONTRIBUTING.md

@@ -1,20 +1,91 @@
 # Contributing Guidelines
+<!-- START doctoc generated TOC please keep comment here to allow auto update -->
+<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
 
-Welcome to Kubernetes. We are excited about the prospect of you joining our [community](https://github.com/kubernetes/community)! The Kubernetes community abides by the CNCF [code of conduct](code-of-conduct.md). Here is an excerpt:
 
-_As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities._
+- [Contributor License Agreements](#contributor-license-agreements)
+- [Finding Things That Need Help](#finding-things-that-need-help)
+- [Contributing a Patch](#contributing-a-patch)
+- [Backporting a Patch](#backporting-a-patch)
+  - [Merge Approval](#merge-approval)
+  - [Google Doc Viewing Permissions](#google-doc-viewing-permissions)
+  - [Issue and Pull Request Management](#issue-and-pull-request-management)
 
-## Getting Started
+<!-- END doctoc generated TOC please keep comment here to allow auto update -->
 
-We have full documentation on how to get started contributing here:
+Read the following guide if you're interested in contributing to cluster-api.
 
-<!---
-If your repo has certain guidelines for contribution, put them here ahead of the general k8s resources
--->
+## Contributor License Agreements
 
-- [Contributor License Agreement](https://git.k8s.io/community/CLA.md) Kubernetes projects require that you sign a Contributor License Agreement (CLA) before we can accept your pull requests
-- [Kubernetes Contributor Guide](http://git.k8s.io/community/contributors/guide) - Main contributor documentation, or you can just jump directly to the [contributing section](http://git.k8s.io/community/contributors/guide#contributing)
-- [Contributor Cheat Sheet](https://git.k8s.io/community/contributors/guide/contributor-cheatsheet.md) - Common resources for existing developers
+We'd love to accept your patches! Before we can take them, we have to jump a couple of legal hurdles.
+
+Please fill out either the individual or corporate Contributor License Agreement (CLA). More information about the CLA and instructions for signing it [can be found here](https://github.com/kubernetes/community/blob/master/CLA.md).
+
+***NOTE***: Only original source code from you and other people that have signed the CLA can be accepted into the repository.
+
+## Finding Things That Need Help
+
+If you're new to the project and want to help, but don't know where to start, we have a semi-curated list of issues that should not need deep knowledge of the system. [Have a look and see if anything sounds interesting](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22). Alternatively, read some of the docs on other controllers and try to write your own, file and fix any/all issues that come up, including gaps in documentation!
+
+## Contributing a Patch
+
+1. If you haven't already done so, sign a Contributor License Agreement (see details above).
+2. Fork the desired repo, develop and test your code changes.
+    1. See the [Development Guide](https://capz.sigs.k8s.io/developers/development.html) for more instructions on setting up your environment and testing changes locally.
+3. Submit a pull request.
+    1. All PRs should be labeled with one of the following kinds
+         - `/kind feature` for PRs releated to adding new features/tests
+         - `/kind bug` for PRs releated to bug fixes and patches
+         - `/kind api-change` for PRs releated to adding, removing, or otherwise changing an API
+         - `/kind cleanup` for PRs releated to code refactoring and cleanup
+         - `/kind deprecation` for PRs related to a feature/enhancement marked for deprecation.
+         - `/kind design` for PRs releated to design proposals
+         - `/kind documentation` for PRs releated to documentation
+         - `/kind failing-test` for PRs releated to to a consistently or frequently failing test.
+         - `/kind flake` for PRs related to a flaky test.
+         - `/kind other` for PRs releated to updating dependencies, minor changes or other
+     2. If the PR requires additional action from users switching to a new release, include the string "action required" in the PR release-notes.
+     3. All code changes must be covered by unit tests and E2E tests.
+     4. All new features should come with user documentation.
+ 4. Once the PR has been reviewed and is ready to be merged, commits should be [squashed](https://github.com/kubernetes/community/blob/master/contributors/guide/github-workflow.md#squash-commits). 
+    1. Ensure that commit message(s) are be meaningful and commit history is readable.
+
+All changes must be code reviewed. Coding conventions and standards are explained in the official [developer docs](https://github.com/kubernetes/community/tree/master/contributors/devel). Expect reviewers to request that you avoid common [go style mistakes](https://github.com/golang/go/wiki/CodeReviewComments) in your PRs.
+
+In case you want to run our E2E tests locally, please refer to [Testing](https://capz.sigs.k8s.io/developers/development.html#submitting-prs-and-testing) guide. An overview of our e2e-test jobs (and also all our other jobs) can be found in [Jobs](https://capz.sigs.k8s.io/developers/jobs.html).
+
+## Backporting a Patch
+
+Cluster API ships older versions through `release-X.X` branches, usually backports are reserved to critical bug-fixes.
+Some release branches might ship with both Go modules and dep (e.g. `release-0.1`), users backporting patches should always make sure
+that the vendored Go modules dependencies match the Gopkg.lock and Gopkg.toml ones by running `dep ensure`
+
+### Merge Approval
+
+Cluster API maintainers may add "LGTM" (Looks Good To Me) or an equivalent comment to indicate that a PR is acceptable. Any change requires at least one LGTM.  No pull requests can be merged until at least one Cluster API maintainer signs off with an LGTM.
+
+### Google Doc Viewing Permissions
+
+To gain viewing permissions to google docs in this project, please join either the [kubernetes-dev](https://groups.google.com/forum/#!forum/kubernetes-dev) or [kubernetes-sig-cluster-lifecycle](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle) google group.
+
+### Issue and Pull Request Management
+
+Anyone may comment on issues and submit reviews for pull requests. However, in
+order to be assigned an issue or pull request, you must be a member of the
+[Kubernetes SIGs](https://github.com/kubernetes-sigs) GitHub organization.
+
+If you are a Kubernetes GitHub organization member, you are eligible for
+membership in the Kubernetes SIGs GitHub organization and can request
+membership by [opening an issue](https://github.com/kubernetes/org/issues/new?template=membership.md&title=REQUEST%3A%20New%20membership%20for%20%3Cyour-GH-handle%3E)
+against the kubernetes/org repo.
+
+However, if you are a member of any of the related Kubernetes GitHub
+organizations but not of the Kubernetes org, you will need explicit sponsorship
+for your membership request. You can read more about Kubernetes membership and
+sponsorship [here](https://github.com/kubernetes/community/blob/master/community-membership.md).
+
+Cluster API maintainers can assign you an issue or pull request by leaving a
+`/assign <your Github ID>` comment on the issue or pull request.
 
 ## Mentorship