# Operator Published articles for Operator. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator DevFeed: [Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator]() Original publisher: [Read original article]() Author: Anil Joshi Published: 2026-09-17T06:43:32Z Content type: tutorial Language: en Sources: [Blog - Percona]() Topics: [Replication](), [export](), [Percona Server for MySQL](), [configuration](), [Server](), [Kubernetes](), [Database]() Tags: [cloud](), [configuration](), [database-trends](), [featured](), [innodb-clusterset](), [insight-for-dbas](), [kubernetes](), [kubernetes-operators](), [mysql](), [mysql-group-replication](), [mysql-high-availability](), [mysql-replication](), [open-source](), [operator](), [percona-kubernetes-operators](), [percona-operator-for-mysql](), [percona-server-for-mysql](), [percona-software](), [replication](), [uncategorized](), [yaml]() ### AI overview This tutorial explains how to configure cross-site replication between two Percona Operator for MySQL clusters to create a ClusterSet environment for disaster recovery and switchover between data-center and disaster-recovery members. It covers deploying the clusters, retrieving endpoints and cluster names, transferring credentials, and initializing the DR cluster. ### Source excerpt A while ago, we discussed the cross-site replication feature of the Percona PXC operator. Recently, a similar cross-site replication feature was introduced in the Percona (PS MySQL) operator v1.2.0, a topology based on Group Replication/InnoDB Cluster. In this blog post, we will explore how to add a DR Cluster to an existing DC Cluster to ... Continued The post Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator appeared first on Percona. ## Percona Operator for PostgreSQL 3.1.0: Transparent Data Encryption, Logical Replicas, and Persistent Logging DevFeed: [Percona Operator for PostgreSQL 3.1.0: Transparent Data Encryption, Logical Replicas, and Persistent Logging]() Original publisher: [Read original article]() Author: Slava Sarzhan Published: 2026-09-09T16:08:31Z Content type: release Language: en Sources: [Blog - Percona]() Topics: [PostgreSQL](), [Encryption](), [Logging](), [Kubernetes](), [Open Source]() Tags: [cloud](), [encryption](), [hashicorp-vault](), [kubernetes](), [logging](), [open-source](), [operator](), [percona](), [percona-operator-for-postgresql](), [postgresql](), [release](), [replication](), [security](), [slavasarzhan-pg]() ### AI overview Percona Operator for PostgreSQL 3.1.0 adds transparent data encryption with pg_tde, logical replicas for read-only workloads, and persistent logging across Pod restarts. The release also adds official RKE2 support and full ARM64 images. ### Source excerpt Percona Operator for PostgreSQL 3.1.0 takes on three things that decide whether a PostgreSQL platform passes review: is the data encrypted at rest, can it serve reads without straining the primary, and are the logs there when you need them. This release answers all three inside the custom resource, so none of them is a ... Continued The post Percona Operator for PostgreSQL 3.1.0: Transparent Data Encryption, Logical Replicas, and Persistent Logging appeared first on Percona. ## Deploy NeMo Guardrails on Red Hat OpenShift AI DevFeed: [Deploy NeMo Guardrails on Red Hat OpenShift AI]() Original publisher: [Read original article]() Author: Rob Geada Published: 2026-09-09T15:05:01Z Content type: tutorial Language: en Sources: [Red Hat](), [Red Hat Developer]() Topics: [NeMo](), [Deployment](), [ai safety](), [Open Source](), [prompt injection]() Tags: [article](), [deployment](), [developer](), [how-to](), [nemo](), [open-source](), [operator](), [platform](), [prompt-injection](), [red-hat](), [safety](), [security]() ### AI overview This tutorial explains how to deploy an evaluated NeMo Guardrails configuration on a Red Hat OpenShift AI cluster. It covers prerequisites, creating a ConfigMap from the configuration files, and creating a NeMoGuardrails custom resource for a managed deployment. ### Source excerpt This is part 3 in a 3-part series on local guardrail development and evaluation. In the 1st article, I looked at how to design and develop a guardrail configuration on a local machine, and then tried some manual testing. In the 2nd article, I explored how to rigorously test a guardrail against popular large-scale risk datasets. The post Deploy NeMo Guardrails on Red Hat OpenShift AI appeared first on Red Hat Developer. ## Highly Available PostgreSQL on Kubernetes in 10 Minutes DevFeed: [Highly Available PostgreSQL on Kubernetes in 10 Minutes]() Original publisher: [Read original article]() Author: Hans-Jürgen Schönig Published: 2026-08-18T05:07:31Z Content type: tutorial Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [PostgreSQL](), [Kubernetes](), [postgresql clusters](), [Database](), [Replication]() Tags: [failover](), [health-checks](), [how-to](), [kubernetes](), [operator](), [patroni](), [pg-operator](), [postgresql](), [postgresql-on-cloud](), [replication](), [tutorial](), [yaml]() ### AI overview This tutorial demonstrates how to deploy a highly available PostgreSQL cluster on Kubernetes with the CYBERTEC PG Operator. Using a 14-line YAML configuration on minikube, it shows leader election, streaming replication, health checks, automatic failover, and read-only replica behavior. It also explains how anti-affinity must be disabled for the single-node minikube setup but should remain enabled on multi-node production clusters. ### Source excerpt This is a detailed blog post about PostgreSQL in Kubernetes, using PG Operator. The post Highly Available PostgreSQL on Kubernetes in 10 Minutes appeared first on CYBERTEC PostgreSQL | Services & Support. ## Introducing the CYBERTEC PG Operator DevFeed: [Introducing the CYBERTEC PG Operator]() Original publisher: [Read original article]() Author: Hans-Jürgen Schönig Published: 2026-08-12T09:05:41Z Content type: release Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [Kubernetes](), [PostgreSQL](), [Replication](), [Open Source]() Tags: [clusters](), [failover](), [kubernetes](), [news](), [open](), [open-source](), [operator](), [pg-operator](), [postgresql](), [postgresql-on-cloud](), [replication]() ### AI overview CYBERTEC introduces an open-source Kubernetes operator for PostgreSQL. The CYBERTEC PG Operator provides PostgreSQL lifecycle management and supports Multi-site Clusters, including cross-site replication and automated failover across multiple Kubernetes locations. ### Source excerpt CYBERTEC PG Operator is an open-source Kubernetes operator for PostgreSQL, with Multi-site Clusters for cross-site replication and automated failover. The post Introducing the CYBERTEC PG Operator appeared first on CYBERTEC PostgreSQL | Services & Support. ## Reaching 90+ internet exchanges as a one-person network DevFeed: [Reaching 90+ internet exchanges as a one-person network]() Original publisher: [Read original article]() Author: Bastiaan Brink Published: 2026-05-24T00:00:00Z Content type: article Language: en Sources: [AS215248 - Notes]() Topics: [Internet](), [Network](), [Hardware]() Tags: [bgp](), [hardware](), [hobby](), [internet](), [ipv6](), [irr](), [network](), [operator](), [peering](), [personal](), [remote-peering](), [rpki]() ### AI overview This article explains how the one-person network AS215248 participates in more than 90 internet exchanges across two dozen countries using hardware in Amsterdam and remote peering. It describes an open peering policy, IPv6 support, and route validation with RPKI and IRR. ### Source excerpt A hobby AS doesn't need a rack in every city. A little hardware in Amsterdam plus remote peering goes a surprisingly long way. ## Walking Through an Unplanned Failover: SQL Server Availability Groups on Kubernetes DevFeed: [Walking Through an Unplanned Failover: SQL Server Availability Groups on Kubernetes]() Original publisher: [Read original article]() Author: Anthony Nocentino Published: 2026-04-19T15:00:00Z Content type: tutorial Language: en Sources: [Kubernetes on Anthony Nocentino's Blog]() Topics: [sql-server](), [Availability](), [Kubernetes](), [Databases]() Tags: [automatic](), [availability-groups](), [container](), [containers](), [crash](), [database](), [failover](), [kubernetes](), [load](), [open-source](), [operator](), [recovery](), [sql-server](), [test]() ### AI overview This walkthrough tests unplanned SQL Server Availability Group failover on Kubernetes by force-deleting the current primary pod under idle and sustained HammerDB TPC-C load. Across six force-deletes, the operator automatically promoted new primaries and restored all three replicas, with the article examining detection, recovery behavior, logs, and timing. ### Source excerpt In my planned failover walkthrough, I showed what happens when you deliberately move the primary role to another replica. That's the easy case. Now I want to show what happens when the primary pod just disappears unexpectedly, like during a node failure or a container crash. No graceful shutdown, no demotion, just gone. I ran two test scenarios, each cycling the primary role across all three pods by force-deleting the current primary three times in a row. First, a 5GB TPC-C database idle. Then, that same 5GB database under sustained HammerDB TPC-C load. Six force-deletes total, six successful automatic failovers. I'll walk through the error log from the promoted replica, the operator's detection and recovery behavior, and the full timing data. ## Walking Through a Planned Failover: SQL Server Always On Availability Groups on Kubernetes DevFeed: [Walking Through a Planned Failover: SQL Server Always On Availability Groups on Kubernetes]() Original publisher: [Read original article]() Author: Anthony Nocentino Published: 2026-04-19T05:00:00Z Content type: tutorial Language: en Sources: [Kubernetes on Anthony Nocentino's Blog]() Topics: [sql-server](), [Kubernetes](), [Availability]() Tags: [availability-groups](), [containers](), [failover](), [kubernetes](), [open-source](), [operator](), [sql-server]() ### AI overview A walkthrough of planned failover rotation for a three-replica SQL Server Availability Group managed by sql-on-k8s-operator on Kubernetes. It examines SQL Server error logs, operator reconciliation behavior, and timing under both an idle database and a sustained TPC-C workload. ### Source excerpt When building the sql-on-k8s-operator, I wanted to make sure it could handle both planned and unplanned failovers. The easy case is a planned failover, where you deliberately move the primary role to another replica. The harder case is an unplanned failover, where the primary pod just disappears. The operator needs to handle both. I recently ran a full planned failover rotation on a three-replica SQL Server Availability Group managed by sql-on-k8s-operator, and I want to show you exactly what happens inside SQL Server and the operator during each hop. If you've been following my Introducing the SQL Server on Kubernetes Operator post, this is the logical next step: what does the error log actually look like during a planned failover, what does the operator do in response, and how long does the whole thing take? ## Introducing the SQL Server on Kubernetes Operator DevFeed: [Introducing the SQL Server on Kubernetes Operator]() Original publisher: [Read original article]() Author: Anthony Nocentino Published: 2026-04-12T05:00:00Z Content type: tutorial Language: en Sources: [Kubernetes on Anthony Nocentino's Blog]() Topics: [Kubernetes](), [sql-server](), [Availability](), [Disaster Recovery](), [Open Source]() Tags: [automated](), [automatic](), [availability](), [availability-groups](), [containers](), [disaster-recovery](), [failover](), [high-availability](), [kubernetes](), [open-source](), [operator](), [sql-server]() ### AI overview This tutorial introduces sql-on-k8s-operator, an open-source Kubernetes operator for managing SQL Server workloads. It addresses high availability and disaster recovery by automating lifecycle management, failover, and Always On Availability Group setup, and demonstrates deployment with custom resources. ### Source excerpt Are you considering replatforming your SQL Server workload due to recent vendor changes, but still need high availability and disaster recovery? You're not alone. One of the challenges with running SQL Server on Kubernetes is that there's no Kubernetes operator available. That means no automated lifecycle management, no automatic failover, and no standard way to bootstrap an Always On Availability Group on Kubernetes. I'm excited to share it today as an open-source project: sql-on-k8s-operator. Let's go. ## wasmCloud v2.0 is here DevFeed: [wasmCloud v2.0 is here]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-03-23T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [wasm](), [WebAssembly](), [Cloud Native Ecosystem](), [Kubernetes](), [Command-line interface](), [Containers](), [Development]() Tags: [cli](), [cloud-native](), [containers](), [go](), [kubernetes](), [native](), [operator](), [rust](), [typescript](), [vendor-lock-in](), [wasi](), [wasm](), [wasm-components](), [wasmcloud](), [webassembly]() ### AI overview wasmCloud v2.0 is a redesigned platform for deploying WebAssembly workloads across clouds, Kubernetes clusters, datacenters, and edge locations. The release introduces a simplified runtime architecture, Kubernetes-native scheduling, Wasm Shell, a workload API, and a Kubernetes Operator. ### Source excerpt wasmCloud v2.0 is a reimagining of the wasmCloud platform: Kubernetes-native, radically simplified, and more powerful than ever. ## New Keycloak Maintainer: Steven Hawkins DevFeed: [New Keycloak Maintainer: Steven Hawkins]() Original publisher: [Read original article]() Author: Stian Thorgersen Published: 2026-01-06T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak]() Tags: [bugs](), [community](), [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [operator](), [saml](), [sso]() ### AI overview Keycloak announces Steven Hawkins as an official maintainer, recognizing his contributions, Operator expertise, community support, bug fixes, and work improving the distribution. ### Source excerpt Although Steven has only been on the Keycloak team for a relatively short period of time he's managed to get the #15 place as the top contributor overall. Now, if you narrow that to the last two years he's in #3rd place. Steven is the go-to guy when it comes to the Operator where his knowledge is above most. He's also regularly helping out the community, whether joining discussions, fixing bugs, or just generally making our distribution better for everyone. Congratulations to Steven becoming an official Keycloak Maintainer. ## Distribution Survey DevFeed: [Distribution Survey]() Original publisher: [Read original article]() Author: Keycloak Cloud Native Team Published: 2025-12-19T00:00:00Z Content type: news Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Deployment](), [container images](), [Zip](), [Cloud]() Tags: [cloud-native](), [container-images](), [deployment](), [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [operator](), [requirements](), [saml](), [sso](), [zip]() ### AI overview Keycloak's Cloud Native Team is asking users to share their preferences and requirements for distributing and deploying Keycloak through the Operator, container images, or ZIP files. The survey focuses on how distribution choices affect deployment lifecycle concerns such as upgrades, scaling, and configuration. ### Source excerpt The different ways of distribution - be it the Operator, container images, or plain ZIP file - play a pivotal role in all Keycloak deployments. It is often the first touchpoint for users and sets the tone for their overall experience. The selected distribution method then affects the whole lifecycle of the deployment - upgrades, scaling, configuration, and more. As we continue to evolve Keycloak to better serve cloud native environments, we are seeking your valuable input to understand your preferences and requirements regarding Keycloak distribution and deployment methods. Help us shape the cloud native future of Keycloak by participating in our survey! You can find the survey here. ## Announcing the Apollo GraphOS Operator in Public Preview DevFeed: [Announcing the Apollo GraphOS Operator in Public Preview]() Original publisher: [Read original article]() Author: Josh Lambert Published: 2025-08-05T06:00:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [Kubernetes](), [API Platform](), [Amazon API Gateway](), [GitOps](), [Deployment](), [observability]() Tags: [announcement](), [api](), [api-management](), [api-platform](), [apollo](), [argo-cd](), [datadog](), [declarative](), [deployment](), [gitops](), [graphos](), [graphql](), [kubernetes](), [observability](), [operator](), [preview]() ### AI overview Apollo announced the Apollo GraphOS Operator in public preview. The Kubernetes operator is designed to help teams manage GraphQL deployments, including development environments, progressive production rollouts, rollbacks, monitoring, and declarative or GraphOS Studio-based management. ### Source excerpt Simplifying GraphQL API Management on Kubernetes As GraphQL adoption accelerates within organizations, so too does the need for a scalable, reliable API platform that empowers your developers and accelerates innovation. Today, we're excited to introduce in public preview the Apollo GraphOS Operator: the best way to manage GraphQL deployments within Kubernetes. ## Manage your subgraphs and supergraphs as Kubernetes-native resources DevFeed: [Manage your subgraphs and supergraphs as Kubernetes-native resources]() Original publisher: [Read original article]() Author: Nicolas Moutschen Published: 2025-08-05T06:00:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [Kubernetes](), [GraphQL]() Tags: [announce](), [announcement](), [declarative](), [gitops](), [graphos](), [graphql](), [kubernetes](), [operator](), [preview]() ### AI overview Apollo announces the public preview of the Apollo GraphOS Operator, which manages subgraphs and supergraphs as declarative, Kubernetes-native resources. The article describes its Custom Resource Definitions for defining subgraphs, composing supergraph schemas, and deploying GraphOS Routers. ### Source excerpt The Kubernetes ecosystem has evolved to provide powerful declarative resource management for applications, services, and infrastructure. Today, we're excited to announce the public preview of the Apollo GraphOS Operator, bringing the best way to manage your subgraphs and supergraphs in Kubernetes environments. With the operator, you can define your subgraphs, compose them into supergraphs, and deploy them using native Kubernetes resources and workflows. ## Keycloak 26.3.1 released DevFeed: [Keycloak 26.3.1 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2025-07-10T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [releases](), [upgrade](), [version]() Tags: [docs](), [idm](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [migration](), [openid-connect](), [operator](), [quarkus](), [releases](), [saml](), [sso](), [tls](), [upgrade](), [version]() ### AI overview Keycloak 26.3.1 is released. The release includes an upgrade to Infinispan 15.0.16.Final, updated limitations for preview rolling updates, and fixes for realm imports, concurrent storage deletion, TLS reloading, datasource options, the Keycloak Operator, documentation, and WebAuthn login regression issues. ### Source excerpt To download the release go to Keycloak downloads. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #40851 Upgrade to Infinispan 15.0.16.Final #40962 Update limitations of the preview feature rolling updates for patch releases infinispan Bugs #35932 Importing a realm takes more than 1 minute when multiple others exist. dist/quarkus #40368 NPE during loading user groups with concurrent deletion storage #40713 Unable to configure TLS reloading in Keycloak version 26.2.0 or later account/api #40838 Mark options for additional datasources as preview dist/quarkus #40890 Keycloak Operator 26.3.0 fails to update to 26.3.0 operator #40930 Docs: server_development/topics/themes.adoc docs #40954 Keycloak 26.3.0 Regression: Failed to login if web-authn is disabled core ## Double click: Human takes on agentic AI DevFeed: [Double click: Human takes on agentic AI]() Original publisher: [Read original article]() Author: Jenny Xie Published: 2025-02-06T00:00:00Z Content type: opinion Language: en Sources: [Figma Blog]() Topics: [Artificial Intelligence](), [User experience (UX)](), [interoperability]() Tags: [agentic-ai](), [agents](), [ai](), [ai-agents](), [anthropic](), [cognitive-load](), [complexity](), [google](), [interoperability](), [microsoft](), [openai](), [operator](), [ux](), [web]() ### AI overview This first installment of Figma's Double Click series presents community perspectives on agentic AI and its implications for user experience and the web. It discusses the appeal of AI agents that reduce user effort, argues that AI should function as an underlying capability rather than a conversational interface, and considers how agentic systems may expose less complexity while enabling greater interoperability across platforms. ### Source excerpt There's a lot of buzz about AI agents. Robots that do more with less supervision--what could go wrong? We asked our community how this might shake up how we think about UX. ## Get Running with Apache Flink on Kubernetes, part 1 of 2 DevFeed: [Get Running with Apache Flink on Kubernetes, part 1 of 2]() Original publisher: [Read original article]() Published: 2025-01-21T00:00:00Z Content type: tutorial Language: en Sources: [Gunnar Morling]() Topics: [apache-flink](), [Kubernetes](), [Deployment](), [Provisioning](), [container images]() Tags: [apache-flink](), [container-images](), [deployment](), [installation](), [kubernetes](), [operator](), [provisioning]() ### AI overview A two-part tutorial on deploying Apache Flink jobs on Kubernetes using the upstream Flink Kubernetes Operator. Part one covers installation, setup, custom-resource deployment, and building container images; part two addresses fault tolerance, high availability, savepoints, observability, and UI access. ### Source excerpt Table of Contents Installation and Setup Deployment Types Deploying Your First Flink Job on Kubernetes Building Custom Job Images This post originally appeared on the Decodable blog. All rights reserved. Kubernetes is a widely used deployment platform for Apache Flink. While Flink has had native support for Kubernetes for quite a while, it is in particular the operator pattern which makes deploying Flink jobs onto Kubernetes clusters a compelling option: you define jobs in a declarative resource, and a control loop running in a component called a Kubernetes operator takes care of provisioning and maintaining (e.g. scaling, updating) all the required resources. Automation is the keyword here, significantly reducing the manual effort required for running Flink jobs in production. ## A Kubernetes operator for Trino? DevFeed: [A Kubernetes operator for Trino?]() Original publisher: [Read original article]() Author: Manfred Moser, Martin Traverso Published: 2024-10-10T00:00:00Z Content type: article Language: en Sources: [Trino Blog]() Topics: [Kubernetes](), [Containers](), [Cloud](), [hosting]() Tags: [cloud](), [community](), [containers](), [helm](), [hosting](), [images](), [kubernetes](), [open-source](), [operator](), [servers](), [slack]() ### AI overview The article discusses the proposal for a Kubernetes operator for Trino. It reviews existing internal and open-source operator efforts, suggests combining them into a modular operator aligned with Trino and potentially compatible with Trino Gateway, and invites contributors to discuss implementation and maintenance questions. ### Source excerpt Trino is deployed everywhere - on-premise, in private data centers, in the cloud with hosting providers, on bare metal servers, on virtual machines, and with containers. With all these options for deployments, a Kubernetes-based platform with a container emerged as the most widely used approach. The Trino project caters for this usage with our container images for every release and our Helm chart. However we keep hearing from people who want to use a Kubernetes operator... ## Optimizing Digit Counting for Kotlin Long Values DevFeed: [Optimizing Digit Counting for Kotlin Long Values]() Original publisher: [Read original article]() Author: Romain Guy Published: 2024-05-27T00:00:00Z Content type: article Language: en Sources: [Posts on Romain Guy]() Topics: [Code](), [Optimization](), [Kotlin]() Tags: [android](), [assembly](), [code](), [developer](), [floating-point](), [graphics](), [kotlin](), [numbers](), [operator](), [optimization](), [performance]() ### AI overview This article explores ways to count the decimal digits in positive Kotlin Long values without relying on floating-point log10, which cannot represent every Long value exactly. It compares a straightforward branching approach with a binary-search solution and reports faster execution for the latter on a Pixel 6. ### Source excerpt Jake Wharton recently caused me to go down yet another silly optimization rabbit hole when he nonchalantly linked to a piece of code used to count the number of digits in a Long during a Slack conversation about Kotlin's lack of ternary operator. This of course triggered folks like Madis Pink and me to want to optimize it... Counting digits Link to heading The simplest way to count the number of digits would be to compute log10(n).toInt() + 1, where n is our input number. Unfortunately logarithmic functions like Kotlin's log10 are only defined for floating point numbers. If our input is an Int or a Long, we could first convert to Double and then call log10, but not all Long values can be stored in a Double (any value above 2^53), and we would have to special case 0. We must therefore find a different solution1. ## Keycloak 24.0.3 released DevFeed: [Keycloak 24.0.3 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2024-04-16T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [LDAP](), [JavaScript](), [Authentication]() Tags: [api](), [authentication](), [idm](), [java](), [javascript](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [openid-connect](), [operator](), [release](), [resolved](), [saml](), [sso]() ### AI overview Keycloak 24.0.3 is released with enhancements and resolved issues affecting Microsoft Active Directory account propagation, LDAP-backed users, authentication, identity brokering, user updates, the JavaScript adapter, and the Keycloak Operator. ### Source excerpt To download the release go to Keycloak downloads. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #26695 Keycloak and MSAD: enabling account in MSAD does not propagate to Keycloak ldap Bugs #24201 Cannot disable LDAP-backed user if importEnabled=false ldap #28100 Failed authentication: java.lang.NullPointerException: Cannot invoke "org.keycloak.models.UserModel.getFederationLink()" because "this.delegate" is null identity-brokering #28248 Update user makes User ID changes when federationLink and LDAP_ID is not set properly admin/api #28335 The false option of the pkceMethod init parameter for the JavaScript adapter is ignored adapter/javascript #28638 Missing permission to read configmaps in `keycloak-operator-role` operator ## Getting Started With PyFlink on Kubernetes DevFeed: [Getting Started With PyFlink on Kubernetes]() Original publisher: [Read original article]() Published: 2023-12-07T00:00:00Z Content type: tutorial Language: en Sources: [Gunnar Morling]() Topics: [apache-flink](), [Kubernetes](), [stream-processing](), [Kafka](), [Python](), [data-engineering]() Tags: [apache-kafka](), [flink](), [kafka](), [kubernetes](), [operator](), [programming](), [python](), [stream-processing]() ### AI overview A practical guide to running PyFlink on Kubernetes with Apache Flink 1.18. It covers installing the Flink Kubernetes Operator and Kafka with Strimzi, creating a PyFlink job that generates data and writes it to Kafka using Flink SQL, building a container image, and deploying the job to Kubernetes. ### Source excerpt Table of Contents What Is PyFlink and Why Should You Care? Prerequisites Installing the Flink Kubernetes Operator Installing Strimzi and Apache Kafka A Simple PyFlink Job Building a Container Image With Your PyFlink Job Deploying a PyFlink Job On Kubernetes This post originally appeared on the Decodable blog. All rights reserved. The other day, I wanted to get my feet wet with PyFlink. While there is a fair amount of related information out there, I couldn't find really up-to-date documentation on using current versions of PyFlink with Flink on Kubernetes. ## Data Classes and Destructuring DevFeed: [Data Classes and Destructuring]() Original publisher: [Read original article]() Author: author@typealias.com (Dave Leeds) Published: 2023-10-09T00:00:00Z Content type: tutorial Language: en Sources: [Dave Leeds on Kotlin - typealias.com]() Topics: [Kotlin](), [data]() Tags: [class](), [classes](), [copy](), [data-class](), [destructuring](), [destructuring-assignment](), [equals](), [hashcode](), [introduction](), [kotlin](), [learn-to-program](), [object](), [open](), [operator](), [override](), [programming](), [properties](), [tostring]() ### AI overview A Kotlin tutorial introducing data classes and destructuring. It explains how data classes relate to equals(), hashCode(), and toString(), beginning with reference equality and overriding inherited functions. ### Source excerpt At the end of the last chapter, we saw how all objects in Kotlin inherit three functions from an open class called Any. Those functions are equals(), hashCode(), and toString(). In this chapter, we're going to learn about data classes, which are super-powered classes that are especially helpful when we've got an immutable class that mainly just holds properties. To better understand data classes, let's first explore each of the three functions above, and see what's involved when we override them! ## Kubernetes operators using Kubebuilder DevFeed: [Kubernetes operators using Kubebuilder]() Original publisher: [Read original article]() Published: 2023-05-27T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Kubernetes](), [Orchestration](), [Go Language]() Tags: [golang](), [k8s](), [kubernetes](), [kubernetes-operators](), [operator](), [orchestration](), [reconciliation]() ### AI overview A practical tutorial on building a Kubernetes operator with Kubebuilder and Go. It creates a TodoList custom resource, implements reconciliation logic that checks pods, deploys the operator to a local kind cluster, and extends it to watch pod events. ### Source excerpt In this post, we will be going over the fastest no-frills approach to getting your operator off the ground using kubebuilder. The post assumes knowledge of the following: Kubernetes and how it works Kubernetes custom resource definitions Kubernetes Operators and reconciliation loops Setting up a local cluster, I use kind for my k8s orchestration needs Golang The task is to create an operator that operates on a Kubernetes CRD TodoList... ## Pattern matching on error codes DevFeed: [Pattern matching on error codes]() Original publisher: [Read original article]() Author: Ole Begemann Published: 2023-02-27T19:32:22Z Content type: article Language: en Sources: [Ole Begemann]() Topics: [Swift](), [Code](), [Framework]() Tags: [apple](), [code](), [compiler](), [operator](), [pattern-matching](), [protocol](), [swift](), [syntax]() ### AI overview This article explains why Swift allows concise pattern matching against Foundation error codes. Foundation overloads the ~= operator to compare error values with error codes, rather than relying on special compiler behavior. The technique applies to CocoaError, URLError, POSIXError, and MachError. ### Source excerpt Foundation overloads the pattern matching operator ~= to enable matching against error codes in catch clauses. catch clauses in Swift support pattern matching, using the same patterns you'd use in a case clause inside a switch or in an if case ... statement. For example, to handle a file-not-found error you might write: import Foundation do { let fileURL = URL(filePath: "/abc") // non-existent file let data = try Data(contentsOf: fileURL) } catch let error as CocoaError where error.code == .fileReadNoSuchFile { print("File doesn't exist") } catch { print("Other error: \(error)") } This binds a value of type CocoaError to the variable error and then uses a where clause to check the specific error code. However, if you don't need access to the complete error instance, there's a shorter way to write this, matching directly against the error code: let data = try Data(contentsOf: fileURL) - } catch let error as CocoaError where error.code == .fileReadNoSuchFile { + } catch CocoaError.fileReadNoSuchFile { print("File doesn't exist") Foundation overloads ~= I was wondering why this shorter syntax works. Is there some special compiler magic for pattern matching against error codes of NSError instances? Turns out: no, the answer is much simpler. Foundation includes an overload for the pattern matching operator ~= that matches error values against error codes.1 The implementation looks something like this: public func ~= (code: CocoaError.Code, error: any Error) -> Bool { guard let error = error as? CocoaError else { return false } return error.code == code } The actual code in Foundation is a little more complex because it goes through a hidden protocol named _ErrorCodeProtocol, but that's not important. You can check out the code in the Foundation repository: Darwin version, swift-corelibs-foundation version. This matching on error codes is available for CocoaError, URLError, POSIXError, and MachError (and possibly more types in other Apple frameworks, I haven't checked). I w [Next page]()