Add InsecureSkipTLSVerify option to multicluster RemoteConfig#911
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR adds an ChangesInsecure TLS Skip Option
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsStopped waiting for pipeline failures after 30000ms. One of your pipelines takes longer than our 30000ms fetch window to run, so review may not consider pipeline-failure results for inline comments if any failures occurred after the fetch window. Increase the timeout if you want to wait longer or run a 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 |
Test Coverage ReportTest Coverage 📊: 69.5% |
Add an InsecureSkipTLSVerify option to the multicluster RemoteConfig and the corresponding Client.AddRemote method. Some remote apiservers rotate their CA certificate frequently and have no stable root certificate to pin, so users need a way to opt out of CA verification per remote. When set, CAData and CAFile are cleared and rest.Config.Insecure is set to true, and any configured caCert is ignored. The new insecureSkipTLSVerify log field surfaces the choice in startup logs whenever a remote is added without verification.
Assisted-by: Claude Code:claude-opus-4 [Bash]