fix(kubernetes_cluster): pin latest GA k8s versions; configurable GKE maintenance window#371
Merged
unni-facets merged 1 commit intoJul 10, 2026
Conversation
… maintenance window Task 1 — support latest k8s (pin to latest GA, not null): - eks_standard: remove non-existent "1.37" from cluster_version enum + validation (EKS standard support tops out at 1.36 as of Jul 2026). Default stays 1.36 (GA). Addons already resolve via null/"latest" per cluster version, so they match. - vke: bump k8s_version default v1.35.0+1 -> v1.36.1+2 (current latest GA per Vultr /v2/kubernetes/versions). Placeholder/sample/validation msg updated. - lke: already at latest GA (1.35) — no change. Task 2 — auto cluster upgrades (GKE): - gke: make the daily maintenance window start time configurable via spec.maintenance_window.start_time (default "03:00", unchanged behavior). Release channel kept at STABLE; node-pool auto-upgrade intentionally not managed (left to consumers). AKS left as-is. Validated: raptor create iac-module --dry-run passes for eks_standard and gke.
unni-facets
deleted the
fix/kubernetes-cluster-latest-k8s-gke-maintenance
branch
July 10, 2026 08:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two threads of work on the
kubernetes_clusterflavors.Task 1 — support latest k8s (pin to latest GA, not null)
Verified current GA versions live per provider (Jul 2026).
1.36(standard support 1.33–1.36; 1.37 not on EKS)1.28–1.37, default1.361.37from enum +variables.tfvalidation. Default1.36unchanged.v1.36.1+2v1.35.0+1v1.36.1+2.1.351.35null/"latest"per cluster version, so they auto-match — no addon edits needed.Task 2 — auto cluster upgrades (GKE)
spec.maintenance_window.start_time(default"03:00"→ behavior unchanged). Release channel kept atSTABLE. Node-pool auto-upgrade intentionally not managed — left to consumers to run on their own timeline.Validation
raptor create iac-module --dry-run— pass foreks_standardandgke.Not fixed here (pre-existing, out of scope)
required_providers(RULE-013) — must stay:vultris a non-hashicorp provider (vultr/vultr); every vultr module in the repo declares it, and terraform can't resolve the source namespace without it. RULE-013 is a false-positive for non-hashicorp providers.@facets/vultr_cloud_accountinput type 404 — the type is defined in-repo (outputs/vultr_cloud_account/) but not registered on the test CP profile. CP-registration matter, not a code bug.variable "instance"istype = any(RULE-025) — pre-existing; full retype is its own task.Version bumps
None required (RULE-023): EKS change removes an invalid option (bugfix), VKE is a default change, GKE adds an optional field — all non-breaking.