Terraform creates the following resources:
* VPC network and a subnet.
* firewall rule to allow traffic on port 22 (SSH) and 80 (HTTP).
* Google Kubernetes Engine cluster.
* Google Container Registry.
* Google Compute Engine instance to run Jenkins.
We used HELM in conjunction of the all the following GCP ressources in order to deploy services et deployments in the Google Kubernetes Engine (GKE). You can have a look on the different GCP ressources we used here:
{% content-ref url="/pages/OUUkcNVxvJLpQ0FivHT7" %}
[Google Kubernetes Engine (GKE)](/whanos-documentation/infrastructure/our-whanos-infrastructure/google-kubernetes-engine-gke.md)
{% endcontent-ref %}
{% content-ref url="/pages/Ro6EmcffTtAQDFTDdfrE" %}
[Google Compute Engine (GCE)](/whanos-documentation/infrastructure/our-whanos-infrastructure/google-compute-engine-gce.md)
{% endcontent-ref %}
{% content-ref url="/pages/6BNzkNDw9CvLwj2LK7d6" %}
[Google Container Registry (GCR)](/whanos-documentation/infrastructure/our-whanos-infrastructure/google-container-registry-gcr.md)
{% endcontent-ref %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://cavonstavants-organization.gitbook.io/whanos-documentation/infrastructure/our-whanos-infrastructure.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.