!!! DEVELOPMENT STOPPED !!! Switches kube config context
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
| Version | Status |
|---|---|
| 29 | Rejected |
| 28 | Rejected |
| 27 | Active |
| 26 | Active |
| 25 | Active |
| 24 | Rejected |
| 23 | Active |
| 22 | Rejected |
| 21 | Active |
| 20 | Active |
| 19 | Active |
| 18 | Rejected |
| 17 | Rejected |
| 16 | Waiting for author |
| 15 | Active |
| 14 | Active |
| 13 | Inactive |
| 12 | Active |
| 11 | Active |
| 10 | Active |
| 9 | Active |
| 8 | Active |
| 7 | Active |
| 6 | Active |
| 5 | Rejected |
| 4 | Active |
| 3 | Active |
| 2 | Active |
| 1 | Waiting for author |
All monitors are canceled in kubeIndicator.js at line 135. Why the timer cancelation is needed?
Because timeouts can get delayed and get triggered after disable in the lock screen. That can lead to security flaw.
[depricated] Kube Config