apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T23:14:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-221-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-221.ec2.internal uid: 2ef38550-6527-4e32-8736-2b1579f188af resourceVersion: "53607" uid: 77ecb3c3-7a0b-4235-98b4-352f02b502a5 spec: sourcePod: network-check-source-989f8b8dc-ktpr9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T23:21:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.474µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:49:37Z" - latency: 1.099177ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:48:37Z" - latency: 879.385µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:47:37Z" - latency: 1.255684ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:46:37Z" - latency: 1.06635ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:45:37Z" - latency: 842.017µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:44:37Z" - latency: 871.074µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:43:37Z" - latency: 958.971µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:42:37Z" - latency: 1.492557ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:41:37Z" - latency: 1.045093ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:40:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T23:14:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-221-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-221.ec2.internal uid: 2ef38550-6527-4e32-8736-2b1579f188af resourceVersion: "48813" uid: 1fb2a1f2-fc1d-42df-9341-b1498d45f373 spec: sourcePod: network-check-source-989f8b8dc-ktpr9 targetEndpoint: acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T23:20:37Z" message: 'load-balancer-api-external: tcp connection to acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.015189ms message: 'load-balancer-api-external: tcp connection to acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:44:37Z" - latency: 7.535239ms message: 'load-balancer-api-external: resolved host name acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:44:37Z" - latency: 3.006042ms message: 'load-balancer-api-external: tcp connection to acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:43:37Z" - latency: 8.280011ms message: 'load-balancer-api-external: resolved host name acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:43:37Z" - latency: 3.344407ms message: 'load-balancer-api-external: tcp connection to acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:42:37Z" - latency: 7.893744ms message: 'load-balancer-api-external: resolved host name acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:42:37Z" - latency: 3.278044ms message: 'load-balancer-api-external: tcp connection to acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:41:37Z" - latency: 6.757016ms message: 'load-balancer-api-external: resolved host name acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:41:37Z" - latency: 3.021453ms message: 'load-balancer-api-external: tcp connection to acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:40:37Z" - latency: 9.057703ms message: 'load-balancer-api-external: resolved host name acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:40:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T23:14:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-221-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-221.ec2.internal uid: 2ef38550-6527-4e32-8736-2b1579f188af resourceVersion: "48812" uid: 4299931b-419e-417f-a9b7-41c33c7cb1ec spec: sourcePod: network-check-source-989f8b8dc-ktpr9 targetEndpoint: acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T23:20:37Z" message: 'load-balancer-api-internal: tcp connection to acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.687432ms message: 'load-balancer-api-internal: tcp connection to acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:44:37Z" - latency: 7.491592ms message: 'load-balancer-api-internal: resolved host name acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:44:37Z" - latency: 4.029725ms message: 'load-balancer-api-internal: tcp connection to acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:43:37Z" - latency: 8.245096ms message: 'load-balancer-api-internal: resolved host name acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:43:37Z" - latency: 3.389817ms message: 'load-balancer-api-internal: tcp connection to acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:42:37Z" - latency: 7.849484ms message: 'load-balancer-api-internal: resolved host name acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:42:37Z" - latency: 2.980753ms message: 'load-balancer-api-internal: tcp connection to acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:41:37Z" - latency: 6.731675ms message: 'load-balancer-api-internal: resolved host name acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:41:37Z" - latency: 3.038991ms message: 'load-balancer-api-internal: tcp connection to acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:40:37Z" - latency: 9.075938ms message: 'load-balancer-api-internal: resolved host name acaa1582c0ffe4dd8b126c1f3b9d7e1f-37ededf7a7da090c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:40:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T23:14:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-221-to-network-check-target-ip-10-0-130-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-221.ec2.internal uid: 2ef38550-6527-4e32-8736-2b1579f188af resourceVersion: "53605" uid: 5a9f0ba3-6f7c-4c52-82ba-1831f417228f spec: sourcePod: network-check-source-989f8b8dc-ktpr9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T23:21:37Z" message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.855441ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:49:37Z" - latency: 2.379674ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:48:37Z" - latency: 2.056841ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:47:37Z" - latency: 2.374305ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:46:37Z" - latency: 2.200776ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:45:37Z" - latency: 2.258768ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:44:37Z" - latency: 2.209686ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:43:37Z" - latency: 2.14873ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:42:37Z" - latency: 2.28826ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:41:37Z" - latency: 2.161485ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:40:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T23:14:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-221-to-network-check-target-ip-10-0-137-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-221.ec2.internal uid: 2ef38550-6527-4e32-8736-2b1579f188af resourceVersion: "53606" uid: 64c05952-d6d5-423b-86a4-ab71c0c5d40b spec: sourcePod: network-check-source-989f8b8dc-ktpr9 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T23:21:37Z" message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 881.328µs message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:49:37Z" - latency: 947.103µs message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:48:37Z" - latency: 994.455µs message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:47:37Z" - latency: 1.50306ms message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:46:37Z" - latency: 971.961µs message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:45:37Z" - latency: 816.647µs message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:44:37Z" - latency: 886.074µs message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:43:37Z" - latency: 817.728µs message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:42:37Z" - latency: 829.972µs message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:41:37Z" - latency: 889.042µs message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:40:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T23:14:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-221-to-network-check-target-ip-10-0-143-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-221.ec2.internal uid: 2ef38550-6527-4e32-8736-2b1579f188af resourceVersion: "53604" uid: ebe7fedd-06a9-4c4d-b1d8-0050ee148a90 spec: sourcePod: network-check-source-989f8b8dc-ktpr9 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T23:21:37Z" message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.903602ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:49:37Z" - latency: 2.126927ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:48:37Z" - latency: 2.132625ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:47:37Z" - latency: 1.963655ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:46:37Z" - latency: 2.184689ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:45:37Z" - latency: 1.867569ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:44:37Z" - latency: 1.925294ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:43:37Z" - latency: 1.705136ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:42:37Z" - latency: 1.869613ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:41:37Z" - latency: 1.908345ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:40:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T23:14:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-221-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-221.ec2.internal uid: 2ef38550-6527-4e32-8736-2b1579f188af resourceVersion: "48811" uid: dd30883a-1a55-47c0-8097-222a5830a083 spec: sourcePod: network-check-source-989f8b8dc-ktpr9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T23:20:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 908.591µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:44:37Z" - latency: 2.107525ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T23:44:37Z" - latency: 1.1895ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:43:37Z" - latency: 1.662082ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T23:43:37Z" - latency: 880.692µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:42:37Z" - latency: 1.854025ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T23:42:37Z" - latency: 1.070301ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:41:37Z" - latency: 1.736361ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T23:41:37Z" - latency: 906.448µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:40:37Z" - latency: 1.872468ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T23:40:37Z" kind: List metadata: resourceVersion: ""