codex70

I can confirm I'm seeing the same issue, the ServiceIntentions appears to deploy correctly, however when I describe the ServiceIntentions I see the following: ``` Status: Conditions: Last Transition Time:...

@jrhunger. it was a good idea to check, but in my case, the filebeat services do have different names in each environment. I suspect the real problem I'm having is...

@jrhunger, the filebeat service is super simple: ``` apiVersion: v1 kind: Service metadata: name: filebeat labels: app: filebeat spec: selector: app: filebeat ports: - name: http port: 5506 targetPort: 5506...

@jrhunger well spotted, that's it. You've explained it perfectly and now I understand why it was causing problems. It looks like I don't necessarily need: ``` dnsPolicy: ClusterFirstWithHostNet hostNetwork: true...

I'm fairly sure I am, I think I've tried everything just in case. We're now looking to reconfigure the broker to see if we can set up something that mutually...

Here you can clearly see the test failing after exactly 9 minutes, followed by a further 9 minutes to quit and stop the driver in the tear down procedure.

> Why are you not setting any timeout on the Grid? Because I wasn't aware that was an option, I must have missed that. Will try that now

OK, I've tried with the following options in the docker compose file, but it hasn't made any difference: ``` selenium-hub: image: selenium/hub:latest container_name: selenium-hub ports: - "4442:4442" - "4443:4443" -...

Thank you, the example I found must have been out of date. I have now put: ``` environment: - SE_NODE_SESSION_TIMEOUT=960000 - SE_SESSION_REQUEST_TIMEOUT=960000 ``` However this still makes no difference. One...

If I set the following options, they get passed through to selenium, but it still makes no difference: ``` options.setImplicitWaitTimeout(clientTimeout); options.setPageLoadTimeout(defaultTimeout); options.setScriptTimeout(defaultTimeout); ``` Whatever settings I change, I still end...