almartino opened a new issue, #140: URL: https://github.com/apache/openserverless/issues/140
- [x] I have searched the [issues](https://github.com/apache/openserverless/issues) of this repository and believe that this is not a duplicate. ### I. Issue Description The `devcluster` uninstall command makes a problematic assumption, specifically in its `rm` operation: `- rm "$KUBECONFIG" "$OPS_TMP/kind.kubeconfig"`. This led to the unintended deletion of the user's `~/.kube/config` file, which contained configurations for production clusters. This issue occurred after an interrupted `devcluster` installation, leaving the system in an inconsistent state. ### II. Steps to Reproduce 1. Initiate the `devcluster slim` installation. 2. Interrupt the installation process before it fully completes. 3. Execute the `devcluster` uninstall command. 4. Observe the removal of `~/.kube/config`. ### III. Expected Behavior The `devcluster` uninstall command should: * Safely remove only files related to the `devcluster` installation. * Avoid making assumptions that could lead to the deletion of critical user configuration files, such as `~/.kube/config`. * Handle interrupted installations gracefully without impacting existing system configurations. * Ideally, prompt the user for irreversible actions like deleting `KUBECONFIG` or backup the kubeconfig when the variable `$KUBECONFIG` target the `~/.kube/config` file. ### IV. Environment * **K8S Runtime and version:** - * **OPS CLI version:** 0.1.0-2409121919.dev * **Others:** OPS_BRANCH=main (commit sha `f512dcb494cf8ee0446c92b5a525ce3ca9b7da69`) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@openserverless.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
