Skip to content

Conversation

jakenotjay
Copy link
Contributor

  • Adds the public ingress parameter to the GCP cluster class
  • Allows for direct configuration instead of a hidden config item

…e instances via class instantiation rather than via the config
Copy link
Member

@jacobtomlinson jacobtomlinson left a comment

Choose a reason for hiding this comment

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

Looks great, one small comment.

self.general_zone = "-".join(self.zone.split("-")[:2]) # us-east1-c -> us-east1
self.service_account = service_account or self.config.get("service_account")
self.instance_scopes = instance_scopes or self.config.get("instance_scopes")
self.public_ingress = public_ingress or self.config.get("public_ingress", True)
Copy link
Member

Choose a reason for hiding this comment

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

Again can we put this default value in the config system? It just makes it easier for folks using the YAML to find the available configuration options.

Copy link
Contributor Author

@jakenotjay jakenotjay Oct 3, 2025

Choose a reason for hiding this comment

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

Hey jacob, I made this edit as it was already in the config, but wasn't accessible to users creating the cluster programatically, see:

public_ingress: true # Assign a public IP address to the scheduler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants