We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
What happened:
I'm looking to create my first chaos experiment where I've deployed the manifests and currently trying to setup an envrionment
What you expected to happen:
Infrastructure is pending and subscriber pod is in crash loop, I would expect the envrionment to connect to the agent
Where can this issue be corrected? (optional)
configmap for subscriber pod needs to have the correct SERVER_ADDR if the existing value is incorrect
How to reproduce it (as minimally and precisely as possible): This is currently whats in the configmap
apiVersion: v1 data: COMPONENTS: | DEPLOYMENTS: ["app=chaos-exporter", "name=chaos-operator", "app=event-tracker", "app=workflow-controller"] CUSTOM_TLS_CERT: "" INFRA_SCOPE: namespace IS_INFRA_CONFIRMED: "false" SERVER_ADDR: http://127.0.0.1:9002/api/query SKIP_SSL_VERIFY: "false" START_TIME: "1726653903043" VERSION: 3.10.0 kind: ConfigMap metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"v1","data":{"COMPONENTS":"DEPLOYMENTS: [\"app=chaos-exporter\", \"name=chaos-operator\", \"app=event-tracker\", \"app=workflow-controller\"]\n","CUSTOM_TLS_CERT":"","INFRA_SCOPE":"namespace","IS_INFRA_CONFIRMED":"false","SERVER_ADDR":"http://\u003cnode-ip\u003e:31254/api/query","SKIP_SSL_VERIFY":"false","START_TIME":"1726653903043","VERSION":"3.10.0"},"kind":"ConfigMap","metadata":{"annotations":{},"creationTimestamp":"2024-09-18T10:06:26Z","name":"subscriber-config","namespace":"resilience-engineering","resourceVersion":"1428829938","uid":"cac723fb-af3d-4434-b7a9-246495e01606"}} creationTimestamp: "2024-09-19T10:51:13Z" name: subscriber-config namespace: resilience-engineering resourceVersion: "1430317541" uid: 342795b8-d94b-43ee-871a-65fdc3647d28
Anything else we need to know?:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happened:
I'm looking to create my first chaos experiment where I've deployed the manifests and currently trying to setup an envrionment
What you expected to happen:
Infrastructure is pending and subscriber pod is in crash loop, I would expect the envrionment to connect to the agent
Where can this issue be corrected? (optional)
configmap for subscriber pod needs to have the correct SERVER_ADDR if the existing value is incorrect
How to reproduce it (as minimally and precisely as possible):
This is currently whats in the configmap
apiVersion: v1 data: COMPONENTS: | DEPLOYMENTS: ["app=chaos-exporter", "name=chaos-operator", "app=event-tracker", "app=workflow-controller"] CUSTOM_TLS_CERT: "" INFRA_SCOPE: namespace IS_INFRA_CONFIRMED: "false" SERVER_ADDR: http://127.0.0.1:9002/api/query SKIP_SSL_VERIFY: "false" START_TIME: "1726653903043" VERSION: 3.10.0 kind: ConfigMap metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"v1","data":{"COMPONENTS":"DEPLOYMENTS: [\"app=chaos-exporter\", \"name=chaos-operator\", \"app=event-tracker\", \"app=workflow-controller\"]\n","CUSTOM_TLS_CERT":"","INFRA_SCOPE":"namespace","IS_INFRA_CONFIRMED":"false","SERVER_ADDR":"http://\u003cnode-ip\u003e:31254/api/query","SKIP_SSL_VERIFY":"false","START_TIME":"1726653903043","VERSION":"3.10.0"},"kind":"ConfigMap","metadata":{"annotations":{},"creationTimestamp":"2024-09-18T10:06:26Z","name":"subscriber-config","namespace":"resilience-engineering","resourceVersion":"1428829938","uid":"cac723fb-af3d-4434-b7a9-246495e01606"}} creationTimestamp: "2024-09-19T10:51:13Z" name: subscriber-config namespace: resilience-engineering resourceVersion: "1430317541" uid: 342795b8-d94b-43ee-871a-65fdc3647d28
Anything else we need to know?:
The text was updated successfully, but these errors were encountered: