github.com/cilium/cilium@v1.16.2/Documentation/network/servicemesh/installation.rst (about)

     1  Installation
     2  ############
     3  
     4  .. tabs::
     5  
     6      .. group-tab:: Helm
     7  
     8          Cilium Ingress Controller can be enabled with helm flag ``ingressController.enabled``
     9          set as true. Please refer to :ref:`k8s_install_helm` for a fresh installation.
    10  
    11          .. parsed-literal::
    12  
    13              $ helm upgrade cilium |CHART_RELEASE| \\
    14                  --namespace kube-system \\
    15                  --reuse-values \\
    16                  --set ingressController.enabled=true \\
    17                  --set ingressController.loadbalancerMode=dedicated
    18              $ kubectl -n kube-system rollout restart deployment/cilium-operator
    19              $ kubectl -n kube-system rollout restart ds/cilium
    20  
    21          Cilium can become the default ingress controller by setting the
    22          ``--set ingressController.default=true`` flag. This will create ingress entries even when the ``ingressClass`` 
    23          is not set.
    24  
    25          If you only want to use envoy traffic management feature without Ingress support, you should only
    26          enable ``--enable-envoy-config`` flag.
    27  
    28          .. parsed-literal::
    29  
    30              $ helm upgrade cilium |CHART_RELEASE| \\
    31                  --namespace kube-system \\
    32                  --reuse-values \\
    33                  --set envoyConfig.enabled=true
    34              $ kubectl -n kube-system rollout restart deployment/cilium-operator
    35              $ kubectl -n kube-system rollout restart ds/cilium
    36  
    37          Additionally, the proxy load-balancing feature can be configured with the ``loadBalancer.l7.backend=envoy`` flag.
    38  
    39          .. parsed-literal::
    40              $ helm upgrade cilium |CHART_RELEASE| \\
    41                  --namespace kube-system \\
    42                  --reuse-values \\
    43                  --set loadBalancer.l7.backend=envoy
    44              $ kubectl -n kube-system rollout restart deployment/cilium-operator
    45              $ kubectl -n kube-system rollout restart ds/cilium
    46  
    47          Next you can check the status of the Cilium agent and operator:
    48  
    49          .. code-block:: shell-session
    50  
    51              $ cilium status
    52  
    53          .. include:: ../../installation/cli-download.rst
    54  
    55      .. group-tab:: Cilium CLI
    56  
    57          .. include:: ../../installation/cli-download.rst
    58  
    59          Cilium Ingress Controller can be enabled with the below command
    60  
    61          .. parsed-literal::
    62  
    63              $ cilium install |CHART_VERSION| \
    64                  --set kubeProxyReplacement=true \
    65                  --set ingressController.enabled=true \
    66                  --set ingressController.loadbalancerMode=dedicated
    67  
    68          Cilium can become the default ingress controller by setting the
    69          ``--set ingressController.default=true`` flag. This will create ingress entries even when the ``ingressClass`` 
    70          is not set.
    71  
    72          If you only want to use envoy traffic management feature without Ingress support, you should only
    73          enable ``--enable-envoy-config`` flag.
    74  
    75          .. parsed-literal::
    76  
    77              $ cilium install |CHART_VERSION| \
    78                  --set kubeProxyReplacement=true \
    79                  --set envoyConfig.enabled=true
    80  
    81          Additionally, the proxy load-balancing feature can be configured with the ``loadBalancer.l7.backend=envoy`` flag.
    82  
    83          .. parsed-literal::
    84  
    85              $ cilium install |CHART_VERSION| \
    86                  --set kubeProxyReplacement=true \
    87                  --set envoyConfig.enabled=true \
    88                  --set loadBalancer.l7.backend=envoy
    89  
    90          Next you can check the status of the Cilium agent and operator:
    91  
    92          .. code-block:: shell-session
    93  
    94              $ cilium status
    95  
    96  It is also recommended that you :ref:`install Hubble CLI<hubble_cli_install>`
    97  which will be used used to observe the traffic in later steps.