Skip to content

Conversation

@Lytol
Copy link

@Lytol Lytol commented Jan 28, 2026

The Helm CRDs have drifted from the base CRDs, and sessionTolerations is missing from the Helm CRDs. This resolves the issue specifically for sessionTolerations. This PR uses the generated site CRD from running just helm-generate, but it prunes all unrelated changes as outlined in #57.

Related to #57

@Lytol Lytol requested a review from ian-flores January 28, 2026 18:17
@claude
Copy link

claude bot commented Jan 28, 2026

Claude finished @Lytol's task —— View job


Reviewing PR

  • Read review guidelines
  • Get PR diff and analyze changes
  • Review Helm CRD changes against checklist
  • Submit review

Verified sessionTolerations schema matches the base CRD exactly. No issues found.

@Lytol Lytol requested a review from amdove January 28, 2026 18:18
Copy link

@claude claude bot left a comment

Choose a reason for hiding this comment

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

Helm Chart Review (dist/chart/)

  • Values have sensible defaults — N/A (CRD schema only)
  • Templates render correctly — Schema addition is well-formed
  • RBAC permissions are minimal — N/A
  • CRDs are up to date — ✅ Verified: sessionTolerations definition matches the base CRD at config/crd/bases/core.posit.team_sites.yaml:1319-1358 exactly

This is a clean, targeted fix that brings the Helm CRD in sync with the base CRD for the sessionTolerations field. The schema correctly defines the Kubernetes Toleration structure with all expected properties (effect, key, operator, tolerationSeconds, value).

@Lytol
Copy link
Author

Lytol commented Jan 28, 2026

How are we handling version bumps by the way? Didn't see any guidance in CONTRIBUTING, so I haven't done anything here yet.

@Lytol
Copy link
Author

Lytol commented Jan 29, 2026

Closing in favor of #60

@Lytol Lytol closed this Jan 29, 2026
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.

3 participants