fix: use valid mission control connection type label#2232
Conversation
Kubernetes label selectors require the label name segment to use valid label syntax, and connectionType contains uppercase characters. Rename the mission-control connection type label to mission-control/connection-type so generated config labels can be selected reliably.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
BenchstatBase: 📊 1 minor regression(s) (all within 5% threshold)
Full benchstat output |
Kubernetes label selectors cannot use the existing
missioncontrol/connectionTypelabel key because the name segment contains uppercase characters.Rename the label to
mission-control/connection-typeso mission-control connection configs can be selected using valid Kubernetes label selector syntax.