Closed nmarchini closed 3 weeks ago
Hello.
Regarding the prompt on step 5, it's because the user added some kind of conditionals when creating the roles to be bound. Not something we include in the OOO roles we offer. And it's something on GCP's side, not a bug in the integration.
For the second thing, which is an actual problem, we offer the option to create an Autopilot cluster with the proper configuration on behalf of the users. Besides that, going with the existing cluster approach means that users need to take care of K8s related settings. I see that the container starts running properly and it crashes, so later it maybe starts again and does the same thing. This is a Kubernetes thing, not the integration. Some guesses include not provisioning the cluster with enough resources, correct probes for the pods, etc.
In many cases users need to go outside of the default offering because of business use cases, but they need to handle the extra steps if they administrate their environment.
Describe the bug Running ./deploy-helm.sh give a prompt on step 5 not mentioned in the documentation. Containers start but then crash after a few mins
To Reproduce Steps to reproduce the behavior:
Expected behavior Helm deployment completes and containers start and send metrics to Dynatrace
Additional context
Running the deployment in GCP Cloud Shell
Error message from container logs (metrics container)