Loodse => Kubermatic, update OWNERS (#1061)

Author: xrstf

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # How to Contribute
 
-Loodse projects are [Apache 2.0 licensed](LICENSE) and accept contributions via
+Kubermatic projects are [Apache 2.0 licensed](LICENSE) and accept contributions via
 GitHub pull requests.  This document outlines some of the conventions on
 development workflow, commit message formatting, contact points and other
 resources to make it easier to get your contribution accepted.
@@ -12,7 +12,7 @@ Origin (DCO). This document was created by the Linux Kernel community and is a
 simple statement that you, as a contributor, have the legal right to make the
 contribution. See the [DCO](DCO) file for details.
 
-Any copyright notices in this repo should specify the authors as "the Loodse Machine Controller project contributors".
+Any copyright notices in this repo should specify the authors as "the Kubermatic Machine Controller project contributors".
 
 To sign your work, just add a line like this at the end of your commit message:
 
@@ -32,17 +32,16 @@ By doing this you state that you can certify the following (from https://develop
 
 ## Email and Chat
 
-The Machine Controller project currently uses the general Loodse email list and Slack channel:
+The Machine Controller project currently uses the general Kubermatic email list and Slack channel:
 - Email: [loodse-dev](https://groups.google.com/forum/#!forum/loodse-dev)
 - Slack: #kubermatic channel on [Kubermatic Slack]((http://slack.kubermatic.io/))
 
 Please avoid emailing maintainers found in the MAINTAINERS file directly. They
 are very busy and read the mailing lists.
 
-##  Reporting a security vulnerability
-
-Due to their public nature, GitHub and mailing lists are not appropriate places for reporting vulnerabilities. If you suspect you have found a security vulnerability in rkt, please do not file a GitHub issue, but instead email [email protected] with the full details, including steps to reproduce the issue.
+## Reporting a security vulnerability
 
+Due to their public nature, GitHub and mailing lists are not appropriate places for reporting vulnerabilities. If you suspect you have found a security vulnerability in machine-controller, please do not file a GitHub issue, but instead email [email protected] with the full details, including steps to reproduce the issue.
 
 ## Getting Started
 

NOTICE

@@ -1,5 +1,5 @@
-Loodse Project
-Copyright 2019 Loodse GmbH
+Kubermatic Project
+Copyright 2019 Kubermatic GmbH
 
-This product includes software developed at Loodse GmbH.
-(http://www.loodse.com/).
+This product includes software developed at Kubermatic GmbH.
+(http://www.kubermatic.com/).

OWNERS

@@ -7,4 +7,4 @@ reviewers:
   - machine-controller-maintainers
 
 labels:
-  - team/lifecycle
+  - sig/cluster-management

OWNERS_ALIASES

@@ -2,12 +2,11 @@
 
 aliases:
   machine-controller-maintainers:
-    - irozzo-1A
     - kron4eg
+    - mfranczy
     - moadqassem
     - moelsayed
     - themue
-    - xrstf
     - xmudrii
+    - xrstf
     - youssefazrak
-    - mfranczy

README.md

@@ -23,14 +23,15 @@
 - Using Ubuntu, Flatcar or CentOS 7 distributions ([not all distributions work on all providers](/docs/operating-system.md))
 
 ## Supported Kubernetes versions
-machine-controller tries to follow as close as possible the Kubernetes version
-[support policy](https://kubernetes.io/docs/setup/release/version-skew-policy/).
+machine-controller tries to follow the Kubernetes version
+[support policy](https://kubernetes.io/docs/setup/release/version-skew-policy/) as close as possible.
 
 Currently supported K8S versions are:
+
+- 1.22
+- 1.21
 - 1.20
 - 1.19
-- 1.18
-- 1.17
 
 ## What does not work
 - Master creation (Not planned at the moment)

Zenhub.md

@@ -3,7 +3,7 @@
 As an Open Source community, it is necessary for our work, communication, and collaboration to be done in the open.
 GitHub provides a central repository for code, pull requests, issues, and documentation.  When applicable, we will use Google Docs for design reviews, proposals, and other working documents.
 
-While GitHub issues, milestones, and labels generally work pretty well, the Loodse team has found that product planning requires some additional tooling that GitHub projects do not offer.  
+While GitHub issues, milestones, and labels generally work pretty well, the Kubermatic team has found that product planning requires some additional tooling that GitHub projects do not offer.
 
 In our effort to minimize tooling while enabling product management insights, we have decided to use [ZenHub Open-Source](https://www.zenhub.com/blog/open-source/) to overlay product and project tracking on top of GitHub.
 ZenHub is a GitHub application that provides Kanban visualization, Epic tracking, fine-grained prioritization, and more.  It's primary backing storage system is existing GitHub issues along with additional metadata stored in ZenHub's database.

code-of-conduct.md

@@ -1,4 +1,4 @@
-# Loodse Community Code of Conduct
+# Kubermatic Community Code of Conduct
 
 ## Contributor Code of Conduct
 
@@ -32,6 +32,6 @@ Conduct may be permanently removed from the project team.
 This code of conduct applies both within project spaces and in public spaces
 when an individual is representing the project or its community.
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Loodse Conduct Committee via coc@loodse.com.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Kubermatic Conduct Committee via coc@kubermatic.com.
 
 This Code of Conduct is adapted from the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) and [Contributor Covenant](http://contributor-covenant.org/version/1/2/0/), version 1.2.0.

docs/vsphere.md

@@ -121,7 +121,7 @@ Procedure:
       "NetworkMapping": [
         {
           "Name": "VM Network",
-          "Network": "Loodse Default"
+          "Network": "Kubermatic Default"
         }
       ],
       "MarkAsTemplate": false,