Fedora / Red Hat Leftovers
-
DevOps: 3 steps to plan and execute a successful project | The Enterprisers Project
While DevOps isn’t a new phrase or idea to anyone in the tech industry, it has become a buzzword in recent years. Such is its popularity that it is now crucial to understand how best to structure and deploy a DevOps team, and there are several different views and methodologies on this.
-
Community Blog monthly summary: December 2022 - Fedora Community Blog
In December, we published 22 posts. The site had 6,642 visits from 3,538 unique viewers. 911 visits came from search engines, while 495 came from Fedora Magazine and 64 came from Twitter.
-
How libabigail 2.2 supports multiple debugging formats | Red Hat Developer
Numerous debugging formats must be supported on Linux systems for C and C++ programs. This article describes the formats supported by libabigail, a tool for creating and unpacking debugging formats, and explains how the redesign of libabigail supports multiple formats.
-
How to use Fabric8 Kubernetes Client | Red Hat Developer
While working with Kubernetes Client, you would mostly be working with standard Kubernetes resources whose model is provided by the library itself. However, it’s not always possible to provide a concrete model type while accessing a Kubernetes API object (e.g. in case of Custom Resources). Fabric8 Kubernetes Client’s GenericKubernetesResource API can be used in these scenarios. It allows objects that do not have java POJOs registered to be manipulated generically.
-
Kubernetes 1.26: Retroactive Default StorageClass | Kubernetes
The v1.25 release of Kubernetes introduced an alpha feature to change how a default StorageClass was assigned to a PersistentVolumeClaim (PVC). With the feature enabled, you no longer need to create a default StorageClass first and PVC second to assign the class. Additionally, any PVCs without a StorageClass assigned can be updated later. This feature was graduated to beta in Kubernetes 1.26.
You can read retroactive default StorageClass assignment in the Kubernetes documentation for more details about how to use that, or you can read on to learn about why the Kubernetes project is making this change.