Skip to content

tools: remove setup-gcp and hack/teardown.sh - #3396

Closed
Steven Shriver (stshrive) wants to merge 1 commit into
agent-substrate:mainfrom
stshrive:dev/remove-setup-gcp
Closed

Steven Shriver (stshrive) wants to merge 1 commit into
agent-substrate:mainfrom
stshrive:dev/remove-setup-gcp

Conversation

@stshrive

Copy link
Copy Markdown
Collaborator

The GKE provisioning and teardown tooling now lives in https://github.com/ai-on-gke/substrate-gke under tools/setup-gcp, so core no longer carries a copy. Docs and comments that pointed at the removed files now point at substrate-gke. go mod tidy drops the GCP client modules only setup-gcp used, and vendor/ and _LICENSES/ are regenerated to match.

Covers #3390, except that hack/teardown.sh is removed here as well; substrate-gke's tools/setup-gcp/teardown.sh replaces it.

Part of #2304

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DCO is a required check and fails: the commit author is [email protected] but the sign-off is [email protected]. Also, per AGENTS.md, drop the #3390 / #2304 references from the commit message and keep them in the PR description.

Comment thread README.md Resolved

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving now that substrate-gke has --cluster-scoped. The DCO check still needs the sign-off email to match the author email before this can merge.

Comment thread AGENTS.md Resolved

@HavenXia Haven Xia (HavenXia) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

others lgtm

@stshrive

Copy link
Copy Markdown
Collaborator Author

DCO is a required check and fails: the commit author is [email protected] but the sign-off is [email protected]. Also, per AGENTS.md, drop the #3390 / #2304 references from the commit message and keep them in the PR description.

This is now resolved

@MushuEE

Grant McCloskey (MushuEE) commented Oct 29, 2026 •

Copy link
Copy Markdown
Collaborator

Cleanup these after this change gets in: #2745 #2532 #1999

I think these are mostly covered by changes in https://github.com/ai-on-gke/substrate-gke already.

The GKE provisioning and teardown tooling now lives in
https://github.com/ai-on-gke/substrate-gke under tools/setup-gcp, so core
no longer carries a copy. Docs and comments that pointed at the removed
files now point at substrate-gke. go mod tidy drops the GCP client
modules only setup-gcp used, and vendor/ and _LICENSES/ are regenerated
to match.

hack/teardown.sh is removed here as well;
substrate-gke's tools/setup-gcp/teardown.sh replaces it.

Signed-off-by: Steven Shriver <[email protected]>
@HavenXia

Copy link
Copy Markdown
Member

need rebase

@thockin Tim Hockin (thockin) added this to the M3 milestone Oct 29, 2026
@thockin Tim Hockin (thockin) self-assigned this Oct 29, 2026
@HavenXia

Copy link
Copy Markdown
Member

After this, nothing in core reads CLUSTER_VERSION, NODE_POOL_NAME or NODE_POOL_VERSION. Could you drop them from hack/ate-dev-env.sh.example here? That would also fix #3371.

@@ -219,7 +219,7 @@ it alongside the gateway. The install applies:
(`app: atenet-egress`), on the provider's gRPC port. Every other connection
to the provider pods is dropped. The NetworkPolicy takes effect only on a
cluster whose network plugin enforces NetworkPolicy, such as GKE Dataplane

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is going to be annoying, but... I think we should reduce or eliminate almost all xrefs to GCP and GKE specific stuff, especially in contexts like this. It doesn't add any clarity ("NetworkPolicy takes effect only on a cluster whose network plugin enforces NetworkPolicy" is tautologically true and sufficient). Worse, it encourages OTHER ecosystem players to request putting their own name here.

Docs are not advertisements.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💯, but can we do more cleanup like that in subsequent PRs where this PR didn't make it worse?

@BenTheElder

Copy link
Copy Markdown
Collaborator

Steven is OOO for a few days I think?, maybe we should have someone pick this up and rebase it.

@thockin

Tim Hockin (thockin) commented Oct 30, 2026 •

Copy link
Copy Markdown
Collaborator

Edit: I was ignoring the code removal. We should land that.

AFAICT this doesn't really have to land in 1.0.0, there's no real code to it, so I am putting it on the back-burner.

@thockin Tim Hockin (thockin) modified the milestones: M3, v1.0.x Oct 30, 2026
@thockin

Copy link
Copy Markdown
Collaborator

Moved back to M3, but after discussion we should split this two 2 PRs. 1) remove GCP setup code; 2) Fix docs / comments etc. We want (1) for RC2

@MushuEE

Copy link
Copy Markdown
Collaborator

I am taking this over to rebase, presume there is no way to take over from Steven short term.

@MushuEE

Copy link
Copy Markdown
Collaborator

This had conflicts with main (mostly from the Hugo docsite move in #1974), so I rebased it and opened #3505 with your commit and authorship preserved. The PR description there explains how each conflict was resolved. If you'd rather keep it here, you can reset your branch to that commit instead, and I'll close #3505.

Zoe Zhao (zoez7) pushed a commit to zoez7/substrate that referenced this pull request Nov 2, 2026
Supersedes agent-substrate#3396 by @stshrive, rebased onto current `main`. The commit
keeps his authorship and sign-off.

The GKE provisioning and teardown tooling now lives in
https://github.com/ai-on-gke/substrate-gke under tools/setup-gcp, so
core no longer carries a copy. Docs and comments that pointed at the
removed files now point at substrate-gke. go mod tidy drops the GCP
client modules only setup-gcp used, and vendor/ and _LICENSES/ are
regenerated to match.

Covers agent-substrate#3390, except that hack/teardown.sh is removed here as well;
substrate-gke's tools/setup-gcp/teardown.sh replaces it.

Part of agent-substrate#2304

### Rebase notes
Conflicts were mostly from the Hugo docsite move (agent-substrate#1974):
- `tools/setup-gcp/cloud-sql.md`: deleted, as in the original PR.
- `docs/guides/operator-install.md`, `docs/guides/postgres.md`: the
original edits, re-applied at the new paths.
- `docs/guides/observability.md`: kept main's version, since agent-substrate#1974
already removed the Dashboards section the original PR edited.
- `cmd/kubectl-ate/README.md`: kept main's stub that points to
`docs/reference/kubectl-ate.md`. That page no longer has the setup-gcp
line, so the edit had nowhere to go.

---------

Signed-off-by: Steven Shriver <[email protected]>
Signed-off-by: Grant McCloskey <[email protected]>
Co-authored-by: Steven Shriver <[email protected]>
Grant McCloskey (MushuEE) added a commit to MushuEE/substrate that referenced this pull request Nov 2, 2026
Supersedes agent-substrate#3396 by @stshrive, rebased onto current `main`. The commit
keeps his authorship and sign-off.

The GKE provisioning and teardown tooling now lives in
https://github.com/ai-on-gke/substrate-gke under tools/setup-gcp, so
core no longer carries a copy. Docs and comments that pointed at the
removed files now point at substrate-gke. go mod tidy drops the GCP
client modules only setup-gcp used, and vendor/ and _LICENSES/ are
regenerated to match.

Covers agent-substrate#3390, except that hack/teardown.sh is removed here as well;
substrate-gke's tools/setup-gcp/teardown.sh replaces it.

Part of agent-substrate#2304

### Rebase notes
Conflicts were mostly from the Hugo docsite move (agent-substrate#1974):
- `tools/setup-gcp/cloud-sql.md`: deleted, as in the original PR.
- `docs/guides/operator-install.md`, `docs/guides/postgres.md`: the
original edits, re-applied at the new paths.
- `docs/guides/observability.md`: kept main's version, since agent-substrate#1974
already removed the Dashboards section the original PR edited.
- `cmd/kubectl-ate/README.md`: kept main's stub that points to
`docs/reference/kubectl-ate.md`. That page no longer has the setup-gcp
line, so the edit had nowhere to go.

---------

Signed-off-by: Steven Shriver <[email protected]>
Signed-off-by: Grant McCloskey <[email protected]>
Co-authored-by: Steven Shriver <[email protected]>
(cherry picked from commit b66e16a)
Dmitry Berkovich (dberkov) pushed a commit that referenced this pull request Nov 3, 2026
Supersedes #3396 by @stshrive, rebased onto current `main`. The commit
keeps his authorship and sign-off.

The GKE provisioning and teardown tooling now lives in
https://github.com/ai-on-gke/substrate-gke under tools/setup-gcp, so
core no longer carries a copy. Docs and comments that pointed at the
removed files now point at substrate-gke. go mod tidy drops the GCP
client modules only setup-gcp used, and vendor/ and _LICENSES/ are
regenerated to match.

Covers #3390, except that hack/teardown.sh is removed here as well;
substrate-gke's tools/setup-gcp/teardown.sh replaces it.

Part of #2304

### Rebase notes
Conflicts were mostly from the Hugo docsite move (#1974):
- `tools/setup-gcp/cloud-sql.md`: deleted, as in the original PR.
- `docs/guides/operator-install.md`, `docs/guides/postgres.md`: the
original edits, re-applied at the new paths.
- `docs/guides/observability.md`: kept main's version, since #1974
already removed the Dashboards section the original PR edited.
- `cmd/kubectl-ate/README.md`: kept main's stub that points to
`docs/reference/kubectl-ate.md`. That page no longer has the setup-gcp
line, so the edit had nowhere to go.

---------

Signed-off-by: Steven Shriver <[email protected]>
Signed-off-by: Grant McCloskey <[email protected]>
Co-authored-by: Steven Shriver <[email protected]>
(cherry picked from commit b66e16a)
Signed-off-by: Eitan Yarmush <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants