Okta vs Kubernetes
Side-by-side trajectory, velocity, and editorial themes.
Okta's developer push is concentrated on Cross App Access and ISV-friendly low-code integrations.
The Okta developer surface is dominated by Cross App Access (XAA) content — protocol tutorials, an xaa.dev playground, and app-to-app connection guides — plus a recent OIN feature for ISVs called API Integration Actions and earlier work on entitlements. Cadence is roughly monthly. All recent posts are educational rather than product launches.
XAA is the centerpiece of the developer story. Okta is using the blog to seed an ecosystem around the spec while deepening ISV integration paths through Workflows-based low-code. An earlier MCP server hints at AI-agent identity interest, but the visible momentum is on XAA and OIN extensibility.
Expect more XAA enablement (partner-app tutorials, possibly a public-preview or GA milestone) and additional OIN features that push provisioning and entitlements toward AI-agent and ISV-tooling use cases.
Kubernetes 1.36 leans into AI/ML scheduling and control-plane scaling.
The 1.36 cycle is graduation-heavy, with PSI metrics, declarative validation, and volume group snapshots all promoted to GA. Alongside that, the project is making architectural moves around workload scheduling (a new PodGroup API), API-server safety (Mixed Version Proxy on by default), and very-large-cluster scaling (server-side sharded list and watch in alpha). Etcd 3.7 has hit beta in parallel.
Kubernetes is repositioning the control plane for two pressures at once: AI/ML batch workloads, where gang scheduling and DRA are becoming first-class concerns, and very-large clusters, where the control plane itself needs to shard. The pattern across this cycle is consolidation — old experimental scaffolding is reaching GA or being removed (ExternalIPs), while new APIs land with explicit separation of static template from runtime state. Less feature sprawl, more API hygiene.
Expect 1.37 to push server-side sharded watch toward beta and to keep extending DRA's reach into native resources like memory and networking. Workload-aware scheduling will likely accumulate scheduler-plugin-level coordination patterns next, with downstream batch frameworks starting to converge on the PodGroup shape.
See more alternatives to Okta →
See more alternatives to Kubernetes →