Update to 1.15.1 (synced from [email protected]) (#142)

CHANGELOG.md

@@ -9,6 +9,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
+- Upgrade cilium to `1.15.1`.
+
+### Changed
+
 - Replace `null` values in `values.yaml` with its actual defaults. Config values with `null` types in the values schema prevented users from changing its values.
 
 ## [0.19.2] - 2024-01-22

helm/cilium/Chart.yaml

@@ -2,10 +2,10 @@ apiVersion: v2
 name: cilium
 displayName: Cilium
 home: https://cilium.io/
-version: 0.19.2
-appVersion: 1.14.5
+version: 0.20.0
+appVersion: 1.15.1
 kubeVersion: ">= 1.16.0-0"
-icon: https://cdn.jsdelivr.net/gh/cilium/cilium@v1.14/Documentation/images/logo-solo.svg
+icon: https://cdn.jsdelivr.net/gh/cilium/cilium@v1.15/Documentation/images/logo-solo.svg
 description: eBPF-based Networking, Security, and Observability
 keywords:
   - BPF
@@ -75,15 +75,15 @@ annotations:
       description: |
         Cilium Endpoint represents the status of individual pods or nodes in
         the cluster which are managed by Cilium, including enforcement status,
-        IP addressing and whether the networking is succesfully operational.
+        IP addressing and whether the networking is successfully operational.
     - kind: CiliumEndpointSlice
       version: v2alpha1
       name: ciliumendpointslices.cilium.io
       displayName: Cilium Endpoint Slice
       description: |
         Cilium Endpoint Slice represents the status of groups of pods or nodes
         in the cluster which are managed by Cilium, including enforcement status,
-        IP addressing and whether the networking is succesfully operational.
+        IP addressing and whether the networking is successfully operational.
     - kind: CiliumEgressGatewayPolicy
       version: v2
       name: ciliumegressgatewaypolicies.cilium.io
@@ -112,6 +112,40 @@ annotations:
       description: |
         Cilium BGP Peering Policy instructs Cilium to create specific BGP peering
         configurations.
+    - kind: CiliumBGPClusterConfig
+      version: v2alpha1
+      name: ciliumbgpclusterconfigs.cilium.io
+      displayName: Cilium BGP Cluster Config
+      description: |
+        Cilium BGP Cluster Config instructs Cilium operator to create specific BGP cluster
+        configurations.
+    - kind: CiliumBGPPeerConfig
+      version: v2alpha1
+      name: ciliumbgppeerconfigs.cilium.io
+      displayName: Cilium BGP Peer Config
+      description: |
+        CiliumBGPPeerConfig is a common set of BGP peer configurations. It can be referenced 
+        by multiple peers from CiliumBGPClusterConfig.
+    - kind: CiliumBGPAdvertisement
+      version: v2alpha1
+      name: ciliumbgpadvertisements.cilium.io
+      displayName: Cilium BGP Advertisement
+      description: |
+        CiliumBGPAdvertisement is used to define source of BGP advertisement as well as BGP attributes 
+        to be advertised with those prefixes.
+    - kind: CiliumBGPNodeConfig
+      version: v2alpha1
+      name: ciliumbgpnodeconfigs.cilium.io
+      displayName: Cilium BGP Node Config
+      description: |
+        CiliumBGPNodeConfig is read only node specific BGP configuration. It is constructed by Cilium operator.
+        It will also contain node local BGP state information.
+    - kind: CiliumBGPNodeConfigOverride
+      version: v2alpha1
+      name: ciliumbgpnodeconfigoverrides.cilium.io
+      displayName: Cilium BGP Node Config Override
+      description: |
+        CiliumBGPNodeConfigOverride can be used to override node specific BGP configuration.
     - kind: CiliumLoadBalancerIPPool
       version: v2alpha1
       name: ciliumloadbalancerippools.cilium.io

helm/cilium/files/agent/poststart-eni.bash

@@ -11,9 +11,9 @@ set -o nounset
 # dependencies on anything that is part of the startup script
 # itself, and can be safely run multiple times per node (e.g. in
 # case of a restart).
-if [[ "$(iptables-save | grep -c 'AWS-SNAT-CHAIN|AWS-CONNMARK-CHAIN')" != "0" ]];
+if [[ "$(iptables-save | grep -E -c 'AWS-SNAT-CHAIN|AWS-CONNMARK-CHAIN')" != "0" ]];
 then
     echo 'Deleting iptables rules created by the AWS CNI VPC plugin'
-    iptables-save | grep -v 'AWS-SNAT-CHAIN|AWS-CONNMARK-CHAIN' | iptables-restore
+    iptables-save | grep -E -v 'AWS-SNAT-CHAIN|AWS-CONNMARK-CHAIN' | iptables-restore
 fi
 echo 'Done!'