[Bug] Upgrade vke-cluster to the version that is actually live (1.32.1+1) by Will-Howard · Pull Request #1267 · bluedotimpact/bluedot

Will-Howard · 2025-09-01T09:39:00Z

Description

From the issue #1266 :

The version shown in the Vultr web UI is actually 1.32.1+1, and running kubectl version locally confirms this (client/server mismatch is just a local issue):
> kubectl version
Client Version: v1.34.0
Kustomize Version: v5.7.1
Server Version: v1.32.1
Warning: version difference between client (1.34) and server (1.32) exceeds the supported minor version skew of +/-1

Issue

#1266

Developer checklist

N/A

Steps to test

On master, running pulumi preview --diff --show-config should give an output that looks like this:

pulumi preview --diff --show-config
Previewing update (prod):
Configuration:
    infra:airtablePat: [secret]
    infra:alertsSlackBotToken: [secret]
    infra:anthropicApiKey: [secret]
    infra:backupGcsKey: [secret]
    infra:keycloakClientId: [secret]
    infra:keycloakClientSecret: [secret]
    infra:loginProxyKeycloakClientSecret: [secret]
    infra:loginProxySharedSecret: [secret]
    infra:meetZoomClientSecret: [secret]
    infra:minioRootPassword: [secret]
    infra:openaiApiKey: [secret]
    infra:prodOnlyWebhookDeletion: [secret]
    infra:roomDisplayBearerToken: [secret]
    pulumi:disable-default-providers: ["kubernetes","minio"]
    vultr:apiKey: [secret]
  pulumi:pulumi:Stack: (same)
    [urn=urn:pulumi:prod::infra::pulumi:pulumi:Stack::infra-prod]
    ~ vultr:index/kubernetes:Kubernetes: (update)
        [id=THE_ACTUAL_ID]
        [urn=urn:pulumi:prod::infra::vultr:index/kubernetes:Kubernetes::vke-cluster]
        [provider=urn:pulumi:prod::infra::pulumi:providers:vultr::default_2_20_1_github_/api.github.com/dirien/pulumi-vultr::ANOTHER_ACTUAL_ID]
      ~ version: "v1.32.1+1" => "v1.29.2+1"
Resources:
    ~ 1 to update
    104 unchanged

And on this branch:

pulumi preview --diff --show-config
Previewing update (prod):
Configuration:
    infra:airtablePat: [secret]
    infra:alertsSlackBotToken: [secret]
    infra:anthropicApiKey: [secret]
    infra:backupGcsKey: [secret]
    infra:keycloakClientId: [secret]
    infra:keycloakClientSecret: [secret]
    infra:loginProxyKeycloakClientSecret: [secret]
    infra:loginProxySharedSecret: [secret]
    infra:meetZoomClientSecret: [secret]
    infra:minioRootPassword: [secret]
    infra:openaiApiKey: [secret]
    infra:prodOnlyWebhookDeletion: [secret]
    infra:roomDisplayBearerToken: [secret]
    pulumi:disable-default-providers: ["kubernetes","minio"]
    vultr:apiKey: [secret]
  pulumi:pulumi:Stack: (same)
    [urn=urn:pulumi:prod::infra::pulumi:pulumi:Stack::infra-prod]
Resources:
    105 unchanged

coderabbitai · 2025-09-01T09:39:07Z

Walkthrough

Updated the Vultr Kubernetes Engine cluster version in apps/infra/src/vultr/vke.ts from v1.29.2+1 to v1.32.1+1. No other properties, control flow, or exported/public signatures changed.

Changes

Cohort / File(s)	Summary of Changes
Vultr VKE config `apps/infra/src/vultr/vke.ts`	Bumped cluster version string from v1.29.2+1 to v1.32.1+1; no other modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

[Bug] Upgrade Kubernetes to a supported version #1266 — Updates the same Kubernetes version in apps/infra/src/vultr/vke.ts, matching this PR’s change.

Poem

A bunny taps the version slate,
From 1.29 to 1.32’s gate.
Carrot commits, hop and apply,
Clusters nibble clouds on high.
One tiny bump, a tidy cheer—
Ship it quick, the burrow’s clear! 🥕🐇

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

Visit our Status Page to check the current availability of CodeRabbit.
Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

greptile-apps

Greptile Summary

This PR updates the Kubernetes version in the Vultr Kubernetes Engine (VKE) cluster configuration from v1.29.2+1 to v1.32.1+1 in the apps/infra/src/vultr/vke.ts file. This is a critical infrastructure fix that addresses a deployment issue where the Pulumi infrastructure code was out of sync with the actual live production cluster.

The change resolves a specific problem where the version specified in the code (v1.29.2+1) has been archived by Vultr, causing deployment failures for the vke-cluster service. According to the issue description and testing evidence provided, the production cluster is already running on v1.32.1+1, as confirmed by both the Vultr web UI and kubectl version output.

This is purely a synchronization fix - the infrastructure code is being updated to match the reality of what's already deployed in production. The change affects the k8sCluster resource definition in the VKE configuration, which is part of the broader Pulumi infrastructure as code setup for managing the bluedot production Kubernetes cluster on Vultr's Amsterdam region.

The fix ensures that future Pulumi deployments will succeed by aligning the declared infrastructure state with the actual deployed state, preventing the mismatch that was causing deployment pipeline failures.

Confidence score: 5/5

This PR is safe to merge with minimal risk as it synchronizes code with existing production infrastructure
Score reflects that this is a straightforward version alignment fix with clear evidence and testing provided
No files require special attention - this is a single-line change in infrastructure configuration

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}

coderabbitai

Actionable comments posted: 0

🧹 Nitpick comments (1)

apps/infra/src/vultr/vke.ts (1)
7-7: Optional: drive the version from Pulumi config to avoid future code edits.

Keeps code stable when bumping versions across stacks.

Apply within this line:
-  version: 'v1.32.1+1',
+  version: clusterVersion,
Add near imports:
import * as pulumi from '@pulumi/pulumi';
const cfg = new pulumi.Config();
const clusterVersion = cfg.get('k8sVersion') ?? 'v1.32.1+1';
Then set per stack:

pulumi config set k8sVersion v1.32.1+1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

MCP integration is disabled by default for public repositories
Jira integration is disabled by default for public repositories
Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 730bfe2 and e6010a1.

📒 Files selected for processing (1)

apps/infra/src/vultr/vke.ts (1 hunks)

🔇 Additional comments (1)

apps/infra/src/vultr/vke.ts (1)

7-7: Pulumi Kubernetes version updated to v1.32.1+1 — no other stale pins found.

marn-in-prod · 2025-09-02T01:34:01Z

Great job on finding that it's been updated for us automatically!

Upgrade vke-cluster to the version that is actually live

e6010a1

Will-Howard requested a review from marn-in-prod September 1, 2025 09:39

greptile-apps Bot reviewed Sep 1, 2025

View reviewed changes

Will-Howard changed the title ~~[Bug] Upgrade vke-cluster to the version that is actually live~~ [Bug] Upgrade vke-cluster to the version that is actually live (1.32.1+1) Sep 1, 2025

coderabbitai Bot reviewed Sep 1, 2025

View reviewed changes

This was referenced Sep 1, 2025

[Bug] Upgrade Kubernetes to a supported version #1266

Closed

[Bug] Upgrade vke-cluster to latest version (v1.33.0+3) #1268

Merged

marn-in-prod approved these changes Sep 2, 2025

View reviewed changes

Will-Howard merged commit 3b91c06 into master Sep 2, 2025
6 checks passed

Will-Howard deleted the wh-kube-upgrade-to-actual-version-2025-09 branch September 2, 2025 09:21

joshestein mentioned this pull request Jun 7, 2026

VKE cluster stuck on EOL k8s 1.33 — empty version metadata blocks upgrade (Vultr support) #2618

Open

5 tasks

This was referenced Jun 7, 2026

[fix] Revert VKE target to v1.33.0+3 to unblock infra CD #2619

Merged

[fix] Temporarily ignore VKE version to unblock infra CD #2628

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Bug] Upgrade vke-cluster to the version that is actually live (1.32.1+1)#1267

[Bug] Upgrade vke-cluster to the version that is actually live (1.32.1+1)#1267
Will-Howard merged 1 commit into
masterfrom
wh-kube-upgrade-to-actual-version-2025-09

Will-Howard commented Sep 1, 2025

Uh oh!

coderabbitai Bot commented Sep 1, 2025 •

edited

Loading

Chat

Support

CodeRabbit Commands (Invoked using PR/Issue comments)

Other keywords and placeholders

CodeRabbit Configuration File (`.coderabbit.yaml`)

Status, Documentation and Community

Uh oh!

greptile-apps Bot left a comment

Uh oh!

coderabbitai Bot left a comment

Uh oh!

marn-in-prod commented Sep 2, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

Will-Howard commented Sep 1, 2025

Description

Issue

Developer checklist

Steps to test

Uh oh!

coderabbitai Bot commented Sep 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Possibly related issues

Poem

Chat

Support

CodeRabbit Commands (Invoked using PR/Issue comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Status, Documentation and Community

Uh oh!

greptile-apps Bot left a comment

Choose a reason for hiding this comment

Greptile Summary

Confidence score: 5/5

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

marn-in-prod commented Sep 2, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

coderabbitai Bot commented Sep 1, 2025 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)