wip(gcp): Bigtable Backup + GKE conformance (blocked on formae gaps)#74
Draft
naxty wants to merge 1 commit into
Draft
wip(gcp): Bigtable Backup + GKE conformance (blocked on formae gaps)#74naxty wants to merge 1 commit into
naxty wants to merge 1 commit into
Conversation
…reen) Split out of the parity batch (PR #73) as WIP - both need deeper work than fixture/schema changes: - GCP::Bigtable::Backup: registration + dependency-ordered fixture + response mapping. Instance create is rejected by the plugin in ~8s and the failure StatusMessage is surfaced to no readable log; blocked on plugin-error observability. - GKE container conformance (Cluster + NodePool): self-contained VPC + subnet (secondary ranges, private nodes, privateIpGoogleAccess). Control plane comes up but node provisioning hits a transient 'subnetwork not found' race; needs provisioner retry or a formae ordering edge (selfLink refs are rejected by GKE).
naxty
added a commit
that referenced
this pull request
Jun 30, 2026
Both need deeper work than this batch (Backup: plugin-error observability; GKE: create-ordering vs GCP subnet consistency). Removed from this PR so it can land green; tracked in PR #74.
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 (WIP — do not merge)
Split out of #73. Two new GCP conformance targets that need deeper work than fixture/schema changes — kept separate so #73 can land green.
GCP::Bigtable::Backup
Registration + dependency-ordered fixture (instance → table → backup via resolvable refs) +
backupResponseTransformer(parses instance/cluster/short-name from the backup path).Blocker: the PRODUCTION instance create is rejected by the plugin in ~8s, but the failure
StatusMessageis surfaced to no readable log (confirmed local + CI: agent log shows only "Failed", the harness plugin temp-log auto-removes, the fail is too fast to snapshot). Can't pin the API reason without closing the plugin-error observability gap.GKE container conformance (Cluster + NodePool)
Self-contained fixture: own VPC + subnet with pod/service secondary ranges, private nodes (org policy forbids external IPs),
privateIpGoogleAccess(image pull, no Cloud NAT).Progress through the layers: org-policy → secondary-range 400 → egress → subnet-create race. Control plane comes up, but node provisioning hits a transient
subnetwork not found. Referencing the subnet by name doesn't force formae to wait for it to be GCP-consistent;selfLinkdoes but GKE rejects the https form. Needs a provisioner-level retry or a formae ordering edge.Status
Neither is conformance-green. Tracking issues; not for merge until the underlying formae gaps (plugin-error observability; create-ordering vs GCP consistency) are addressed.