<div id="readability-page-1" class="page"><section>
<p>notes while reading "istio in action"</p><blockquote>
<p>A service mesh is a distributed application infrastructure that is responsible for handling network traffic on behalf of the application in a transparent, out of process manner.<br>
The service proxies form the "data plane" through which all traffic is handled and observed. The data plane is responsible for establishing, securing, and controlling the traffic through the mesh. The management components that instruct the data plane how to behave is known as the "control plane". The control plane is the brains of the mesh and exposes an API for operators to manipulate the network behaviors. Together, the data plane and the control plane provide important capabilities necessary in any cloud-native architecture</p>
</blockquote>
<p><img src="https://files.jaigouk.com/2021/03/Screenshot_20210323-000033_Moon--Reader-Pro.jpg" alt="Screenshot_20210323-000033_Moon--Reader-Pro" loading="lazy"></p>
<p><img src="https://files.jaigouk.com/2021/03/Screenshot_20210323-003057_Moon--Reader-Pro.jpg" alt="Screenshot_20210323-003057_Moon--Reader-Pro" loading="lazy"></p>
<p>For helm v3.2.4 and k3s arm64 env,</p>
<pre><code>helm repo add querycapistio https://querycap.github.io/istio
kubectl create namespace istio-operater
helm upgrade --install istio-operater querycapistio/istio-operator
</code></pre>
<p>output</p>
<pre><code>Release "istio-operater" has been upgraded. Happy Helming!
NAME: istio-operater
LAST DEPLOYED: Fri Mar 26 17:43:16 2021
NAMESPACE: default
STATUS: deployed
REVISION: 4
TEST SUITE: None
</code></pre>
<p>for k3s, make sure traefik is not running</p>
<pre><code>k3sup install --ip  xx.xx.xx.xx \
        --user my_user \
        --ssh-key ~/.ssh/my_key \
        --ssh-port 22  \
        --k3s-extra-args "--disable traefik"

# ssh to the server 
sudo rm /var/lib/rancher/k3s/server/manifests/traefik.*

k3sup join --server-ip xx.xx.xx.xx \
        --ip yy.yy.yy.yy \
        --user my_user \
        --ssh-key ~/.ssh/my_key \
        --ssh-port 22
</code></pre>
<p>use <a href="https://github.com/querycap/istio/tree/master/deploy/istio-system">istio-system</a> directory to deploy via <a href="https://kubernetes.io/docs/tasks/manage-kubernetes-objects/kustomization/">kustomize</a></p>
<pre><code>kubectl apply -k &lt;kustomization_directory&gt;
</code></pre>
<p>after this, manually change nodeAffinity in deployment. remove other arch values and change value to arm64 for istio-ingressgateway and istio-egressgateway deployments.</p>
<pre><code>      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
              - matchExpressions:
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - arm64
          preferredDuringSchedulingIgnoredDuringExecution:
            - weight: 2
              preference:
                matchExpressions:
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - amd64
</code></pre>
<p><img src="https://files.jaigouk.com/2021/03/istio-deployment.png" alt="istio-deployment" loading="lazy"></p>

</section><section>
<p>
Copyright © <a href="#">Jaigouk.Kim</a> 2021 <span>•</span> All rights reserved.
</p>
<p>
<span>Published with <a href="https://ghost.org/">Ghost</a>.</span>
</p>
</section></div>

Jaigouk.Kim

notes while reading "istio in action"
A service mesh is a distributed application infrastructure that is responsible for handling network traffic on behalf of the application in a transparent, out of process manner.
For helm v3.2.4 and k3s arm64 env,
helm repo add querycapistio https://querycap.github.io/istio
kubectl create namespace istio-operater
helm upgrade --install istio-operater querycapistio/istio-operator
output
Release "istio-operater" has been upgraded. Happy Helming!
NAME: istio-operater
LAST DEPLOYED: Fri Mar 26 17:43:16 2021
NAMESPACE: default
STATUS: deployed
REVISION: 4
TEST SUITE: None
for k3s, make sure traefik is not running
k3sup install --ip  xx.xx.xx.xx \
        --user my_user \
        --ssh-key ~/.ssh/my_key \
        --ssh-port 22  \
        --k3s-extra-args "--disable traefik"
# ssh to the server 
sudo rm /var/lib/rancher/k3s/server/manifests/traefik.*
k3sup join --server-ip xx.xx.xx.xx \
        --ip yy.yy.yy.yy \
        --user my_user \
        --ssh-key ~/.ssh/my_key \
        --ssh-port 22
use istio-system directory to deploy via kustomize
kubectl apply -k <kustomization_directory>
after this, manually change nodeAffinity in deployment. remove other arch values and change value to arm64 for istio-ingressgateway  and  istio-egressgateway deployments.
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
              - matchExpressions:
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - arm64
          preferredDuringSchedulingIgnoredDuringExecution:
            - weight: 2
              preference:
                matchExpressions:
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - amd64

istio

댓글