apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:04:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-243-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-243.ec2.internal uid: 3a5773e5-fd77-4ce5-a240-06e87e01ee16 resourceVersion: "54727" uid: 0c378c8b-47b9-4bda-a1c6-ecb99e82c47d spec: sourcePod: network-check-source-989f8b8dc-vzc9l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T19:11:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 931.192µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:39:17Z" - latency: 840.657µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:38:17Z" - latency: 916.065µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:37:17Z" - latency: 910.513µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:36:17Z" - latency: 1.092323ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:35:17Z" - latency: 981.162µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:34:17Z" - latency: 1.030248ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:33:17Z" - latency: 1.090832ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:32:17Z" - latency: 682.738µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:31:17Z" - latency: 1.237926ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:30:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:04:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-243-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-243.ec2.internal uid: 3a5773e5-fd77-4ce5-a240-06e87e01ee16 resourceVersion: "55686" uid: f0f8ba3f-a005-4363-9abc-6c59aeb192c5 spec: sourcePod: network-check-source-989f8b8dc-vzc9l targetEndpoint: a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T19:10:17Z" message: 'load-balancer-api-external: tcp connection to a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.834387ms message: 'load-balancer-api-external: tcp connection to a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:40:17Z" - latency: 8.652921ms message: 'load-balancer-api-external: resolved host name a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:40:17Z" - latency: 5.248279ms message: 'load-balancer-api-external: tcp connection to a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:39:17Z" - latency: 10.524508ms message: 'load-balancer-api-external: resolved host name a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:39:17Z" - latency: 4.366312ms message: 'load-balancer-api-external: tcp connection to a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:38:17Z" - latency: 8.23728ms message: 'load-balancer-api-external: resolved host name a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:38:17Z" - latency: 4.774192ms message: 'load-balancer-api-external: tcp connection to a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:37:17Z" - latency: 7.048372ms message: 'load-balancer-api-external: resolved host name a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:37:17Z" - latency: 5.273642ms message: 'load-balancer-api-external: tcp connection to a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:36:17Z" - latency: 6.819091ms message: 'load-balancer-api-external: resolved host name a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:36:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:04:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-243-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-243.ec2.internal uid: 3a5773e5-fd77-4ce5-a240-06e87e01ee16 resourceVersion: "55685" uid: 610f6708-1028-48f2-afc1-d8b1903b07a8 spec: sourcePod: network-check-source-989f8b8dc-vzc9l targetEndpoint: a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T19:10:17Z" message: 'load-balancer-api-internal: tcp connection to a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.65254ms message: 'load-balancer-api-internal: tcp connection to a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:40:17Z" - latency: 8.581755ms message: 'load-balancer-api-internal: resolved host name a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:40:17Z" - latency: 4.9337ms message: 'load-balancer-api-internal: tcp connection to a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:39:17Z" - latency: 10.552732ms message: 'load-balancer-api-internal: resolved host name a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:39:17Z" - latency: 3.615305ms message: 'load-balancer-api-internal: tcp connection to a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:38:17Z" - latency: 8.182437ms message: 'load-balancer-api-internal: resolved host name a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:38:17Z" - latency: 4.746594ms message: 'load-balancer-api-internal: tcp connection to a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:37:17Z" - latency: 7.082297ms message: 'load-balancer-api-internal: resolved host name a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:37:17Z" - latency: 5.434911ms message: 'load-balancer-api-internal: tcp connection to a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:36:17Z" - latency: 6.771784ms message: 'load-balancer-api-internal: resolved host name a2e133ac80310410389f41cd613a340a-392efed97e23debf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:36:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:04:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-243-to-network-check-target-ip-10-0-133-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-243.ec2.internal uid: 3a5773e5-fd77-4ce5-a240-06e87e01ee16 resourceVersion: "54726" uid: faaf06a3-521e-4673-b068-e15b9c32634b spec: sourcePod: network-check-source-989f8b8dc-vzc9l targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T19:11:17Z" message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.176827ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:39:17Z" - latency: 2.153861ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:38:17Z" - latency: 2.637935ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:37:17Z" - latency: 2.166787ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:36:17Z" - latency: 2.883398ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:35:17Z" - latency: 2.71604ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:34:17Z" - latency: 2.760845ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:33:17Z" - latency: 2.488017ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:32:17Z" - latency: 1.766205ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:31:17Z" - latency: 2.216217ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:30:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:04:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-243-to-network-check-target-ip-10-0-137-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-243.ec2.internal uid: 3a5773e5-fd77-4ce5-a240-06e87e01ee16 resourceVersion: "54725" uid: 760a32bb-27d3-4ef1-a515-43ebcc8043d3 spec: sourcePod: network-check-source-989f8b8dc-vzc9l targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T19:11:17Z" message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.147876ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:39:17Z" - latency: 2.138703ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:38:17Z" - latency: 2.048193ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:37:17Z" - latency: 2.076774ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:36:17Z" - latency: 2.32519ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:35:17Z" - latency: 2.345488ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:34:17Z" - latency: 2.376266ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:33:17Z" - latency: 1.971671ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:32:17Z" - latency: 1.994594ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:31:17Z" - latency: 2.120862ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:30:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:04:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-243-to-network-check-target-ip-10-0-140-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-243.ec2.internal uid: 3a5773e5-fd77-4ce5-a240-06e87e01ee16 resourceVersion: "54723" uid: 460e890f-9726-417a-b131-399c97078c31 spec: sourcePod: network-check-source-989f8b8dc-vzc9l targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T19:11:17Z" message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 891.197µs message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:39:17Z" - latency: 691.761µs message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:38:17Z" - latency: 877.519µs message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:37:17Z" - latency: 817.793µs message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:36:17Z" - latency: 1.097249ms message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:35:17Z" - latency: 1.322391ms message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:34:17Z" - latency: 1.021619ms message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:33:17Z" - latency: 811.539µs message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:32:17Z" - latency: 702.485µs message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:31:17Z" - latency: 777.941µs message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:30:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:04:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-243-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-243.ec2.internal uid: 3a5773e5-fd77-4ce5-a240-06e87e01ee16 resourceVersion: "55684" uid: ced2d350-3299-47a1-b9c8-a32caa2065a8 spec: sourcePod: network-check-source-989f8b8dc-vzc9l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T19:10:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 868.608µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:40:17Z" - latency: 1.898885ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:40:17Z" - latency: 1.134247ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:39:17Z" - latency: 1.885537ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:39:17Z" - latency: 1.161248ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:38:17Z" - latency: 1.546369ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:38:17Z" - latency: 1.113743ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:37:17Z" - latency: 1.638908ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:37:17Z" - latency: 973.055µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:36:17Z" - latency: 1.581282ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:36:17Z" kind: List metadata: resourceVersion: ""