Differences

This shows you the differences between two versions of the page.

--- linux_faq:kubernetes_using_single_node_as_master_and_worker [2021/07/14 07:59] – [Ingress-controller] admin
+++ linux_faq:kubernetes_using_single_node_as_master_and_worker [2021/07/14 10:08] – [Cert manager] admin
@@ Line 124: / Line 124: @@
 https://habr.com/ru/company/southbridge/blog/443110/ \\
 https://metallb.universe.tf/installation/ \\
-  kubectl create ns metallb-system
+  helm repo add metallb https://metallb.github.io/metallb
-  helm install --name metallb stable/metallb --namespace metallb-system
+  helm repo update
-При установке с помощью **helm** конфигурация хранится в **ConfigMap** с именем **metallb-config**, который лежит в том же неймспейсе куда установлен **metallb** (в данном случае - **metallb-system**).
+  kubectl create ns metallb-system
-<code>apiVersion: v1
+  helm upgrade --install -n metallb-system metallb metallb/metallb \
-kind: ConfigMap
+    --set configInline.address-pools[0].name="default" \
-metadata:
+    --set configInline.address-pools[0].protocol="layer2" \
-  namespace: metallb-system
+    --set configInline.address-pools[0].addresses[0]="192.168.77.160-192.168.77.189"
-  name: metallb-config
-data:
-  config: |
-    address-pools:
-    - name: default
-      protocol: layer2
-      addresses:
-      - 192.168.77.160-192.168.77.189
-</code>
 ==== Апгрейдим metallb ====
   helm repo update
-  helm upgrade metallb stable/metallb --namespace metallb-system
+  helm upgrade -n metallb-system metallb metallb/metallb --reuse-values
 ===== Ingress-controller =====
 https://docs.cert-manager.io/en/latest/tutorials/acme/quick-start/# \\
@@ Line 180: / Line 170: @@
 https://docs.cert-manager.io/en/latest/getting-started/install/kubernetes.html#installing-with-helm \\
 Устанавливаем:
-<code># Install the CustomResourceDefinition resources separately
+<code>kubectl create namespace cert-manager
-kubectl apply --validate=false -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.11/deploy/manifests/00-crds.yaml
-# Create the namespace for cert-manager
-kubectl create namespace cert-manager
-# Add the Jetstack Helm repository
 helm repo add jetstack https://charts.jetstack.io
-# Update your local Helm chart repository cache
 helm repo update
-# Install the cert-manager Helm chart
+helm upgrade --install \
-helm install \
+  cert-manager jetstack/cert-manager \
-  --name cert-manager \
   --namespace cert-manager \
-  --version v0.11.0 \
+  --create-namespace \
-  jetstack/cert-manager
+  --version v1.4.0 \
+  --set installCRDs=true
 </code>
 https://docs.cert-manager.io/en/latest/tasks/issuers/index.html \\
 Создаем издателя **Let's Encrypt** (ACME Issuer):
-<code>apiVersion: cert-manager.io/v1alpha2
+<code>kubectl apply -f - << EOF
+apiVersion: cert-manager.io/v1
 kind: ClusterIssuer
 metadata:
@@ Line 220: / Line 203: @@
         ingress:
           class: nginx
+EOF
 </code>
 Смотрим на его состояние:
@@ Line 234: / Line 218: @@
 ==== Апгрейдим cert-manager ====
   helm repo update
-  helm upgrade --namespace cert-manager cert-manager jetstack/cert-manager
+  helm upgrade --namespace cert-manager cert-manager jetstack/cert-manager --reuse-values
 ===== Ingress, Cert-Manager и сертификаты Let's Encrypt =====
 <del>https://docs.cert-manager.io/en/latest/getting-started/install/kubernetes.html</del>\\