1_r/devopsish

1_r/devopsish

54563 bookmarks
Custom sorting
Measuring developer productivity? A response to McKinsey
Measuring developer productivity? A response to McKinsey
The consulting firm came up with a methodology they claim can measure software developer productivity. But that measurement comes at a high price – and we offer a more sensible approach.
·newsletter.pragmaticengineer.com·
Measuring developer productivity? A response to McKinsey
Open source licensing, creativity, innovation, freedom
Open source licensing, creativity, innovation, freedom
The definition of open source isn’t arbitrary; it was designed to preserve the rights of those who create open source and codify the responsibilities of those use it. Its hard-won definition deserves defending, even if it is at times inconvenient.
·juliaferraioli.com·
Open source licensing, creativity, innovation, freedom
Choosing a Password Manager
Choosing a Password Manager
Password breaches are a common occurrence, and if you use the same password on every site, that may grant access to bad actors who try out that password elsewhere to get into your accounts. The best way to protect yourself is to use a unique password everywhere (and two-factor authentication,...
·ssd.eff.org·
Choosing a Password Manager
How to Set up Time Machine Server in macOS Ventura or Later
How to Set up Time Machine Server in macOS Ventura or Later
Note: This is an updated version of an article from 2018. With macOS, Apple makes it easy to set up a drive to be a target for other Macs to use with Time Machine. Say you have a Mac mini on your network, and a MacBook Pro. You can hook up an external drive to [...]
·512pixels.net·
How to Set up Time Machine Server in macOS Ventura or Later
*@gmail.com
*@gmail.com
Hi all, just replying to loop in *@outlook.com and *@yahoo.com.
·xkcd.com·
*@gmail.com
The Dark Side of SRE
The Dark Side of SRE
The life of an SRE might seem full of opportunity. But behind the curtain you can often find reality full of chronic stress and career stagnation
·codereliant.io·
The Dark Side of SRE
GRU hacking tools targeting Ukrainian military devices detailed by Five Eyes
GRU hacking tools targeting Ukrainian military devices detailed by Five Eyes
The U.K.'s National Cyber Security Centre and allied agencies issued a technical report detailing "Infamous Chisel," a set of hacking tools that Russia is using against Ukrainian military tablet computers.
·therecord.media·
GRU hacking tools targeting Ukrainian military devices detailed by Five Eyes
Blog: Kubernetes Legacy Package Repositories Will Be Frozen On September 13, 2023
Blog: Kubernetes Legacy Package Repositories Will Be Frozen On September 13, 2023
Authors : Bob Killen (Google), Chris Short (AWS), Jeremy Rickard (Microsoft), Marko Mudrinić (Kubermatic), Tim Bannister (The Scale Factory)On August 15, 2023, the Kubernetes project announced the general availability ofthe community-owned package repositories for Debian and RPM packages availableat pkgs.k8s.io . The new package repositories are replacement for the legacyGoogle-hosted package repositories: apt.kubernetes.io and yum.kubernetes.io .Theannouncement blog post for pkgs.k8s.iohighlighted that we will stop publishing packages to the legacy repositories inthe future.Today, we're formally deprecating the legacy package repositories (apt.kubernetes.ioand yum.kubernetes.io ), and we're announcing our plans to freeze the contents ofthe repositories as of September 13, 2023 .Please continue reading in order to learn what does this mean for you as an user ordistributor, and what steps you may need to take.How does this affect me as a Kubernetes end user?This change affects users directly installing upstream versions of Kubernetes ,either manually by following the officialinstallation andupgrade instructions, orby using a Kubernetes installer that's using packages provided by the Kubernetesproject.This change also affects you if you run Linux on your own PC and have installed kubectl using the legacy package repositories .We'll explain later on how to check if you're affected.If you use fully managed Kubernetes, for example through a service from a cloudprovider, you would only be affected by this change if you also installed kubectlon your Linux PC using packages from the legacy repositories. Cloud providers aregenerally using their own Kubernetes distributions and therefore they don't usepackages provided by the Kubernetes project; more importantly, if someone else ismanaging Kubernetes for you, then they would usually take responsibility for that check.If you have a managed control planebut you are responsible for managing the nodes yourself , and any of those nodes run Linux,you should check whether you are affected.If you're managing your clusters on your own by following the official installationand upgrade instructions, please follow the instructions in this blog post to migrateto the (new) community-owned package repositories.If you're using a Kubernetes installer that's using packages provided by theKubernetes project, please check the installer tool's communication channels forinformation about what steps you need to take, and eventually if needed, follow upwith maintainers to let them know about this change.How does this affect me as a Kubernetes distributor?If you're using the legacy repositories as part of your project (e.g. a Kubernetesinstaller tool), you should migrate to the community-owned repositories as soon aspossible and inform your users about this change and what steps they need to take.Timeline of changes15th August 2023:Kubernetes announces a new, community-managed source for Linux software packages of Kubernetes components31st August 2023:(this announcement) Kubernetes formally deprecates the legacypackage repositories13th September 2023 (approximately):Kubernetes will freeze the legacy package repositories,(apt.kubernetes.io and yum.kubernetes.io ).The freeze will happen immediately following the patch releases that are scheduled for September, 2023.The Kubernetes patch releases scheduled for September 2023 (v1.28.2, v1.27.6,v1.26.9, v1.25.14) will have packages published both to the community-owned andthe legacy repositories.We'll freeze the legacy repositories after cutting the patch releases for Septemberwhich means that we'll completely stop publishing packages to the legacy repositoriesat that point.For the v1.28, v1.27, v1.26, and v1.25 patch releases from October 2023 and onwards,we'll only publish packages to the new package repositories (pkgs.k8s.io ).What about future minor releases?Kubernetes 1.29 and onwards will have packages published only to thecommunity-owned repositories (pkgs.k8s.io ).Can I continue to use the legacy package repositories?The existing packages in the legacy repositories will be available for the foreseeablefuture. However, the Kubernetes project can't provide any guarantees on how longis that going to be. The deprecated legacy repositories, and their contents, mightbe removed at any time in the future and without a further notice period.The Kubernetes project strongly recommends migrating to the new community-ownedrepositories as soon as possible .Given that no new releases will be published to the legacy repositories after the September 13, 2023cut-off point, you will not be able to upgrade to any patch or minor release made from that date onwards.Whilst the project makes every effort to release secure software, there may oneday be a high-severity vulnerability in Kubernetes, and consequently an importantrelease to upgrade to. The advice we're announcing will help you be as prepared forany future security update, whether trivial or urgent.How can I check if I'm using the legacy repositories?The steps to check if you're using the legacy repositories depend on whether you'reusing Debian-based distributions (Debian, Ubuntu, and more) or RPM-based distributions(CentOS, RHEL, Rocky Linux, and more) in your cluster.Run these instructions on one of your nodes in the cluster.Debian-based Linux distributionsThe repository definitions (sources) are located in /etc/apt/sources.list and /etc/apt/sources.list.d/on Debian-based distributions. Inspect these two locations and try to locate apackage repository definition that looks like:deb [signed-by=/etc/apt/keyrings/kubernetes-archive-keyring.gpg] https://apt.kubernetes.io/ kubernetes-xenial mainIf you find a repository definition that looks like this, you're using the legacy repository and you need to migrate.If the repository definition uses pkgs.k8s.io , you're already using thecommunity-hosted repositories and you don't need to take any action.On most systems, this repository definition should be located in/etc/apt/sources.list.d/kubernetes.list (as recommended by the Kubernetesdocumentation), but on some systems it might be in a different location.If you can't find a repository definition related to Kubernetes, it's likely that youdon't use package managers to install Kubernetes and you don't need to take any action.RPM-based Linux distributionsThe repository definitions are located in /etc/yum.repos.d if you're using theyum package manager, or /etc/dnf/dnf.conf and /etc/dnf/repos.d/ if you're usingdnf package manager. Inspect those locations and try to locate a package repositorydefinition that looks like this:[kubernetes]name=Kubernetesbaseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-\$basearchenabled=1gpgcheck=1gpgkey=https://packages.cloud.google.com/yum/doc/rpm-package-key.gpgexclude=kubelet kubeadm kubectlIf you find a repository definition that looks like this, you're using the legacy repository and you need to migrate.If the repository definition uses pkgs.k8s.io , you're already using thecommunity-hosted repositories and you don't need to take any action.On most systems, that repository definition should be located in /etc/yum.repos.d/kubernetes.repo(as recommended by the Kubernetes documentation), but on some systems it might bein a different location.If you can't find a repository definition related to Kubernetes, it's likely that youdon't use package managers to install Kubernetes and you don't need to take any action.How can I migrate to the new community-operated repositories?For more information on how to migrate to the new communitymanaged packages, please refer to theannouncement blog post for pkgs.k8s.io .Why is the Kubernetes project making this change?Kubernetes has been publishing packages solely to the Google-hosted repositorysince Kubernetes v1.5, or the past seven years! Following in the footsteps ofmigrating to our community-managed registry, registry.k8s.io , we are now migrating theKubernetes package repositories to our own community-managed infrastructure. We’rethankful to Google for their continuous hosting and support all these years, butthis transition marks another big milestone for the project’s goal of migratingto complete community-owned infrastructure.Is there a Kubernetes tool to help me migrate?We don't have any announcement to make about tooling there. As a Kubernetes user, youhave to manually modify your configuration to use the new repositories. Automatingthe migration from the legacy to the community-owned repositories is technicallychallenging and we want to avoid any potential risks associated with this.AcknowledgmentsFirst of all, we want to acknowledge the contributions from Alphabet. Staff at Googlehave provided their time; Google as a business has provided both the infrastructureto serve packages, and the security context for giving those packages trustworthydigital signatures.These have been important to the adoption and growth of Kubernetes.Releasing software might not be glamorous but it's important. Many people withinthe Kubernetes contributor community have contributed to the new way that we, as aproject, have for building and publishing packages.And finally, we want to once again acknowledge the help from SUSE. OpenBuildService,from SUSE, is the technology that the powers the new community-managed package repositories.
·kubernetes.io·
Blog: Kubernetes Legacy Package Repositories Will Be Frozen On September 13, 2023
Finally! | ReiserFS Officially Declared "Obsolete"
Finally! | ReiserFS Officially Declared "Obsolete"
As part of updates to the older file-system drivers for Linux 6.6, the ReiserFS file-system is no longer marked as 'Supported' but is officially treated as 'Obsolete' within the Linux kernel.
·phoronix.com·
Finally! | ReiserFS Officially Declared "Obsolete"
Visual Studio for Mac Retirement Announcement - Visual Studio Blog
Visual Studio for Mac Retirement Announcement - Visual Studio Blog
Today we are announcing the retirement of the Visual Studio for Mac IDE. Visual Studio for Mac 17.6 will continue to be supported for another 12 months, until August 31st, 2024, with servicing updates for security issues and updated platforms from Apple.
·devblogs.microsoft.com·
Visual Studio for Mac Retirement Announcement - Visual Studio Blog