Please provide Calico 3.15 or newer to support Wireguard encryption via Calico

Bug #1917383 reported by Paul Goins
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Calico Charm
Triaged
Medium
Unassigned
Canal Charm
Triaged
Medium
Unassigned

Bug Description

A customer I'm working with is looking to have their in-cluster K8s traffic encrypted, and the WireGuard integration added to Calico 3.15 has been brought up as a way to easily enable this.

While I understand charm-calico would allow for us to use upstream-provided images (e.g. https://hub.docker.com/r/calico/node, https://hub.docker.com/r/calico/kube-controllers), it seems it would be preferable for us to have this via a CDK image hosted via rocks.canonical.com.

Best Regards,
Paul Goins

Revision history for this message
Paul Goins (vultaire) wrote :

I recognize this project might be somewhat of a mismatch for the bug, but I wasn't sure which exact project should receive that request. That being said, it may be desirable to update the charm defaults if a new image is made available.

Please link this bug to the appropriate project if this is not the right place. Thank you.

Revision history for this message
George Kraft (cynerva) wrote :

I suspect this will be more than just a trivial image bump. I recall trying to update Calico a few months back as part of the VXLAN work, but hit some problems where pods were unable to communicate with eachother on the newer Calico. So I think some investigation and charm fixes will be needed along with the new images.

Changed in charm-calico:
importance: Undecided → Medium
Changed in charm-canal:
importance: Undecided → Medium
Changed in charm-calico:
status: New → Triaged
Changed in charm-canal:
status: New → Triaged
Changed in charm-calico:
milestone: none → 1.21
Changed in charm-canal:
milestone: none → 1.21
Revision history for this message
George Kraft (cynerva) wrote :

This won't be making it into 1.21.

Changed in charm-calico:
milestone: 1.21 → none
Changed in charm-canal:
milestone: 1.21 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.