Servers: Kubernetes 1.27, Drupal, and Distributed Databases (UPDATED)

posted by Roy Schestowitz on Apr 18, 2023,
updated May 04, 2023

• Kubernetes 1.27: More fine-grained pod topology spread policies reached bet

  In Kubernetes v1.19, Pod topology spread constraints went to general availability (GA).

  As time passed, we - SIG Scheduling - received feedback from users, and, as a result, we're actively working on improving the Topology Spread feature via three KEPs. All of these features have reached beta in Kubernetes v1.27 and are enabled by default.

  This blog post introduces each feature and the use case behind each of them.

• Preserving the open web through Drupal

  Just because I share content online doesn't mean I want to share control over it.

  My website is a perfect example of what I mean. I take photos nearly everywhere I go: To date, I have more than 10,000 photos uploaded to my Drupal site. Using something like Instagram might be easier, but my photos are precious to me, which is why I feel so strongly about preserving the open web.

  There are many reasons proprietary platforms don't meet my requirements for sharing. First, I like to own my data. If you think back to early social media sites like MySpace, they infamously lost massive amounts of user data. Artists lost their music. People lost their photos. This sort of thing still happens on Facebook and other social media sites.

• Run a distributed database on the cloud

  Apache ShardingSphere is an open source distributed database toolkit. It enhances any database with data sharding, elastic scaling, encryption, and many other capabilities. Deploying and maintaining ShardingSphere-Proxy clusters and load balancing manually can be labor-intensive and time-consuming. To address this issue, Apache ShardingSphere offers ShardingSphere on Cloud, a collection of cloud-based solutions.

  ShardingSphere-on-Cloud includes automated deployment scripts to virtual machines in cloud environments. It also includes tools for a Kubernetes cloud-native environment and a variety of hands-on content for high availability, observability, security policy compliance, and more. This includes Helm Charts, an Operator, and automatic horizontal scaling.

  The new cloud project provides the following capabilities [...]

UPDATE

Late coverage:

• Latest Kubernetes 1.27 Release Provides More Control

  The latest version 1.27 of Kubernetes adds a range of capabilities that promise to give IT teams more granular control over pods within individual clusters.

Much later:

• Blog: Kubernetes 1.27: HorizontalPodAutoscaler ContainerResource type metric moves to beta

  Kubernetes 1.20 introduced the ContainerResource type metric in HorizontalPodAutoscaler (HPA).

  In Kubernetes 1.27, this feature moves to beta and the corresponding feature gate (HPAContainerMetrics) gets enabled by default.

  What is the ContainerResource type metric

  The ContainerResource type metric allows us to configure the autoscaling based on resource usage of individual containers.

  In the following example, the HPA controller scales the target so that the average utilization of the cpu in the application container of all the pods is around 60%.

Latest:

• Kubernetes 1.27: StatefulSet PVC Auto-Deletion (beta)

  Kubernetes v1.27 graduated to beta a new policy mechanism for StatefulSets that controls the lifetime of their PersistentVolumeClaims (PVCs). The new PVC retention policy lets users specify if the PVCs generated from the StatefulSet spec template should be automatically deleted or retrained when the StatefulSet is deleted or replicas in the StatefulSet are scaled down.