apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T10:35:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-214-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-214.ec2.internal uid: 59b1dd5b-7afb-4c00-a305-a807e24021df resourceVersion: "43483" uid: 59adfe4e-6124-4242-b61f-f22a820c14ad spec: sourcePod: network-check-source-7f44b6dd87-r8m7n targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T10:42:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.043839ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:03:24Z" - latency: 1.097498ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:02:24Z" - latency: 1.356966ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:01:24Z" - latency: 1.020864ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:00:24Z" - latency: 1.097063ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:59:24Z" - latency: 953.212µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:58:24Z" - latency: 972.605µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:57:24Z" - latency: 941.831µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:56:24Z" - latency: 936.411µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:55:24Z" - latency: 933.505µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:54:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T10:35:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-214-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-214.ec2.internal uid: 59b1dd5b-7afb-4c00-a305-a807e24021df resourceVersion: "45536" uid: 20475638-2426-4f85-bf03-65509f838f90 spec: sourcePod: network-check-source-7f44b6dd87-r8m7n targetEndpoint: a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T10:41:24Z" message: 'load-balancer-api-external: tcp connection to a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.409091ms message: 'load-balancer-api-external: tcp connection to a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:05:24Z" - latency: 6.81107ms message: 'load-balancer-api-external: resolved host name a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:05:24Z" - latency: 4.677398ms message: 'load-balancer-api-external: tcp connection to a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:04:24Z" - latency: 6.659591ms message: 'load-balancer-api-external: resolved host name a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:04:24Z" - latency: 5.41935ms message: 'load-balancer-api-external: tcp connection to a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:03:24Z" - latency: 6.350563ms message: 'load-balancer-api-external: resolved host name a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:03:24Z" - latency: 5.110765ms message: 'load-balancer-api-external: tcp connection to a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:02:24Z" - latency: 7.145214ms message: 'load-balancer-api-external: resolved host name a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:02:24Z" - latency: 3.336763ms message: 'load-balancer-api-external: tcp connection to a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:01:24Z" - latency: 6.810657ms message: 'load-balancer-api-external: resolved host name a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:01:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T10:35:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-214-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-214.ec2.internal uid: 59b1dd5b-7afb-4c00-a305-a807e24021df resourceVersion: "45535" uid: a769d001-5431-432b-90b8-c5a46706c0e2 spec: sourcePod: network-check-source-7f44b6dd87-r8m7n targetEndpoint: a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T10:41:24Z" message: 'load-balancer-api-internal: tcp connection to a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.413028ms message: 'load-balancer-api-internal: tcp connection to a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:05:24Z" - latency: 6.714881ms message: 'load-balancer-api-internal: resolved host name a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:05:24Z" - latency: 4.660124ms message: 'load-balancer-api-internal: tcp connection to a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:04:24Z" - latency: 6.625293ms message: 'load-balancer-api-internal: resolved host name a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:04:24Z" - latency: 3.903604ms message: 'load-balancer-api-internal: tcp connection to a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:03:24Z" - latency: 6.252319ms message: 'load-balancer-api-internal: resolved host name a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:03:24Z" - latency: 5.09037ms message: 'load-balancer-api-internal: tcp connection to a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:02:24Z" - latency: 7.175832ms message: 'load-balancer-api-internal: resolved host name a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:02:24Z" - latency: 4.265103ms message: 'load-balancer-api-internal: tcp connection to a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:01:24Z" - latency: 6.740148ms message: 'load-balancer-api-internal: resolved host name a8ed93a73e0a84e909408d55c82d9430-f6b447b17eb14c2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:01:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T10:35:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-214-to-network-check-target-ip-10-0-140-254 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-214.ec2.internal uid: 59b1dd5b-7afb-4c00-a305-a807e24021df resourceVersion: "43481" uid: 53bf080d-2ec3-4378-8587-7a99c39b3dce spec: sourcePod: network-check-source-7f44b6dd87-r8m7n targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T10:42:24Z" message: 'network-check-target-ip-10-0-140-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.530077ms message: 'network-check-target-ip-10-0-140-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:03:24Z" - latency: 2.938865ms message: 'network-check-target-ip-10-0-140-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:02:24Z" - latency: 2.273255ms message: 'network-check-target-ip-10-0-140-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:01:24Z" - latency: 1.998583ms message: 'network-check-target-ip-10-0-140-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:00:24Z" - latency: 2.302174ms message: 'network-check-target-ip-10-0-140-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:59:24Z" - latency: 2.253365ms message: 'network-check-target-ip-10-0-140-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:58:24Z" - latency: 2.03552ms message: 'network-check-target-ip-10-0-140-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:57:24Z" - latency: 2.32914ms message: 'network-check-target-ip-10-0-140-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:56:24Z" - latency: 2.446969ms message: 'network-check-target-ip-10-0-140-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:55:24Z" - latency: 1.877546ms message: 'network-check-target-ip-10-0-140-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:54:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T10:35:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-214-to-network-check-target-ip-10-0-142-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-214.ec2.internal uid: 59b1dd5b-7afb-4c00-a305-a807e24021df resourceVersion: "43480" uid: d8a03ce3-f5e8-41c8-a4c7-5e9b461569dc spec: sourcePod: network-check-source-7f44b6dd87-r8m7n targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-21T10:42:24Z" message: 'network-check-target-ip-10-0-142-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.550218ms message: 'network-check-target-ip-10-0-142-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:03:24Z" - latency: 888.558µs message: 'network-check-target-ip-10-0-142-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:02:24Z" - latency: 917.18µs message: 'network-check-target-ip-10-0-142-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:01:24Z" - latency: 1.060874ms message: 'network-check-target-ip-10-0-142-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:00:24Z" - latency: 919.967µs message: 'network-check-target-ip-10-0-142-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:59:24Z" - latency: 993.388µs message: 'network-check-target-ip-10-0-142-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:58:24Z" - latency: 1.223058ms message: 'network-check-target-ip-10-0-142-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:57:24Z" - latency: 1.516716ms message: 'network-check-target-ip-10-0-142-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:56:24Z" - latency: 963.594µs message: 'network-check-target-ip-10-0-142-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:55:24Z" - latency: 961.659µs message: 'network-check-target-ip-10-0-142-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:54:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T10:35:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-214-to-network-check-target-ip-10-0-142-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-214.ec2.internal uid: 59b1dd5b-7afb-4c00-a305-a807e24021df resourceVersion: "43482" uid: 4e72896a-e48e-43fe-a6ec-6e1fda3325ff spec: sourcePod: network-check-source-7f44b6dd87-r8m7n targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T10:42:24Z" message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.424799ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:03:24Z" - latency: 2.339483ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:02:24Z" - latency: 2.435807ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:01:24Z" - latency: 2.562697ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:00:24Z" - latency: 2.54551ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:59:24Z" - latency: 2.278273ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:58:24Z" - latency: 2.54751ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:57:24Z" - latency: 2.396043ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:56:24Z" - latency: 2.150402ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:55:24Z" - latency: 2.049118ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T10:54:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T10:35:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-214-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-214.ec2.internal uid: 59b1dd5b-7afb-4c00-a305-a807e24021df resourceVersion: "45534" uid: 901b4218-930e-423f-8b0b-d0e352c2168f spec: sourcePod: network-check-source-7f44b6dd87-r8m7n targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T10:41:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 824.546µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:05:24Z" - latency: 1.725482ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T11:05:24Z" - latency: 905.357µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:04:24Z" - latency: 1.654866ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T11:04:24Z" - latency: 1.0064ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:03:24Z" - latency: 1.918472ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T11:03:24Z" - latency: 893.69µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:02:24Z" - latency: 1.78468ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T11:02:24Z" - latency: 1.18114ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:01:24Z" - latency: 1.826401ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T11:01:24Z" kind: List metadata: resourceVersion: ""