chore: use kubeconfig instead of doctl for dev deployment#555
chore: use kubeconfig instead of doctl for dev deployment#555
Conversation
|
Warning Rate limit exceeded
⌛ 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. WalkthroughModified GitHub Actions workflow to replace DigitalOcean doctl-based kubeconfig retrieval with inline secret-driven setup. Removed CLUSTER environment variable and doctl installation steps. Added new step to decode kubeconfig from secrets directly into ~/.kube/config. Changes
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
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 |
Replace DIGITALOCEAN_CI_TOKEN with KUBECONFIG_DEV secret (plain YAML) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
c088717 to
8890cec
Compare
Summary
secrets.DIGITALOCEAN_CI_TOKENwithsecrets.KUBECONFIG_DEV(base64 encoded kubeconfig) for dev deploymentChanges
.github/workflows/deploy-dev.yaml: Removed doctl installation, use kubeconfig secret directlyTest plan
KUBECONFIG_DEVsecret to repo (base64 encoded kubeconfig)devbranch🤖 Generated with Claude Code
Summary by CodeRabbit