apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:12:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-160-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-160.ec2.internal uid: 8202a80b-55fd-4810-84fd-85de4991f1e2 resourceVersion: "18515" uid: ab1e98aa-4bef-40d7-bcea-dddb2541244b spec: sourcePod: network-check-source-6f78d59f99-gw2gb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T22:19:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 985.431µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:52Z" - latency: 1.193863ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:52Z" - latency: 935.203µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:52Z" - latency: 972.328µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:30:52Z" - latency: 1.033173ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:29:52Z" - latency: 1.125052ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:28:52Z" - latency: 1.167332ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:27:52Z" - latency: 934.184µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:26:52Z" - latency: 1.258462ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:25:52Z" - latency: 898µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:24:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:12:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-160-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-160.ec2.internal uid: 8202a80b-55fd-4810-84fd-85de4991f1e2 resourceVersion: "19695" uid: 4094186e-4959-4271-8e8f-fba32203e1dc spec: sourcePod: network-check-source-6f78d59f99-gw2gb targetEndpoint: ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T22:18:52Z" message: 'load-balancer-api-external: tcp connection to ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.513465ms message: 'load-balancer-api-external: tcp connection to ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:52Z" - latency: 11.727099ms message: 'load-balancer-api-external: resolved host name ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:36:52Z" - latency: 16.192198ms message: 'load-balancer-api-external: tcp connection to ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:52Z" - latency: 11.803993ms message: 'load-balancer-api-external: resolved host name ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:35:52Z" - latency: 16.548176ms message: 'load-balancer-api-external: tcp connection to ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:52Z" - latency: 12.526815ms message: 'load-balancer-api-external: resolved host name ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:34:52Z" - latency: 18.316864ms message: 'load-balancer-api-external: tcp connection to ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:52Z" - latency: 8.32615ms message: 'load-balancer-api-external: resolved host name ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:33:52Z" - latency: 17.497947ms message: 'load-balancer-api-external: tcp connection to ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:52Z" - latency: 9.903808ms message: 'load-balancer-api-external: resolved host name ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:32:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:12:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-160-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-160.ec2.internal uid: 8202a80b-55fd-4810-84fd-85de4991f1e2 resourceVersion: "19694" uid: 36fcc8cc-608e-42ce-ad98-4c1b8e43b19c spec: sourcePod: network-check-source-6f78d59f99-gw2gb targetEndpoint: ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T22:18:52Z" message: 'load-balancer-api-internal: tcp connection to ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.528229ms message: 'load-balancer-api-internal: tcp connection to ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:52Z" - latency: 11.678785ms message: 'load-balancer-api-internal: resolved host name ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:36:52Z" - latency: 18.748158ms message: 'load-balancer-api-internal: tcp connection to ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:52Z" - latency: 11.893273ms message: 'load-balancer-api-internal: resolved host name ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:35:52Z" - latency: 16.169715ms message: 'load-balancer-api-internal: tcp connection to ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:52Z" - latency: 12.56119ms message: 'load-balancer-api-internal: resolved host name ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:34:52Z" - latency: 18.387518ms message: 'load-balancer-api-internal: tcp connection to ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:52Z" - latency: 8.390307ms message: 'load-balancer-api-internal: resolved host name ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:33:52Z" - latency: 17.025831ms message: 'load-balancer-api-internal: tcp connection to ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:52Z" - latency: 9.960042ms message: 'load-balancer-api-internal: resolved host name ad6b179cec02f44fda3055e9c45bc0a4-3c76003ddd682871.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:32:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:12:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-160-to-network-check-target-ip-10-0-137-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-160.ec2.internal uid: 8202a80b-55fd-4810-84fd-85de4991f1e2 resourceVersion: "18506" uid: 7fc57f57-a0a5-4fc9-9777-1c00c86599e1 spec: sourcePod: network-check-source-6f78d59f99-gw2gb targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:19:52Z" message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.232106ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:52Z" - latency: 1.388931ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:52Z" - latency: 1.153212ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:52Z" - latency: 1.087269ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:30:52Z" - latency: 1.456424ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:29:52Z" - latency: 1.28064ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:28:52Z" - latency: 1.415472ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:27:52Z" - latency: 1.201268ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:26:52Z" - latency: 1.484346ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:25:52Z" - latency: 1.35544ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:24:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:12:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-160-to-network-check-target-ip-10-0-139-44 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-160.ec2.internal uid: 8202a80b-55fd-4810-84fd-85de4991f1e2 resourceVersion: "18507" uid: 05b48808-8078-46f1-8935-d7c35f1d67be spec: sourcePod: network-check-source-6f78d59f99-gw2gb targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:19:52Z" message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.040952ms message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:52Z" - latency: 2.439571ms message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:52Z" - latency: 1.715981ms message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:52Z" - latency: 1.908196ms message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:30:52Z" - latency: 2.131619ms message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:29:52Z" - latency: 925.76µs message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:28:52Z" - latency: 1.706965ms message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:27:52Z" - latency: 1.975432ms message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:26:52Z" - latency: 1.243863ms message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:25:52Z" - latency: 1.549195ms message: 'network-check-target-ip-10-0-139-44: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:24:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:12:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-160-to-network-check-target-ip-10-0-142-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-160.ec2.internal uid: 8202a80b-55fd-4810-84fd-85de4991f1e2 resourceVersion: "18511" uid: 6c475965-dfb9-47c3-93b0-3fa789e8d76b spec: sourcePod: network-check-source-6f78d59f99-gw2gb targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:19:52Z" message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.721865ms message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:52Z" - latency: 1.846309ms message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:52Z" - latency: 1.797751ms message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:52Z" - latency: 568.67µs message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:30:52Z" - latency: 1.767773ms message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:29:52Z" - latency: 1.625386ms message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:28:52Z" - latency: 526.763µs message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:27:52Z" - latency: 1.638916ms message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:26:52Z" - latency: 1.869193ms message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:25:52Z" - latency: 658.69µs message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:24:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:12:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-160-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-160.ec2.internal uid: 8202a80b-55fd-4810-84fd-85de4991f1e2 resourceVersion: "19693" uid: fd10e2c8-87d8-41b6-a43b-a972d7290dec spec: sourcePod: network-check-source-6f78d59f99-gw2gb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T22:18:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.453354ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:52Z" - latency: 2.015885ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:36:52Z" - latency: 1.840153ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:52Z" - latency: 2.127024ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:35:52Z" - latency: 2.132759ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:52Z" - latency: 1.812477ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:34:52Z" - latency: 773.593µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:52Z" - latency: 1.706944ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:33:52Z" - latency: 699.764µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:52Z" - latency: 1.883663ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:32:52Z" kind: List metadata: resourceVersion: ""