docs(decisions): Kubernetes out of scope; cluster-blueprint write API not viable - #32
Merged
Merged
Conversation
… not viable
Record two scope decisions in DECISIONS.md:
- Kubernetes (PCD-K / Cluster-API) is deliberately out of scope for this IaaS
provider — it's a CAPI-native model that belongs in a dedicated provider.
- The pcd_cluster_blueprint write resource is NOT shipped. Driving the live
resmgr/v2 blueprint API showed create requires a complete object with a valid
non-empty storageBackends (opaque 500 otherwise), delete works, but UPDATE has
no working path (documented PUT /blueprint/{name} 404s even for an existing
blueprint; POST/{name} 404, PATCH 405, PUT /blueprint 500). A resource with no
working update would have to force-replace a cluster-defining object on every
change, which is unsafe. The pcd_cluster_blueprint data source (read) remains
the supported surface.
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.
Records two scope decisions (docs-only) after investigation.
Kubernetes (PCD-K) — out of scope
pcd_kubernetes_clusteris a Cluster-API-native model that belongs in a dedicated CAPI/Kubernetes provider, not this IaaS provider. Decision by the maintainer.pcd_cluster_blueprintwrite resource — not shippedI built the resource and then drove the live
resmgr/v2blueprint API directly (the lab blueprint was made freely mutable for this). On CE 2026.4:POST /blueprintstorageBackends; anything partial/empty returns an opaque 500DELETE /blueprint/{name}PUT /blueprint/{name}returns 404 for an existing blueprint;POST /{name}→404,PATCH→405,PUT /blueprint→500With no working update, a resource would have to force-replace a cluster-defining object on every change — unsafe (hosts/clusters depend on it) — and create is itself fragile. So the write resource is not shipped; the existing
pcd_cluster_blueprintdata source (read) is the supported surface, and blueprints are authored via the UI wizard. Revisit if a later CE build fixes the update path.No code change — the half-built resource was reverted; all test blueprints created during investigation were cleaned up (lab has only
ce-lab-bp).