1_r/devopsish

1_r/devopsish

54612 bookmarks
Custom sorting
When Cutting Costs, Don’t Lose Sight of Long-Term Organizational Health
When Cutting Costs, Don’t Lose Sight of Long-Term Organizational Health
After three years of adapting to disrupted business conditions due to the pandemic, the aftermath of inflation and fears of recession have leaders scrambling to get budgets in line with slower revenue growth. Riddled with the anxiety of making the wrong choices and having to deliver tough news, leaders are often prone to making short-sighted decisions when cutting costs. And when it comes to sustaining the intended outcomes of cut costs, most organizations are abysmal. Rather than grasping at straws or doing what seems “least painful,” these are the turbulent times when leaders must double down on protecting the long-term aspirations and culture of their organization. If you’re facing the need to tighten your belt, the authors present several ways to trim costs — without sacrificing the long-term health of the company.
·hbr.org·
When Cutting Costs, Don’t Lose Sight of Long-Term Organizational Health
Fedora Asahi Aims To Provide The Fedora Workstation Experience For Apple Silicon Systems
Fedora Asahi Aims To Provide The Fedora Workstation Experience For Apple Silicon Systems
For those wanting to run Linux bare metal on modern Apple Silicon M1/M2 systems, the easiest way to do so is by using the Asahi Linux distribution with its downstream kernel carrying the latest Apple driver enablement patches for the ARM hardware, the specialized installer for safely setting up the Linux distribution on the Apple, and modern package base provided by Arch Linux
·phoronix.com·
Fedora Asahi Aims To Provide The Fedora Workstation Experience For Apple Silicon Systems
It’s imperative
It’s imperative
But this isn’t all about aesthetics; there’s a prime reason why one should avoid whoppers.
·blog.syncpup.com·
It’s imperative
Researcher 'Predicts' Turkey Earthquake 3 Days Prior
Researcher 'Predicts' Turkey Earthquake 3 Days Prior
A Dutch researcher predicted the earthquake which struck Turkey and Syria, just three days before two massive quakes affected the region
·greekreporter.com·
Researcher 'Predicts' Turkey Earthquake 3 Days Prior
The U.S. secretly passed a medical cybersecurity law - Stacey on IoT | Internet of Things news and analysis
The U.S. secretly passed a medical cybersecurity law - Stacey on IoT | Internet of Things news and analysis
Surprise! During the end-of-year rush to pass the federal spending bill, a piece of legislation with more than 4,000 pages apportioning out $1.7 trillion of spending, legislators included a section that helps make connected medical devices more secure. The law requires that any medical device that is connected to the internet get pre-market approval before […]
·staceyoniot.com·
The U.S. secretly passed a medical cybersecurity law - Stacey on IoT | Internet of Things news and analysis
Americans Flunked This Test on Online Privacy
Americans Flunked This Test on Online Privacy
Many consumers want control over their personal details. But few understand how online tracking works, says a new report from the University of Pennsylvania.
·nytimes.com·
Americans Flunked This Test on Online Privacy
Self-hosting Mastodon on AWS using Nomad
Self-hosting Mastodon on AWS using Nomad
With Twitter being a mess at the moment, I decided to try out Mastodon as an alternative. Mastodon is a federated social media platform, built on top of a protocol called ActivityPub. It can be self-hosted, letting you own your data, and I wanted to do so using Nomad as a cluster orchestrator. This post shows how I did it, and will hopefully inspire you to give Mastodon a try if you haven’t already! You can find me on the Fediverse at @carrot@bunny.cloud 🐘.
·carrot.blog·
Self-hosting Mastodon on AWS using Nomad
Blog: k8s.gcr.io image registry will be frozen from the 3rd of April 2023
Blog: k8s.gcr.io image registry will be frozen from the 3rd of April 2023
Authors : Mahamed Ali (Rackspace Technology) The Kubernetes project runs a community-owned image registry called registry.k8s.io to host its container images. On the 3rd of April 2023, the old registry k8s.gcr.io will be frozen and no further images for Kubernetes and related subprojects will be pushed to the old registry. This registry registry.k8s.io replaced the old one and has been generally available for several months. We have published a blog post about its benefits to the community and the Kubernetes project. This post also announced that future versions of Kubernetes will not be available in the old registry. Now that time has come. What does this change mean for contributors: If you are a maintainer of a subproject, you will need to update your manifests and Helm charts to use the new registry. What does this change mean for end users: 1.27 Kubernetes release will not be published to the old registry. Patch releases for 1.24, 1.25, and 1.26 will no longer be published to the old registry from April. Please read the timelines below for details of the final patch releases in the old registry. Starting in 1.25, the default image registry has been set to registry.k8s.io . This value is overridable in kubeadm and kubelet but setting it to k8s.gcr.io will fail for new releases after April as they won’t be present in the old registry. If you want to increase the reliability of your cluster and remove dependency on the community-owned registry or you are running Kubernetes in networks where external traffic is restricted, you should consider hosting local image registry mirrors. Some cloud vendors may offer hosted solutions for this. Timeline of the Changes: k8s.gcr.io will be frozen on the 3rd of April 2023 1.27 is expected to be released on the 12th of April 2023 The last 1.23 release on k8s.gcr.io will be 1.23.18 (1.23 goes EoL before the freeze) The last 1.24 release on k8s.gcr.io will be 1.24.12 The last 1.25 release on k8s.gcr.io will be 1.25.8 The last 1.26 release on k8s.gcr.io will be 1.26.3 What's next Please make sure your cluster does not have dependencies on old image registry. For example, you can run this command to list the images used by pods: kubectl get pods --all-namespaces -o jsonpath = "{.items[*].spec.containers[*].image}" |\ tr -s '[[:space:]]' '\n' |\ sort |\ uniq -c There may be other dependencies on the old image registry. Make sure you review any potential dependencies to keep your cluster healthy and up to date. Acknowledgments Change is hard , and evolving our image-serving platform is needed to ensure a sustainable future for the project. We strive to make things better for everyone using Kubernetes. Many contributors from all corners of our community have been working long and hard to ensure we are making the best decisions possible, executing plans, and doing our best to communicate those plans. Thanks to Aaron Crickenberger, Arnaud Meukam, Benjamin Elder, Caleb Woodbine, Davanum Srinivas, Mahamed Ali, and Tim Hockin from SIG K8s Infra, Brian McQueen, and Sergey Kanzhelev from SIG Node, Lubomir Ivanov from SIG Cluster Lifecycle, Adolfo García Veytia, Jeremy Rickard, Sascha Grunert, and Stephen Augustus from SIG Release, Bob Killen and Kaslin Fields from SIG Contribex, Tim Allclair from the Security Response Committee. Also a big thank you to our friends acting as liaisons with our cloud provider partners: Jay Pipes from Amazon and Jon Johnson Jr. from Google.
·kubernetes.io·
Blog: k8s.gcr.io image registry will be frozen from the 3rd of April 2023
Banning Noncompetes Is Good for Innovation
Banning Noncompetes Is Good for Innovation
A ban on noncompetes, like the one proposed in the U.S. by the Federal Trade Commission, is not just good for workers. It’s good for companies and innovation in the long run. By letting workers share in the benefits of their innovations, noncompetes motivate them to work harder, make it easier for them to start new companies, and make the overall economy more dynamic and competitive.
·hbr.org·
Banning Noncompetes Is Good for Innovation