apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T14:45:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: a563c482-0f1b-4f52-ba9e-3c7645f35432 resourceVersion: "49886" uid: 76d100e5-c45f-44c0-9139-7a517747deeb spec: sourcePod: network-check-source-685456655f-bvc5f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-10T14:52:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.317325ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:13:13Z" - latency: 722.841µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:12:13Z" - latency: 991.231µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:11:13Z" - latency: 956.684µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:10:13Z" - latency: 1.271409ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:09:13Z" - latency: 1.109393ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:08:13Z" - latency: 1.141205ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:07:13Z" - latency: 1.120272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:06:13Z" - latency: 892.424µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:05:13Z" - latency: 1.193673ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:04:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T14:45:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: a563c482-0f1b-4f52-ba9e-3c7645f35432 resourceVersion: "51537" uid: efba9633-9a09-4f46-a959-502fbfe7eb60 spec: sourcePod: network-check-source-685456655f-bvc5f targetEndpoint: aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T14:51:13Z" message: 'load-balancer-api-external: tcp connection to aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.47516ms message: 'load-balancer-api-external: tcp connection to aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:15:13Z" - latency: 8.64338ms message: 'load-balancer-api-external: resolved host name aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T15:15:13Z" - latency: 2.987664ms message: 'load-balancer-api-external: tcp connection to aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:14:13Z" - latency: 8.316183ms message: 'load-balancer-api-external: resolved host name aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T15:14:13Z" - latency: 5.196884ms message: 'load-balancer-api-external: tcp connection to aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:13:13Z" - latency: 8.609305ms message: 'load-balancer-api-external: resolved host name aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T15:13:13Z" - latency: 5.297156ms message: 'load-balancer-api-external: tcp connection to aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:12:13Z" - latency: 9.159781ms message: 'load-balancer-api-external: resolved host name aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T15:12:13Z" - latency: 5.104619ms message: 'load-balancer-api-external: tcp connection to aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:11:13Z" - latency: 9.381355ms message: 'load-balancer-api-external: resolved host name aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T15:11:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T14:45:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: a563c482-0f1b-4f52-ba9e-3c7645f35432 resourceVersion: "51536" uid: 1595f44b-805a-443f-834b-5110f69ac4cc spec: sourcePod: network-check-source-685456655f-bvc5f targetEndpoint: aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T14:51:13Z" message: 'load-balancer-api-internal: tcp connection to aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.536799ms message: 'load-balancer-api-internal: tcp connection to aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:15:13Z" - latency: 8.613719ms message: 'load-balancer-api-internal: resolved host name aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T15:15:13Z" - latency: 2.979336ms message: 'load-balancer-api-internal: tcp connection to aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:14:13Z" - latency: 8.362253ms message: 'load-balancer-api-internal: resolved host name aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T15:14:13Z" - latency: 4.566107ms message: 'load-balancer-api-internal: tcp connection to aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:13:13Z" - latency: 8.652098ms message: 'load-balancer-api-internal: resolved host name aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T15:13:13Z" - latency: 5.328882ms message: 'load-balancer-api-internal: tcp connection to aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:12:13Z" - latency: 9.000451ms message: 'load-balancer-api-internal: resolved host name aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T15:12:13Z" - latency: 4.60426ms message: 'load-balancer-api-internal: tcp connection to aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:11:13Z" - latency: 9.421028ms message: 'load-balancer-api-internal: resolved host name aea3965c3dc824022b62784cdcbeb3fe-adeba8d8bc1d2dad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T15:11:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T14:45:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-network-check-target-ip-10-0-136-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: a563c482-0f1b-4f52-ba9e-3c7645f35432 resourceVersion: "49885" uid: 3725b3a7-932a-451a-980d-5edf70987b38 spec: sourcePod: network-check-source-685456655f-bvc5f targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-10T14:52:13Z" message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.186509ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:13:13Z" - latency: 1.901495ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:12:13Z" - latency: 2.28517ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:11:13Z" - latency: 1.867322ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:10:13Z" - latency: 2.450527ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:09:13Z" - latency: 2.370769ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:08:13Z" - latency: 2.610503ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:07:13Z" - latency: 2.051859ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:06:13Z" - latency: 2.027871ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:05:13Z" - latency: 2.693383ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:04:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T14:45:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-network-check-target-ip-10-0-141-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: a563c482-0f1b-4f52-ba9e-3c7645f35432 resourceVersion: "49883" uid: fa4f4afe-9e8b-4373-8c96-bc8628549cec spec: sourcePod: network-check-source-685456655f-bvc5f targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-10T14:52:13Z" message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.011641ms message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:13:13Z" - latency: 1.50315ms message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:12:13Z" - latency: 918.631µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:11:13Z" - latency: 922.662µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:10:13Z" - latency: 1.087301ms message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:09:13Z" - latency: 1.47638ms message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:08:13Z" - latency: 1.40631ms message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:07:13Z" - latency: 1.126015ms message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:06:13Z" - latency: 1.037969ms message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:05:13Z" - latency: 1.78104ms message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:04:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T14:45:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-network-check-target-ip-10-0-142-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: a563c482-0f1b-4f52-ba9e-3c7645f35432 resourceVersion: "49884" uid: 2c0c6af1-177d-4fbb-9de3-8f7eaf453c5c spec: sourcePod: network-check-source-685456655f-bvc5f targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-10T14:52:13Z" message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.214151ms message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:13:13Z" - latency: 1.824888ms message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:12:13Z" - latency: 2.471842ms message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:11:13Z" - latency: 2.122345ms message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:10:13Z" - latency: 2.337401ms message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:09:13Z" - latency: 2.251047ms message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:08:13Z" - latency: 2.545221ms message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:07:13Z" - latency: 2.362712ms message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:06:13Z" - latency: 2.002086ms message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:05:13Z" - latency: 2.336896ms message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:04:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T14:45:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: a563c482-0f1b-4f52-ba9e-3c7645f35432 resourceVersion: "51534" uid: 6638586b-86ee-475f-8595-03f44faaf949 spec: sourcePod: network-check-source-685456655f-bvc5f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-10T14:51:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 818.072µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:15:13Z" - latency: 1.907214ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T15:15:13Z" - latency: 981.115µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:14:13Z" - latency: 2.106648ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T15:14:13Z" - latency: 1.273656ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:13:13Z" - latency: 1.85985ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T15:13:13Z" - latency: 1.106492ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:12:13Z" - latency: 2.417978ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T15:12:13Z" - latency: 897.885µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T15:11:13Z" - latency: 1.704989ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T15:11:13Z" kind: List metadata: resourceVersion: ""