Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Z9r5 patch 1 #306

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions candi/cloud-providers/gcp/docs/ENVIRONMENT.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,18 +3,16 @@ title: "Cloud provider — GCP: Preparing environment"
description: "Configuring GCP for Deckhouse cloud provider operation."
---

You need to create a service account so that Deckhouse can manage resources in the Google Cloud. Below is a brief sequence of steps to create a service account. If you need detailed instructions, you can find them in the [provider's documentation](https://cloud.google.com/iam/docs/service-accounts).
You ned to create a service account so that Deckhouse can manage resources in the Google Cloud. Below is a brief sequence of steps to create a service account. If you need detailed instructions, you can find them in the [provider's documentation](https://cloud.google.com/iam/docs/service-accounts).

> **Note!** The created `service account key` cannot be restored, you can only delete and create a new one.
## Setup using Google Cloud Console

Follow this [link](https://console.cloud.google.com/iam-admin/serviceaccounts), select your project and create a new service account or select an existing one.

The account must be assigned several necessary roles:

```text
Compute Admin
Comput Admin
Service Account User
Network Management Admin
```
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ description: "Описание схем размещения и взаимоде

## Standard

* Для кластера создается отдельная VPC с [Cloud NAT](https://cloud.google.com/nat/docs/overview).
* Для астера создается отдельная VPC с [Cloud NAT](https://cloud.google.com/nat/docs/overview).
* Узлы в кластере не имеют публичных IP-адресов.
* Публичные IP-адреса можно назначить на статические и master-узлы:
* При этом будет использоваться One-to-One NAT для отображения публичного IP-адреса в IP-адрес узла (следует помнить, что CloudNAT в этом случае использоваться не будет).
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,6 @@ kind: VCDClusterConfiguration
apiVersions:
- apiVersion: deckhouse.io/v1
openAPISpec:
type: object
additionalProperties: false
description: |
Describes the configuration of a cloud cluster in VCD.

Expand Down
4 changes: 2 additions & 2 deletions modules/021-cni-cilium/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@ This module is responsible for providing a network between multiple nodes in a c

## Limitations

1. Service types `NodePort` and `LoadBalancer` do not work with hostNetwork endpoints in the `DSR` LB mode. Switch to `SNAT` if it is required.
`DSR` LB mode. Switch to `SNAT` if it is required.
2. `HostPort` Pods will bind only to [one interface IP](https://github.com/deckhouse/deckhouse/issues/3035). If there are multiple interfaces/IPs present, Cilium will select only one of them, preferring private IP space.
3. Kernel requirements.
* The `cni-cilium` module requires a Linux kernel version >= `5.7`.
* For the `cni-cilium` module to work together with the [istio](../110-istio/), [openvpn](../500-openvpn/) or [node-local-dns]({% if site.d8Revision == 'CE' %}{{ site.urls.ru}}/documentation/v1/modules/{% else %}..{% endif %}/350-node-local-dns/) module, a Linux kernel version >= `5.7` is required.
4. OS compatibility issues:
* Ubuntu:
* not working on 18.04
1. Service types `NodePort` and `LoadBalancer` do not work with hostNetwork endpoints in the * not working on 18.04
* to work on 20.04 you need to install HWE kernel
* CentOS:
* 7 (needs new kernel from [repository](http://elrepo.org))
Expand Down
3 changes: 2 additions & 1 deletion modules/021-cni-cilium/docs/README_RU.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,8 @@ description: Модуль cni-cilium Deckhouse обеспечивает рабо
2. `HostPort` поды биндятся только [к одному IP](https://github.com/deckhouse/deckhouse/issues/3035). Если в ОС есть несколько интерфейсов/IP, Cilium выберет один из них, предпочитая «серые» IP-адреса «белым».
3. Требования к ядру:
* Для работы модуля `cni-cilium` необходимо ядро Linux версии >= `5.7`.
* Для работы модуля `cni-cilium` совместно с модулем [istio](../110-istio/), [openvpn](../500-openvpn/) или [node-local-dns]({% if site.d8Revision == 'CE' %}{{ site.urls.ru}}/documentation/v1/modules/{% else %}..{% endif %}/350-node-local-dns/) необходимо ядро Linux версии >= `5.7`.
* Для работы модуля `cni-cilium` совместно с модулем [istio](../110-istio/), [openvpn](../500-openvpn/) или
1. Service types `NodePort` and `LoadBalancer` do not work with hostNetwork endpoints in the [node-local-dns]({% if site.d8Revision == 'CE' %}{{ site.urls.ru}}/documentation/v1/modules/{% else %}..{% endif %}/350-node-local-dns/) необходимо ядро Linux версии >= `5.7`.
4. Проблемы совместимости с ОС:
* Ubuntu:
* не работоспособно на 18.04
Expand Down
22 changes: 0 additions & 22 deletions modules/030-cloud-provider-gcp/docs/CONFIGURATION.md

This file was deleted.

22 changes: 0 additions & 22 deletions modules/030-cloud-provider-gcp/docs/CONFIGURATION_RU.md

This file was deleted.

5 changes: 0 additions & 5 deletions modules/030-cloud-provider-gcp/docs/CR.md

This file was deleted.

5 changes: 0 additions & 5 deletions modules/030-cloud-provider-gcp/docs/CR_RU.md

This file was deleted.

38 changes: 0 additions & 38 deletions modules/030-cloud-provider-gcp/docs/EXAMPLES.md

This file was deleted.

38 changes: 0 additions & 38 deletions modules/030-cloud-provider-gcp/docs/EXAMPLES_RU.md

This file was deleted.

21 changes: 0 additions & 21 deletions modules/030-cloud-provider-gcp/docs/FAQ.md

This file was deleted.

21 changes: 0 additions & 21 deletions modules/030-cloud-provider-gcp/docs/FAQ_RU.md

This file was deleted.

14 changes: 0 additions & 14 deletions modules/030-cloud-provider-gcp/docs/README.md

This file was deleted.

14 changes: 0 additions & 14 deletions modules/030-cloud-provider-gcp/docs/README_RU.md

This file was deleted.

2 changes: 2 additions & 0 deletions modules/040-terraform-manager/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,3 +12,5 @@ The module provide tools for working with Terraform in the Kubernetes cluster.
* The module is enabled by default if the following secrets are present in the cluster:
* `kube-system/d8-provider-cluster-configuration`;
* `d8-system/d8-cluster-terraform-state`.

edecrip
Loading