apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:21:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-205-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-205.ec2.internal uid: 272e5c55-2d27-40ff-b166-34756b7e7524 resourceVersion: "43702" uid: 229829f1-c259-486c-8318-8a79602c9580 spec: sourcePod: network-check-source-7f44b6dd87-h6lcj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T17:28:10Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 952.837µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:10Z" - latency: 1.141203ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:10Z" - latency: 937.258µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:10Z" - latency: 1.134856ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:10Z" - latency: 958.773µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:10Z" - latency: 1.047534ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:10Z" - latency: 1.030555ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:10Z" - latency: 1.103613ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:10Z" - latency: 898.651µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:10Z" - latency: 963.175µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:40:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:21:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-205-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-205.ec2.internal uid: 272e5c55-2d27-40ff-b166-34756b7e7524 resourceVersion: "45947" uid: c8d5b3b6-55d7-4f9b-af1e-8a5280b85d6b spec: sourcePod: network-check-source-7f44b6dd87-h6lcj targetEndpoint: aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T17:27:11Z" message: 'load-balancer-api-external: tcp connection to aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.777948ms message: 'load-balancer-api-external: tcp connection to aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:51:10Z" - latency: 7.194483ms message: 'load-balancer-api-external: resolved host name aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:51:10Z" - latency: 4.661384ms message: 'load-balancer-api-external: tcp connection to aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:50:10Z" - latency: 6.756689ms message: 'load-balancer-api-external: resolved host name aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:50:10Z" - latency: 3.80388ms message: 'load-balancer-api-external: tcp connection to aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:10Z" - latency: 7.486146ms message: 'load-balancer-api-external: resolved host name aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:49:10Z" - latency: 5.152153ms message: 'load-balancer-api-external: tcp connection to aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:10Z" - latency: 7.359601ms message: 'load-balancer-api-external: resolved host name aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:48:10Z" - latency: 5.088935ms message: 'load-balancer-api-external: tcp connection to aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:10Z" - latency: 7.348484ms message: 'load-balancer-api-external: resolved host name aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:47:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:21:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-205-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-205.ec2.internal uid: 272e5c55-2d27-40ff-b166-34756b7e7524 resourceVersion: "45946" uid: 929c6a56-a30e-40e9-b46a-5b7da032ec37 spec: sourcePod: network-check-source-7f44b6dd87-h6lcj targetEndpoint: aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T17:27:11Z" message: 'load-balancer-api-internal: tcp connection to aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.754129ms message: 'load-balancer-api-internal: tcp connection to aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:51:10Z" - latency: 7.167966ms message: 'load-balancer-api-internal: resolved host name aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:51:10Z" - latency: 3.97348ms message: 'load-balancer-api-internal: tcp connection to aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:50:10Z" - latency: 6.849901ms message: 'load-balancer-api-internal: resolved host name aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:50:10Z" - latency: 3.744793ms message: 'load-balancer-api-internal: tcp connection to aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:10Z" - latency: 7.51601ms message: 'load-balancer-api-internal: resolved host name aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:49:10Z" - latency: 5.163025ms message: 'load-balancer-api-internal: tcp connection to aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:10Z" - latency: 7.436732ms message: 'load-balancer-api-internal: resolved host name aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:48:10Z" - latency: 5.105365ms message: 'load-balancer-api-internal: tcp connection to aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:10Z" - latency: 7.311731ms message: 'load-balancer-api-internal: resolved host name aedc745f303ab4aaf9f88dcdd08c1525-c3684ecfe856cba9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:47:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:21:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-205-to-network-check-target-ip-10-0-131-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-205.ec2.internal uid: 272e5c55-2d27-40ff-b166-34756b7e7524 resourceVersion: "43699" uid: d7c81545-bd3d-4c9e-af7c-c05612b29652 spec: sourcePod: network-check-source-7f44b6dd87-h6lcj targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:28:10Z" message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 855.015µs message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:10Z" - latency: 829.321µs message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:10Z" - latency: 899.934µs message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:10Z" - latency: 957.921µs message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:10Z" - latency: 1.256098ms message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:10Z" - latency: 886.67µs message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:10Z" - latency: 1.054104ms message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:10Z" - latency: 864.535µs message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:10Z" - latency: 853.923µs message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:10Z" - latency: 1.38104ms message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:40:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:21:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-205-to-network-check-target-ip-10-0-132-207 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-205.ec2.internal uid: 272e5c55-2d27-40ff-b166-34756b7e7524 resourceVersion: "43700" uid: 52754efb-a7ab-4ab0-808e-32c84cde1e4c spec: sourcePod: network-check-source-7f44b6dd87-h6lcj targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:28:10Z" message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.99105ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:10Z" - latency: 2.298525ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:10Z" - latency: 2.194177ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:10Z" - latency: 1.890232ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:10Z" - latency: 2.083729ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:10Z" - latency: 1.677849ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:10Z" - latency: 2.129772ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:10Z" - latency: 2.001787ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:10Z" - latency: 1.992693ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:10Z" - latency: 2.062345ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:40:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:21:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-205-to-network-check-target-ip-10-0-141-59 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-205.ec2.internal uid: 272e5c55-2d27-40ff-b166-34756b7e7524 resourceVersion: "43701" uid: 3d11d07c-1910-4e87-99e9-5840452651ca spec: sourcePod: network-check-source-7f44b6dd87-h6lcj targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:28:10Z" message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.365331ms message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:10Z" - latency: 2.312113ms message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:10Z" - latency: 2.402265ms message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:10Z" - latency: 2.430819ms message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:10Z" - latency: 2.51085ms message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:10Z" - latency: 2.286435ms message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:10Z" - latency: 2.634571ms message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:10Z" - latency: 2.499166ms message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:10Z" - latency: 1.957734ms message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:10Z" - latency: 2.392275ms message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:40:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:21:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-205-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-205.ec2.internal uid: 272e5c55-2d27-40ff-b166-34756b7e7524 resourceVersion: "45945" uid: 984bd37c-e809-4d3a-b19e-ae8ea69028ad spec: sourcePod: network-check-source-7f44b6dd87-h6lcj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T17:27:10Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.048111ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:51:10Z" - latency: 1.780912ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:51:10Z" - latency: 903.293µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:50:10Z" - latency: 2.159269ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:50:10Z" - latency: 773.543µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:10Z" - latency: 2.103234ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:49:10Z" - latency: 876.645µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:10Z" - latency: 1.816891ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:48:10Z" - latency: 845.959µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:10Z" - latency: 1.816531ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:47:10Z" kind: List metadata: resourceVersion: ""