You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> Make sure that kubectl is installed and configured to access a GKE cluster. Relevant documentation can be found [here](https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl#run_against_a_specific_cluster).
54
+
40
55
To spin it up on your own GKE cluster, run the following:
This will run the application as a GKE workload. You can view it from the `Workloads` tab under the `Resource Management` section on GKE console.
49
66
50
67
The generated logs can be viewed under the `Logs` tab on the `Job Details` page. These logs will show the detected resource attributes for GKE.
68
+
The detected attributes will contain the attributes detected by the GCP resource detector as well as the attributes attached by the autoconfigure module.
51
69
52
70
## Running the application locally
53
71
@@ -71,3 +89,15 @@ After running the example successfully, you should see the emitted span in JSON
71
89
```
72
90
INFO: {"resource":{"attributes": ... }}
73
91
```
92
+
93
+
## Cleanup
94
+
95
+
Cleanup any Google Cloud Resources created to run this sample.
0 commit comments