Skip to content

fix: convert kramdown definition lists to HTML dl elements#2583

Merged
ctauchen merged 1 commit intotigera:mainfrom
ctauchen:fix-definition-list-html
Mar 11, 2026
Merged

fix: convert kramdown definition lists to HTML dl elements#2583
ctauchen merged 1 commit intotigera:mainfrom
ctauchen:fix-definition-list-html

Conversation

@ctauchen
Copy link
Collaborator

Summary

  • Convert all kramdown-style definition list syntax (term\n: definition) to standard HTML <dl>/<dt>/<dd> elements
  • MDX/Docusaurus does not support kramdown definition lists; these rendered as plain text instead of structured lists
  • Fixes 24 definitions across 6 files (2 source files + 4 versioned copies)

Affected files

  • calico/networking/openstack/neutron-api.mdx (4 definitions across 3 <dl> blocks)
  • calico-cloud/reference/architecture/design/l3-interconnect-fabric.mdx (4 definitions in 1 <dl> block)
  • calico_versioned_docs/version-3.29/networking/openstack/neutron-api.mdx
  • calico_versioned_docs/version-3.30/networking/openstack/neutron-api.mdx
  • calico_versioned_docs/version-3.31/networking/openstack/neutron-api.mdx
  • calico-cloud_versioned_docs/version-22-2/reference/architecture/design/l3-interconnect-fabric.mdx

Test plan

  • Verify definition lists render correctly on affected pages
  • Confirm no markdown/JSX parsing errors in build

🤖 Generated with Claude Code

MDX/Docusaurus does not support the kramdown-style definition list
syntax (term\n: definition). Convert all instances to standard HTML
<dl>/<dt>/<dd> elements which render correctly in MDX without
requiring any additional remark plugins.

Affected files:
- calico/networking/openstack/neutron-api.mdx
- calico-cloud/reference/architecture/design/l3-interconnect-fabric.mdx
- versioned copies of the above (3.29, 3.30, 3.31, calico-cloud-22-2)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ctauchen ctauchen requested a review from a team as a code owner March 10, 2026 17:15
Copilot AI review requested due to automatic review settings March 10, 2026 17:15
@netlify
Copy link

netlify bot commented Mar 10, 2026

Deploy Preview for calico-docs-preview-next ready!

Name Link
🔨 Latest commit dc95000
🔍 Latest deploy log https://app.netlify.com/projects/calico-docs-preview-next/deploys/69b051bb5ffc3600082d0988
😎 Deploy Preview https://deploy-preview-2583--calico-docs-preview-next.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link

netlify bot commented Mar 10, 2026

Deploy Preview succeeded!

Built without sensitive environment variables

Name Link
🔨 Latest commit dc95000
🔍 Latest deploy log https://app.netlify.com/projects/tigera/deploys/69b051ba72af4f000876e201
😎 Deploy Preview https://deploy-preview-2583--tigera.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 91 (🟢 up 20 from production)
Accessibility: 98 (no change from production)
Best Practices: 92 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes a rendering issue where kramdown-style definition list syntax (term\n: definition) was being used in MDX files. Since Docusaurus/MDX does not support kramdown syntax, these definition lists rendered as plain text rather than structured definition lists. The fix converts them to standard HTML <dl>/<dt>/<dd> elements with appropriate inline HTML formatting.

Changes:

  • Convert kramdown definition lists to HTML <dl>/<dt>/<dd> elements in 6 files (2 source + 4 versioned copies), replacing markdown formatting inside the HTML blocks with equivalent HTML tags
  • Add a QoS documentation section backport to the version-3.29 neutron-api file (not mentioned in the PR description)
  • Add Vale linting suppression comments to the version-22-2 l3-interconnect-fabric file to match the source file

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
calico/networking/openstack/neutron-api.mdx Convert 3 kramdown definition list blocks to HTML <dl> elements
calico-cloud/reference/architecture/design/l3-interconnect-fabric.mdx Convert 1 kramdown definition list block (4 terms) to HTML <dl> element
calico_versioned_docs/version-3.29/networking/openstack/neutron-api.mdx Convert definition lists + add new QoS section backport
calico_versioned_docs/version-3.30/networking/openstack/neutron-api.mdx Convert 3 kramdown definition list blocks to HTML <dl> elements
calico_versioned_docs/version-3.31/networking/openstack/neutron-api.mdx Convert 3 kramdown definition list blocks to HTML <dl> elements
calico-cloud_versioned_docs/version-22-2/reference/architecture/design/l3-interconnect-fabric.mdx Convert definition list + add Vale suppression comments

Comment on lines +143 to +177
## QoS

Calico for OpenStack implements some Neutron QoS policy fields: the `max_kbps`
and `max_burst_kbps` fields of bandwidth limit rules, and the `max_kpps` field
of packet rate limit rules. Calico also honours the `direction` field of these
rules, so these limits can be set independently for both ingress and egress
directions.

:::note

There is uncertainty as to whether `max_burst_kbps` is intended to configure
the burst *rate* or the burst *size*. Calico interprets it as the burst *rate*
and honours `neutron.conf` fields for configuring the burst *size*.

:::

There are also new Calico Neutron driver settings (cluster-wide, set in `neutron.conf`):

- `[calico] max_ingress_connections_per_port` for imposing a maximum number of
ingress connections per Neutron port, and

- `[calico] max_egress_connections_per_port` for imposing a maximum number of
egress connections per Neutron port.

- `[calico] ingress_burst_kbits`, if non-zero, configures the maximum allowed
burst at peakrate, in the ingress direction.

- `[calico] egress_burst_kbits`, if non-zero, configures the maximum allowed
burst at peakrate, in the egress direction.

- `[calico] ingress_minburst_bytes`, if non-zero, configures the minimum burst
size for peakrate data, in the ingress direction.

- `[calico] egress_minburst_bytes`, if non-zero, configures the minimum burst
size for peakrate data, in the egress direction.
Copy link

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR description says this PR only "converts kramdown definition lists to HTML dl elements" across the 6 listed files. However, this diff also adds an entirely new "## QoS" section (lines 143–177) to the version-3.29 file. This content backport is not mentioned in the PR summary or test plan. It would be helpful to document this additional change in the PR description so reviewers are aware of it and can verify the content is correct for version 3.29.

Copilot uses AI. Check for mistakes.
Comment on lines +213 to +215
{/* vale Vale.Repetition = NO */}
compute server, shares the same AS as the ToR that they are connected
{/* vale Vale.Repetition = YES */}
Copy link

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR description does not mention the addition of Vale linting suppression comments ({/* vale Vale.Repetition = NO/YES */}) in this file. While these are likely needed to suppress false-positive lint warnings, they should be noted in the PR description for completeness.

Copilot uses AI. Check for mistakes.
@ctauchen ctauchen merged commit 442fe18 into tigera:main Mar 11, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants