github.com/cilium/cilium@v1.16.2/Documentation/configuration/index.rst (about)

     1  .. only:: not (epub or latex or html)
     2  
     3      WARNING: You are looking at unreleased Cilium documentation.
     4      Please use the official rendered version released here:
     5      https://docs.cilium.io
     6  
     7  .. _configuration:
     8  
     9  Configuration
    10  =============
    11  
    12  Your Cilium installation is configured by one or more Helm values -
    13  see :ref:`helm_reference`. These helm values are converted to arguments
    14  for the individual components of a Cilium installation, such as
    15  :doc:`../cmdref/cilium-agent` and :doc:`../cmdref/cilium-operator`, and
    16  stored in a ConfigMap.
    17  
    18  .. _cilium-config-configmap:
    19  
    20  ``cilium-config`` ConfigMap
    21  -----------------------------
    22  
    23  These arguments are stored in a shared ConfigMap called ``cilium-config``
    24  (albeit without the leading ``--``). For example, a typical installation
    25  may look like
    26  
    27  .. code-block:: shell-session
    28  
    29     $ kubectl -n kube-system get configmap cilium-config -o yaml
    30     data:
    31       agent-not-ready-taint-key: node.cilium.io/agent-not-ready
    32       arping-refresh-period: 30s
    33       auto-direct-node-routes: "false"
    34       (output continues)
    35  
    36  .. _making-config-changes:
    37  
    38  Making Changes
    39  --------------
    40  
    41  You may change the configuration of a running installation in three ways:
    42  
    43  #. Via ``helm upgrade``
    44  
    45     Do so by providing new values to Helm and applying them to the existing
    46     installation. By setting the value ``rollOutCiliumPods=true``, the agent
    47     pods will be gradually restarted.
    48  
    49  
    50  #. Via ``cilium config set``
    51  
    52     The `Cilium CLI <https://github.com/cilium/cilium-cli/>`_ has the ability
    53     to update individual values in the ``cilium-config`` ConfigMap. This will
    54     not affect running pods; pods must be deleted manually to pick up any changes.
    55  
    56  #. Via ``CiliumNodeConfig`` objects
    57  
    58     Cilium also supports configuration on sets of nodes. See the
    59     :ref:`per-node-configuration` page for more details. Likewise, this also requires
    60     that pods be manually deleted for changes to take effect.
    61  
    62  
    63  Core Agent
    64  ----------
    65  .. toctree::
    66     :maxdepth: 1
    67     :glob:
    68  
    69     api-rate-limiting
    70     api-restrictions
    71     per-node-config
    72     sctp
    73     vlan-802.1q
    74     argocd-issues
    75  
    76  Security
    77  --------
    78  .. toctree::
    79     :maxdepth: 1
    80     :glob:
    81  
    82     verify-image-signatures
    83     sbom