You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue:
Kilo currently relies on node.spec.podCIDR for subnet announcement. However, when Cilium is in cluster-mode, it doesn't respect node.spec.podCIDR and doesn't populates subnet from CiliumNode to Node. This behavior leads to inconsistencies in subnet allocation.
Suggestion:
I propose introducing the annotation kilo.squat.ai/force-subnet as a means to enforce subnet allocation. This annotation would allow users to specify the desired subnet directly, ensuring consistency between Kilo and your environment.
Expected Benefits:
Flexibility: Provides users with the flexibility to enforce specific subnets where necessary, accommodating diverse network configurations.
The text was updated successfully, but these errors were encountered:
Issue:
Kilo currently relies on
node.spec.podCIDR
for subnet announcement. However, when Cilium is in cluster-mode, it doesn't respectnode.spec.podCIDR
and doesn't populates subnet from CiliumNode to Node. This behavior leads to inconsistencies in subnet allocation.Suggestion:
I propose introducing the annotation
kilo.squat.ai/force-subnet
as a means to enforce subnet allocation. This annotation would allow users to specify the desired subnet directly, ensuring consistency between Kilo and your environment.Expected Benefits:
The text was updated successfully, but these errors were encountered: