Skip to content

PMREQ-810: Refresh enterprise CRDs to add L2 Bridge Network fields#4719

Closed
fasaxc wants to merge 8 commits into
tigera:masterfrom
fasaxc:l2-prod
Closed

PMREQ-810: Refresh enterprise CRDs to add L2 Bridge Network fields#4719
fasaxc wants to merge 8 commits into
tigera:masterfrom
fasaxc:l2-prod

Conversation

@fasaxc

@fasaxc fasaxc commented Apr 20, 2026

Copy link
Copy Markdown
Member

Description

Refreshes the enterprise CRD bundle from tigera/calico-private:master to pick up the L2 Bridge fields on the Network resource (PMREQ-810).

RBAC and the base Network CRD landed earlier via the VRF work on master; this PR is CRD-only.

Release Note

Operator: update Network CRD with L2 support.

For PR author

  • Tests for change.
  • If changing pkg/apis/, run make gen-files
  • If changing versions, run make gen-versions

For PR reviewers

A note for code reviewers - all pull requests must have the following:

  • Milestone set according to targeted release.
  • Appropriate labels:
    • kind/bug if this is a bugfix.
    • kind/enhancement if this is a a new feature.
    • enterprise if this PR applies to Calico Enterprise only.

@marvin-tigera marvin-tigera added this to the v1.43.0 milestone Apr 20, 2026
@fasaxc fasaxc changed the title PMREQ-810: Add Network CRD and RBAC for L2 VM mobility [PMREQ-810]: L2 support phase 1: Add Network CRD and RBAC for L2 VM mobility Apr 22, 2026
@fasaxc fasaxc force-pushed the l2-prod branch 2 times, most recently from b3a971b to acb2e66 Compare May 1, 2026 10:04
Master already carries the Network resource (added with the VRF
work) and the matching RBAC for calico-node, calico-cni-plugin,
calico-typha, calico-apiserver, and non-cluster-host Felix.  This
commit adds the L2 Bridge spec fields by refreshing the enterprise
CRD bundle from the calico-private wt-l2-prod-cni branch, which
has been rebased onto master so it carries both spec.vrf and
spec.l2Bridge.

config/enterprise_versions.yml is temporarily pointed at the
wt-l2-prod-cni branch.  Reset to "master" once wt-l2-prod-cni
merges into calico-private master.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@radTuti radTuti modified the milestones: v1.43.0, v1.44.0 Jun 12, 2026
fasaxc and others added 7 commits June 22, 2026 12:27
Refreshes pkg/imports/crds/enterprise from the monorepo phase-1e branch.
Adds IPPool L2Workload allowedUse (enum + CEL validation rules), L2 bridge
Network CRD fields, WAF/applicationlayer CRDs, and felix/kube-controllers
config additions. Fixes API-server rejection of IPPools with allowedUses:
[L2Workload].

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Updates the Network CRD (v1 + v3) from the calico-private
wt-l2-prod-cni worktree after its latest sync with master.
ECK bundle and other CRDs are unchanged (worktree's master sync
already matches operator master).

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Refresh networks (drop unimplemented L2HostTrunkPort.VLANs), plus
felixconfigurations and ipamblocks regen drift.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The L2 Bridge Network work has been merged to calico-private master,
so reset libcalico-go.version to master and regenerate the enterprise
CRD bundle.  Removes the temporary wt-l2-prod-cni pin.

Note: master does not currently include the L2Workload IPPool allowedUse;
that follow-up will land separately when the IPPool changes merge.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@fasaxc fasaxc changed the title [PMREQ-810]: L2 support phase 1: Add Network CRD and RBAC for L2 VM mobility PMREQ-810: Refresh enterprise CRDs to add L2 Bridge Network fields Jul 8, 2026
@fasaxc fasaxc marked this pull request as ready for review July 8, 2026 10:16
@fasaxc fasaxc requested review from a team and marvin-tigera as code owners July 8, 2026 10:16
@fasaxc fasaxc added kind/enhancement New feature or request enterprise Feature applies to enterprise only labels Jul 8, 2026
@fasaxc

fasaxc commented Jul 8, 2026

Copy link
Copy Markdown
Member Author

Looks like automation picked this up #4995

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enterprise Feature applies to enterprise only kind/enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants