Fedora / Red Hat / IBM Leftovers
-
Fedora Hatch Cork 2022 - Fedora Community Blog
Fedora Hatch Cork was a small, local one day mini-conference. Fedora Project contributors were welcome to attend, learn about the project and connect with other contributors. There were several Fedora-related sessions, followed by a social activity in the evening. The event was held in the Red Hat office in Cork which was recently renovated.
The day opened with an icebreaker event called “Faces”. Attendees paired up with somebody nearby and swapped sheets of paper to draw a feature of the person they swapped with, starting with the eyes. It was a great exercise to meet new people at the event. It also allowed me to absolutely butcher some peoples’ great drawings!
-
A developer’s guide to Kubernetes storage concepts | Red Hat Developer
This second article continues a series discussing Kubernetes storage concepts. I will define the concepts of volumes, persistent volume claims, and storage classes, and why they should matter to a developer. I will also explain how persistent volumes and storage provisioners enable system administrators to manage storage for a Kubernetes cluster while offering developers self-service to storage. You will also discover the special abilities of stateful sets.
-
Why CSI drivers are essential in Kubernetes storage | Red Hat Developer
This article is the third and final part of the series about Kubernetes storage concepts. I will explain how Container Storage Interface (CSI) drivers enable advanced storage features necessary for production environments and CI/CD pipelines. This article also underscores the need for storage products designed for Kubernetes versus storage designed for traditional physical and virtual data centers or Infrastructure-as-a-Service (IaaS) clouds.
-
8 ways to get out of a career rut
The pandemic was difficult to navigate for most of us, but if we can try to identify something positive that transpired as a result, it allowed (or forced) time for reflection and re-evaluation.
Consider the millennial who felt stuck at a small company with no room for growth. Or the older generation of workers who thought they should retire early because the future was so uncertain and accepting a complete shift to digital felt daunting. For Gen Z, the prospect of never meeting managers or colleagues – because of virtual interviews and remote jobs – was foreign and left some without a sense of belonging.
Not only were we physically absent from workspaces, but many of us also struggled mentally with the sudden, enormous changes to our daily routines and goals. It became a time of contemplation, where many professionals began reassessing their careers (and lives). And the realization for many? They felt stuck.
-
How Kubernetes improves developer agility | Red Hat Developer
This article is the first in a series that explains Kubernetes storage on a high level. In the series, I provide information for a programmer or software architect to decide which types of storage meet the requirements for their applications running on Kubernetes. This series provides links to help you go deeper into your chosen technologies but does not dig into YAML syntax or Kubernetes APIs. Whether a novice or experienced with Kubernetes, this overview can guide you toward a storage architecture that is right for your application.
-
How to make your APIs more discoverable | Red Hat Developer
API discoverability is a key aspect of any API management initiative. The discoverability of an API directly impacts its adoption and usage. A typical big enterprise with multiple development teams might build hundreds of APIs that they would want to reuse internally or share with partners that build complementary applications. If the teams cannot discover existing APIs, they might build a new API with the same functionality, which leads to duplication of efforts and underutilization of the existing API. It is also an unscalable practice to contact the API developer each time someone wants to use the API.
There needs to be a better and more hands-off way for internal teams and partners to discover and understand the usage of these APIs without directly contacting the developers who built them. API discoverability does not just mean making it easy to find an API by providing an inventory (though this is the first and most important step you should take). It should also address some key aspects that are important for an API consumer, such as understanding the API through documentation, request and response format, sign-up options, and the business terms and conditions (in case of a partner) of using the API.