Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[BUG] Cilium CNI not compatible with Talos cluster type #361

Closed
AverageMarcus opened this issue Dec 24, 2024 · 1 comment · Fixed by #362
Closed

[BUG] Cilium CNI not compatible with Talos cluster type #361

AverageMarcus opened this issue Dec 24, 2024 · 1 comment · Fixed by #362
Assignees
Labels
bug Something isn't working

Comments

@AverageMarcus
Copy link

Description

When creating a civo_kubernetes_cluster with the cluster type of talos and the CNI as cilium the cluster is created successfully but actually uses the Flannel CNI. Any subsequent applies cause an error before the cni property is immutable and it is now comflicting with the flannel value that was actually applied.

Example:

resource "civo_kubernetes_cluster" "example" {
  firewall_id = civo_firewall.example.id
  network_id = civo_network.example.id

  cluster_type = "talos"
  kubernetes_version = "talos-v1.5.0"
  cni = "cilium"

  pools {
    size = "g4s.kube.xsmall"
    node_count = 2
  }
}

Acceptance Criteria

If cilium is not a valid CNI value for Talos then the initial create should be blocked with an error. Otherwise, if Cilium is a supported CNI then it should use that value when creating the cluster.

@AverageMarcus AverageMarcus added the bug Something isn't working label Dec 24, 2024
@NerdyShawn
Copy link
Contributor

Pretty sure Talos only leverages Flannel currently, if you try to build a new cluster via ui as well and select Talos the cilium option gets greyed out.
image

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants