Replace Loodse -> Kubermatic (#426)

* Replace Loodse -> Kubermatic

* Change loodse -> kubermatic

Author: scheeles

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.

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 Docs project contributors".
+Any copyright notices in this repo should specify the authors as "the Kubermatic Docs project contributors".
 
 To sign your work, just add a line like this at the end of your commit message:
 
@@ -26,16 +26,16 @@ By doing this you state that you can certify the following (from https://develop
 
 ## Email and Chat
 
-The Docs project currently uses the general Loodse email list and Slack channel:
-- Email: [loodse-dev](https://groups.google.com/forum/#!forum/loodse-dev)
+The Docs project currently uses the general Kubermatic email list and Slack channel:
+- Email: [kubermatic-dev](https://groups.google.com/forum/#!forum/kubermatic-dev)
 - Slack: #[kubermatic](http://slack.kubermatic.io/) on Slack
 
 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, please do not file a GitHub issue, but instead email security@loodse.com with the full details, including steps to reproduce the issue.
+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, please do not file a GitHub issue, but instead email security@kubermatic.com with the full details, including steps to reproduce the issue.
 
 
 ## Getting Started

LICENSE

@@ -1,4 +1,4 @@
-Loodse documentation is licensed under the Apache License 2.0 or,
+Kubermatic documentation is licensed under the Apache License 2.0 or,
 alternatively, under the Creative Commons Attribution 4.0 International
 Public License.
 
@@ -190,7 +190,7 @@ Public License.
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright 2019 Loodse
+   Copyright 2019 Kubermatic
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

README.md

@@ -45,5 +45,5 @@ Feedback and discussion are available on [the mailing list][11].
 [2]: https://github.com/kubermatic/docs/blob/master/CONTRIBUTING.md
 [4]: https://github.com/kubermatic/docs/blob/master/CODE_OF_CONDUCT.md
 
-[11]: https://groups.google.com/forum/#!forum/loodse-dev
+[11]: https://groups.google.com/forum/#!forum/kubermatic-dev
 [13]: https://github.com/kubermatic/docs/blob/master/docs/zenhub.md

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.

config.toml

@@ -12,9 +12,9 @@ favicon = "/img/favicon.ico"
 # Prefix URL to edit current page. Will display an "Edit this page" button on top right hand corner of every page.
 # Useful to give opportunity to people to create merge request for your doc.
 # See the config.toml file from this documentation site to have an example.
-editURL = "https://github.com/loodse/docs/edit/master/content/"
+editURL = "https://github.com/kubermatic/docs/edit/master/content/"
 # Author of the site, will be used in meta information
-author = "Loodse GmbH"
+author = "Kubermatic GmbH"
 # Description of the site, will be used in meta information
 description = "Official Kubermatic Documentation"
 # Shows a checkmark for visited pages on the menu
@@ -63,7 +63,7 @@ url = "https://www.kubermatic.com"
 class = "fa fa-globe"
 
 [[params.socials]]
-url = "https://twitter.com/Loodse"
+url = "https://twitter.com/Kubermatic"
 class = "fab fa-twitter"
 
 [[params.socials]]
@@ -75,5 +75,5 @@ url = "https://www.youtube.com/channel/UCHyOXqpOR7TRyOzS5bolcUw"
 class = "fab fa-youtube"
 
 [[params.socials]]
-url = "https://www.facebook.com/loodse/"
+url = "https://www.facebook.com/kubermatic/"
 class = "fab fa-facebook-f"

content/kubecarrier/master/api_reference/_index.md

@@ -669,7 +669,7 @@ spec:
     displayName: CouchDB
     description: The compfy database
   baseCRD:
-    name: couchdbs.eu-west-1.loodse
+    name: couchdbs.eu-west-1.kubermatic
 ```
 
 **Example with limited fields**
@@ -683,7 +683,7 @@ spec:
     displayName: CouchDB
     description: The compfy database
   baseCRD:
-    name: couchdbs.eu-west-1.loodse
+    name: couchdbs.eu-west-1.kubermatic
   derive:
     expose:
     - versions:

content/kubecarrier/master/getting_started/70_api_access.md

@@ -168,7 +168,7 @@ Static users uses a static htpasswd file for user authentication.
 First, create a new file via the `htpasswd` utility. In this example, we are using `Bcrypt` as a hashing algorithm. Make sure to specify a strong algorithm, because the default `MD5` hash is insecure.
 
 ```bash
-htpasswd -B -C 12 -c my-user-file nico@loodse.com
+htpasswd -B -C 12 -c my-user-file nico@kubermatic.com
 ```
 
 Load this file into a Kubernetes Secret into the `kubecarrier-system` namespace:

content/kubecarrier/v0.1/api_reference/_index.md

@@ -613,7 +613,7 @@ spec:
     displayName: CouchDB
     description: The compfy database
   baseCRD:
-    name: couchdbs.eu-west-1.loodse
+    name: couchdbs.eu-west-1.kubermatic
 ```
 
 **Example with limited fields**
@@ -627,7 +627,7 @@ spec:
     displayName: CouchDB
     description: The compfy database
   baseCRD:
-    name: couchdbs.eu-west-1.loodse
+    name: couchdbs.eu-west-1.kubermatic
   derive:
     kindOverride: CouchDBPublic
     expose:

content/kubecarrier/v0.2/api_reference/_index.md

@@ -613,7 +613,7 @@ spec:
     displayName: CouchDB
     description: The compfy database
   baseCRD:
-    name: couchdbs.eu-west-1.loodse
+    name: couchdbs.eu-west-1.kubermatic
 ```
 
 **Example with limited fields**
@@ -627,7 +627,7 @@ spec:
     displayName: CouchDB
     description: The compfy database
   baseCRD:
-    name: couchdbs.eu-west-1.loodse
+    name: couchdbs.eu-west-1.kubermatic
   derive:
     kindOverride: CouchDBPublic
     expose:

content/kubecarrier/v0.2/getting_started/70_api_access.md

@@ -156,7 +156,7 @@ Htpasswd uses a static htpasswd file for user authentication.
 First, create a new file via the `htpasswd` utility. In this example, we are using `Bcrypt` as a hashing algorithm. Make sure to specify a strong algorithm, because the default `MD5` hash is insecure.
 
 ```bash
-htpasswd -B -c my-user-file nico@loodse.com
+htpasswd -B -c my-user-file nico@kubermatic.com
 ```
 
 Load this file into a Kubernetes Secret into the `kubecarrier-system` namespace:

content/kubecarrier/v0.3/api_reference/_index.md

@@ -669,7 +669,7 @@ spec:
     displayName: CouchDB
     description: The compfy database
   baseCRD:
-    name: couchdbs.eu-west-1.loodse
+    name: couchdbs.eu-west-1.kubermatic
 ```
 
 **Example with limited fields**
@@ -683,7 +683,7 @@ spec:
     displayName: CouchDB
     description: The compfy database
   baseCRD:
-    name: couchdbs.eu-west-1.loodse
+    name: couchdbs.eu-west-1.kubermatic
   derive:
     expose:
     - versions:

content/kubecarrier/v0.3/getting_started/70_api_access.md

@@ -168,7 +168,7 @@ Static users uses a static htpasswd file for user authentication.
 First, create a new file via the `htpasswd` utility. In this example, we are using `Bcrypt` as a hashing algorithm. Make sure to specify a strong algorithm, because the default `MD5` hash is insecure.
 
 ```bash
-htpasswd -B -C 12 -c my-user-file nico@loodse.com
+htpasswd -B -C 12 -c my-user-file nico@kubermatic.com
 ```
 
 Load this file into a Kubernetes Secret into the `kubecarrier-system` namespace:

content/kubermatic/master/_index.en.md

@@ -13,7 +13,7 @@ Kubermatic is directly integrated with leading cloud providers Amazon Web Servic
 ## Features
 
 {{% notice tip %}}
-For latest updates follow us on Twitter [@Loodse](https://twitter.com/Loodse)
+For latest updates follow us on Twitter [@Kubermatic](https://twitter.com/Kubermatic)
 {{% /notice %}}
 
 ### Use Kubernetes
@@ -30,4 +30,4 @@ You can add and remove nodes in our easy to use dashboard. Just specify the amou
 
 ## Further Information
 
-See [Loodse.com](https://www.loodse.com/).
+See [Kubermatic.com](https://www.kubermatic.com/).

content/kubermatic/master/advanced/custom_links/_index.en.md

@@ -52,7 +52,7 @@ spec:
   - icon: ""
     label: Twitter
     location: footer
-    url: https://www.twitter.com/loodse
+    url: https://www.twitter.com/kubermatic
   - icon: ""
     label: GitHub
     location: footer

content/kubermatic/master/advanced/oidc_auth/_index.en.md

@@ -37,10 +37,10 @@ In order for the shared `kubeconfig` to be of any use, we must grant that other
 point to the cluster and create a `rolebinding` or `clusterrolebinding`, using the email address of the user the `kubeconfig` was
 shared to as value for the `user` property.
 
-The following example command grants read-only access to the cluster to `lukasz@loodse.com`:
+The following example command grants read-only access to the cluster to `lukasz@kubermatic.com`:
 
 ```bash
-kubectl create clusterrolebinding lukaszviewer --clusterrole=view --user=lukasz@loodse.com
+kubectl create clusterrolebinding lukaszviewer --clusterrole=view --user=lukasz@kubermatic.com
 ```
 
 Now it's time to let the user the cluster was shared to use the config and list some resources for example `pods`.
@@ -56,7 +56,7 @@ If the `lukaszviewer` binding gets deleted or something else goes wrong, the fol
 ```bash
 kubectl get pods
 
-Error from server (Forbidden): pods is forbidden: User "lukasz@loodse.com" cannot list pods in the namespace "default"
+Error from server (Forbidden): pods is forbidden: User "lukasz@kubermatic.com" cannot list pods in the namespace "default"
 ```
 
 ### Prerequisites

content/kubermatic/master/concepts/datacenters/_index.en.md

@@ -151,7 +151,7 @@ datacenters:
           centos: "centos-template"
           coreos: "coreos-template"
       requiredEmailDomains:
-      - "loodse.com"
+      - "kubermatic.com"
       - "example.com"
 
   #==================================

content/kubermatic/master/installation/install_kubermatic_ee/_index.en.md

@@ -8,7 +8,7 @@ enterprise = true
 This chapter explains the installation procedure of Kubermatic into a pre-existing Kubernetes cluster.
 
 {{% notice note %}}
-At the moment you need to be invited to get access to Kubermatic's Docker registry before you can try it out. Please [contact sales](mailto:sales@loodse.com) to receive your credentials.
+At the moment you need to be invited to get access to Kubermatic's Docker registry before you can try it out. Please [contact sales](mailto:sales@kubermatic.com) to receive your credentials.
 {{% /notice %}}
 
 ## Terminology
@@ -144,7 +144,7 @@ dex:
     userID: "08a8684b-db88-4b73-90a9-3cd1661f5466"
 
 kubermaticOperator:
-  # insert the Docker authentication JSON provided by Loodse here
+  # insert the Docker authentication JSON provided by Kubermatic here
   imagePullSecret: |
     {
       "auths": {

content/kubermatic/master/upgrading/2.6_to_2.7/_index.en.md

@@ -106,14 +106,14 @@ datacenters:
     location: Antarctica
     seed: europe-west3-c
     country: DE
-    provider: Loodse
+    provider: Kubermatic
     seed_dns_overwrite: internal8
     spec:
       vsphere:
         endpoint: "https://antarctica.kubermatic.io"
         datacenter: "Datacenter-foo"
         datastore: "datastore-bar"
-        cluster: "loodse-cluster"
+        cluster: "kubermatic-cluster"
         allow_insecure: false
         root_path: "/Datacenter/vm/kubermatic"
         templates:

content/kubermatic/master/upgrading/2.8_to_2.9/_index.en.md

@@ -67,7 +67,7 @@ Within the "Add Node" dialog, the user can specific if a floating IP should be a
 If the assignment of floating IP's is a requirement to ensure Node-> API server communication, the assignment can be enforced within the datacenters.yaml:
 
 ```yaml
-  loodse-hamburg-1:
+  kubermatic-hamburg-1:
     location: Hamburg
     seed: europe-west3-c
     country: DE

content/kubermatic/v2.12/_index.en.md

@@ -15,7 +15,7 @@ Kubermatic is directly integrated with leading cloud providers Amazon Web Servic
 ## Features
 
 {{% notice tip %}}
-For latest updates follow us on Twitter [@Loodse](https://twitter.com/Loodse)
+For latest updates follow us on Twitter [@Kubermatic](https://twitter.com/Kubermatic)
 {{% /notice %}}
 
 ### Use Kubernetes
@@ -32,4 +32,4 @@ You can add and remove nodes in our easy to use dashboard. Just specify the amou
 
 ## Further Information
 
-See [Loodse.com](https://www.loodse.com/).
+See [Kubermatic.com](https://www.kubermatic.com/).

content/kubermatic/v2.12/advanced/custom_links/_index.en.md

@@ -63,7 +63,7 @@ As a first step we need to change the application config:
   "custom_links": [
     {
       "label": "Twitter",
-      "url": "https://www.twitter.com/loodse"
+      "url": "https://www.twitter.com/kubermatic"
     },
     {
       "label": "GitHub",
@@ -99,7 +99,7 @@ Let's change some of the icons:
   "custom_links": [
     {
       "label": "Twitter",
-      "url": "https://www.twitter.com/loodse",
+      "url": "https://www.twitter.com/kubermatic",
       "icon": "http://www.stickpng.com/assets/images/580b57fcd9996e24bc43c53e.png"
     },
     {

content/kubermatic/v2.12/advanced/oidc_auth/_index.en.md

@@ -37,10 +37,10 @@ In order for the shared `kubeconfig` to be of any use, we must grant that other
 point to the cluster and create a `rolebinding` or `clusterrolebinding`, using the email address of the user the `kubeconfig` was
 shared to as value for the `user` property.
 
-The following example command grants read-only access to the cluster to `lukasz@loodse.com`:
+The following example command grants read-only access to the cluster to `lukasz@kubermatic.com`:
 
 ```bash
-kubectl create clusterrolebinding lukaszviewer --clusterrole=view --user=lukasz@loodse.com
+kubectl create clusterrolebinding lukaszviewer --clusterrole=view --user=lukasz@kubermatic.com
 ```
 
 Now it's time to let the user the cluster was shared to use the config and list some resources for example `pods`.
@@ -56,7 +56,7 @@ If the `lukaszviewer` binding gets deleted or something else goes wrong, the fol
 ```bash
 kubectl get pods
 
-Error from server (Forbidden): pods is forbidden: User "lukasz@loodse.com" cannot list pods in the namespace "default"
+Error from server (Forbidden): pods is forbidden: User "lukasz@kubermatic.com" cannot list pods in the namespace "default"
 ```
 
 ### Prerequisites

content/kubermatic/v2.12/concepts/datacenters/_index.en.md

@@ -151,7 +151,7 @@ datacenters:
           centos: "centos-template"
           coreos: "coreos-template"
       requiredEmailDomains:
-      - "loodse.com"
+      - "kubermatic.com"
       - "example.com"
 
   #==================================

content/kubermatic/v2.12/installation/install_kubermatic/_index.en.md

@@ -8,7 +8,7 @@ weight = 20
 This chapter explains the automated as well as the manual installation of Kubermatic into a pre-existing Kubernetes cluster.
 
 {{% notice note %}}
-At the moment you need to be invited to get access to Kubermatic's Docker registry before you can try it out. Please [contact sales](mailto:sales@loodse.com) to receive your credentials.
+At the moment you need to be invited to get access to Kubermatic's Docker registry before you can try it out. Please [contact sales](mailto:sales@kubermatic.com) to receive your credentials.
 {{% /notice %}}
 
 ## Terminology

content/kubermatic/v2.12/installation/install_kubermatic/_installer.en.md

@@ -8,7 +8,7 @@ weight = 10
 Using the installer is the recommended way of installing Kubermatic into your cluster. It provides a simple web wizard for configuration and automates the installation of all required components.
 
 {{% notice note %}}
-At the moment you need to be invited to get access to Kubermatic's Docker registry before you can try it out. Please [contact sales](mailto:sales@loodse.com) to receive your credentials.
+At the moment you need to be invited to get access to Kubermatic's Docker registry before you can try it out. Please [contact sales](mailto:sales@kubermatic.com) to receive your credentials.
 {{% /notice %}}
 
 ## Quickstart