github.com/cilium/cilium@v1.16.2/Documentation/network/kubernetes/compatibility.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  .. _k8scompatibility:
     8  
     9  ************************
    10  Kubernetes Compatibility
    11  ************************
    12  
    13  Cilium is compatible with multiple Kubernetes API Groups. Some are deprecated
    14  or beta, and may only be available in specific versions of Kubernetes.
    15  
    16  All Kubernetes versions listed are e2e tested and guaranteed to be compatible
    17  with Cilium. Older and newer Kubernetes versions, while not listed, will depend
    18  on the forward / backward compatibility offered by Kubernetes.
    19  
    20  +------------------------+---------------------------+----------------------------------+
    21  | k8s Version            | k8s NetworkPolicy API     | CiliumNetworkPolicy              |
    22  +------------------------+---------------------------+----------------------------------+
    23  |                        |                           | ``cilium.io/v2`` has a           |
    24  | 1.27, 1.28, 1.29, 1.30 | * `networking.k8s.io/v1`_ | :term:`CustomResourceDefinition` |
    25  +------------------------+---------------------------+----------------------------------+
    26  
    27  As a general rule, Cilium aims to run e2e tests using the latest build from the
    28  development branch against currently supported Kubernetes versions defined in
    29  `Kubernetes Patch Releases <https://kubernetes.io/releases/patch-releases/>`_
    30  page.
    31  
    32  Once a release branch gets created from the development branch, Cilium typically
    33  does not change the Kubernetes versions it uses to run e2e tests for the entire
    34  maintenance period of that particular release.
    35  
    36  Additionally, Cilium runs e2e tests against various cloud providers' managed
    37  Kubernetes offerings using multiple Kubernetes versions. See the following links
    38  for the current test matrix for each cloud provider:
    39  
    40  - :git-tree:`AKS <.github/actions/azure/k8s-versions.yaml>`
    41  - :git-tree:`EKS <.github/actions/aws/k8s-versions.yaml>`
    42  - :git-tree:`GKE <.github/actions/gke/k8s-versions.yaml>`
    43  
    44  Cilium CRD schema validation
    45  ============================
    46  
    47  Cilium uses a CRD for its Network Policies in Kubernetes. This CRD might have
    48  changes in its schema validation, which allows it to verify the correctness of
    49  a Cilium Clusterwide Network Policy (CCNP) or a Cilium Network Policy (CNP).
    50  
    51  The CRD itself has an annotation, ``io.cilium.k8s.crd.schema.version``, with the
    52  schema definition version. By default, Cilium automatically updates the CRD, and
    53  its validation, with a newer one.
    54  
    55  The following table lists all Cilium versions and their expected schema
    56  validation version:
    57  
    58  .. include:: compatibility-table.rst
    59  
    60  .. _networking.k8s.io/v1: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#networkpolicy-v1-networking-k8s-io