Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

GKE nodes are private #7

Closed
jbw976 opened this issue May 10, 2021 · 1 comment
Closed

GKE nodes are private #7

jbw976 opened this issue May 10, 2021 · 1 comment
Assignees
@stevendborrelli

Comments

@jbw976
Copy link
Member

jbw976 commented May 10, 2021

In the GKE composition spec, we are declaring the nodes to be private: https://github.com/upbound/platform-ref-gcp/blob/main/cluster/gke/composition.yaml#L31

This means that the nodes don't have outbound network access and can't do docker pulls, so the services being installed via provider-helm cannot get to the running state: crossplane-contrib/provider-helm#76 (comment)

We should no longer declare these nodes as private and then test to make sure that the full cluster comes up along with all of the services that provider-helm is deploying. Not only the helm chart should be OK/deployed, but the actual containers in the GKE instance should be running OK too.
@stevendborrelli stevendborrelli mentioned this issue May 10, 2021
Merged
@jbw976
Copy link
Member Author

jbw976 commented May 13, 2021

Fixed by #8

@jbw976 jbw976 closed this as completed May 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stevendborrelli stevendborrelli

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stevendborrelli @jbw976