kubectl-aks
kubectl-aks copied to clipboard
Azure
Azure Kubernetes Service (AKS) kubectl plugin
Add test for run-command.md. In order to test it locally you need to write an INI file at `docs/run-command.ini` with sample: ``` → cat docs/run-command.ini.sample mySubID = mySubID myRG =...
We use the "github.com/sirupsen/logrus" for logging. The `--verbose` should set the log level to debug: `logrus.SetLevel(logrus.DebugLevel)`.
_Originally posted by @blanquicet in https://github.com/Azure/kubectl-aks/pull/52#discussion_r1478434793_: If we check, we always execute `config show` after a `config import`. I started thinking that we should automatically print the imported data in...
## Current situation It is only possible to run `check-apiserver-connectivity` on one single node: ```bash kubectl aks check-apiserver-connectivity --node aks-agentpool-27170680-vmss000000 ``` Or: ```bash kubectl aks config import kubectl aks config...
## Current situation Users have to set the node and set it as current node: ```bash $ kubectl aks config set-node node1 --subscription mySubID --node-resource-group myRG --vmss myVMSS --instance-id myInstanceID1...
## Current situation We must specify every time the subscription ID. Given that usually users work in one single subscription, let's allow to set it once and forever. ## Ideal...
## Current situation Currently, the outcome of the `check-apiserver-connectivity` command is mainly `succeeded` or `failed`: ``` $ kubectl aks check-apiserver-connectivity --node aks-agentpool-27170680-vmss000000 Running... Connectivity check: succeeded $ echo $? 0...
## Current situation Currently, the `check-apiserver-connectivity` command requests users to specify the node where the check will be performed: ``` $ kubectl get nodes NAME STATUS ROLES AGE VERSION aks-agentpool-27170680-vmss000000...
## Current situation `kubectl-aks` does not provide any way to copy files into nodes. ## Ideal future situation Investigate if it could be useful for users to have a command...
## Current situation `kubectl aks` doesn't provide a way to ssh into the nodes (VMSS instances) of an AKS cluster. ## Ideal future situation Investigate if how we can implement...