[WIP] feat: decouple the kubeconfig#3722
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gauron99 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
4697ec7 to
f0c7baf
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #3722 +/- ##
==========================================
- Coverage 56.92% 56.06% -0.87%
==========================================
Files 181 183 +2
Lines 20933 21379 +446
==========================================
+ Hits 11916 11986 +70
- Misses 7809 8168 +359
- Partials 1208 1225 +17
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
f0c7baf to
325154a
Compare
325154a to
5aba827
Compare
Current scope
f.Local.Authis a list but we do linear search for both Setting and Getting so the other input would be "dead code"--cluster=can be used to "clear" the stored cluster url and re-used the active context from kubeconfigFlow
deployis unchanged functionally ->func deployfirst time see that no cluster is set, uses active kubeconfig context (just as now in main) and tries that as fallback method. Extra addition is on successful deploy this url + creds will be stored in-house.func/local.yamlfile to be re-used on further deployments if untouched therefore you can freely switch contexts around and your function will still point to that initially deployed cluster with creds (now you dont even need kubeconfig at all)Changes
cluster access without kubeconfig
.func/local.yaml — subsequent deploys work without kubeconfig
credential resolution
/kind enhancement
Release Note