Jack Francis jackfrancis

Why do English countries (England, Canada, The United States, Australia) have such a high incidence of inventing sports, both for their own amusement, and those that are exported around the world: the many types of football (association football for export; Canadian Football, American Football, and Australian Rules Football for local amusement), Rugby, Cricket, regulated Horse Racing, Baseball, Tennis, Badminton, Ice Hockey, Basketball, Volleyball. Why don't English colonies of non-"English" (meaning generally Anglo-Saxon-dominant peoples) peoples invent sports, and instead adopt the English ones (for example India with cricket, African nations with football, Hong Kong with horse racing, badminton, and football)? Why didn't non-English colonies adopt their non-English rulers' sports, but instead also adopted the English sport (Argentina and Brazil adopting football, for example)? Is there something unique about English culture that suggests a predeliction for inventing rules-based athletic games that othe

Here's what Cluster Autoscaler will do in your scenario, end‑to‑end. The behavior is entirely driven by the fact that the Kubernetes Node objects still exist (kubelet stops, but the API server retains them) and the Azure cloud provider does not surface VM power state to CA.

How CA classifies the 33 stopped nodes

CA buckets every node every loop in clusterstate.go (updateReadinessStats). The buckets are mutually exclusive:

Agent Workflow: Reinforce `azure` support

Auto-generated by providerize on 2026-02-24 22:56 UTC Repository: https://github.com/ray-project/ray

Context

This repository has cloud provider integrations for: aws, gcp, azure.

Current ranking (best → worst):

KubeRay Federation Proposal — Analysis & Comparative Landscape

Proposal Summary

Issue #4561 by @yuchen-ecnu proposes adding federation capability to KubeRay so that a single logical RayCluster can span multiple Kubernetes clusters. The core motivation:

Fragmented GPUs: Organizations procure GPUs across multiple cloud vendors/AZs. Today these are isolated into separate K8s clusters, preventing a unified Ray cluster.
Operational pain: Users must split datasets, deploy multiple small RayClusters, and manually manage them — causing long-tail performance issues and complexity.
Virtual Kubelet limitations: The common workaround (aggregating via Virtual Kubelet) creates control-plane scalability bottlenecks, especially at scale (e.g., 10K→400K+ cores in an hour).

	#!/usr/bin/env python3
	"""
	Count commits per cloud provider in kubernetes/autoscaler's
	cluster-autoscaler/cloudprovider/ tree over a given time window.

	How it works
	------------
	GitHub's REST Commits API supports two filters we exploit:
	- `path` : restrict to commits that touched files under this path
	- `since` : ISO-8601 timestamp lower bound

	Here are my two talks:

	The first one will be a joint session w/ GKE (and fellow SIG Autoscaling TL) describing the OSS CA and our plans to make significant changes in 2026.

	The tl;dr is that GOOG will be investing significantly in the OSS CA to correct a decade of forking and blackbox dev.

	This is directly due to investments that we have made in the SIG to modernize the OSS surface area, release process, E2E tests, etc.

	- https://maintainersummiteu2026.sched.com/event/2EWf1/cluster-autoscaler-evolution-kuba-tuznik-google-jack-francis-microsoft

	{
	"kustomize_substitutions": {
	"AZURE_SUBSCRIPTION_ID": "<sub id here>",
	"AZURE_TENANT_ID": "<tenant id here>",
	"AZURE_CLIENT_SECRET": "<sp pw here>",
	"AZURE_CLIENT_ID": "<sp id here>",
	"AZURE_ENVIRONMENT": "AzurePublicCloud",
	"AZURE_SSH_PUBLIC_KEY_B64": "<ssh public key here>"
	},
	"worker-templates": {

	#!/bin/bash

	if [ -z "$RESOURCE_GROUP" ]; then
	echo "must provide a RESOURCE_GROUP env var"
	exit 1;
	fi

	if [ -z "$REGION" ]; then
	echo "must provide a REGION env var"
	exit 1;

	#!/bin/bash

	if [ -z "$RESOURCE_GROUP" ]; then
	echo "must provide a RESOURCE_GROUP env var"
	exit 1;
	fi

	# Continually look for non-Succeeded VMSS instances
	while true; do
	NUM_VMSS=0