Repository navigation
v2.1.0
#3007
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The first feature release after v2.0.0, with the security fixes of Node v24.22.3.
What's new:
v2.1.0 brings combined logs for the pods of a workload, the certificate details of secrets, the mutating admission policies, and two new members of the extension API: a credential store encrypted with the secret store of the system, and the certificate view of secrets. It also fixes the connection to clusters whose kubeconfig has a colon in its file name or is written in UTF-16, Windows shells given by name, and several issues of the logs, the sidebar and the details.
New Features
kubectl apply, as YAML. The default container of a pod, from thekubectl.kubernetes.io/default-containerannotation, is marked in the pod details, the pod menu and the logs, and is the one Shell, Attach and Logs open. See Show the default container and the last applied configuration from the kubectl annotations #2988, Show the default container and the last applied configuration from the kubectl annotations #2989containers:orvolumes:, as well as each item of the list. See Collapse Yaml when editing #2524, Fold a YAML key together with the sequence written at its indentation #2996Extensions API
Common.Credentials.forExtension(this)keeps the tokens and passwords of an extension encrypted at rest with ElectronsafeStorage, in both processes, bound to the extension instance and removed when the extension is uninstalled. It promises encryption at rest only: it is not a boundary between extensions. On Linux it is available with libsecret or KWallet, and a desktop Electron does not recognise can name one with--password-store. See the contract. See Add Common.Credentials, an encrypted credential store for extensions #2782, Keep extension credentials encrypted at rest with safeStorage: Common.Credentials #3011, Keep extension credentials encrypted at rest with safeStorage: Common.Credentials #3012Renderer.Component.SecretCertificatesrenders the certificate section of the secret details for the data of any secret, such as thecertSecretRefof a Flux source, with the parsing done by the host. See Export the certificate section of secrets to extensions as Renderer.Component.SecretCertificates #3008, Export the certificate section of secrets to extensions as Renderer.Component.SecretCertificates #3010orderNumberofclusterPageMenusorders the menus of an extension, and their children, in the sidebar again. See clusterPageMenus.orderNumber is ignored by the v2 sidebar registrator #2959, Order the sidebar menus of an extension by their declared order numbers #2987K8sApihas theMutatingAdmissionPolicyandMutatingAdmissionPolicyBindingmodels andNode.getKernelVersion().isAllowedResourcefinds the admissionregistration resources, which it looked up under a wrong API group before. See Add Kernel Version column to the Nodes list #2411, Add MutatingAdmissionPolicy and MutatingAdmissionPolicyBinding #2511Improvements
Fixes
libXScrnSaver, which these distributions do not provide and nothing in Freelens uses. The DEB package no longer requireslibxss1for the same reason. See Drop the unused libXss requirement of the RPM and DEB packages #2896context ... does not exist. See Bug: Kubeconfig file with colon (:) in filename causes context initialization failure on macOS #2895, Pass the kubeconfig to freelens-k8s-proxy as one file #2919wsl.exe, starts when Freelens runs fromC:\Windows\System32, instead of failing withFile not found. See Settings, Terminal Path: PATH ENV not longer recognized #2918, Look up a Windows shell given by name on PATH before starting it #2941Security
http2andtls, nine of them rated High. The main process uses both in its connections to the clusters. See #XXXXUpdates
All reactions