apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:57:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-87-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-87.ec2.internal uid: 46211dd9-948a-4956-a3a6-d2cef8ece05c resourceVersion: "39057" uid: 346027e1-a73f-4c1a-b6dd-991d459fc728 spec: sourcePod: network-check-source-8894fc9bd-pvs64 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-23T18:04:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.146324ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:53:15Z" - latency: 1.257478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:52:15Z" - latency: 1.15535ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:51:15Z" - latency: 1.248789ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:50:15Z" - latency: 948.251µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:49:15Z" - latency: 1.018858ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:48:15Z" - latency: 990.687µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:47:15Z" - latency: 989.484µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:46:15Z" - latency: 1.173797ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:45:15Z" - latency: 1.255585ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:57:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-87-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-87.ec2.internal uid: 46211dd9-948a-4956-a3a6-d2cef8ece05c resourceVersion: "41124" uid: e75d608a-ad7b-4b07-8ad6-40af1aa1af67 spec: sourcePod: network-check-source-8894fc9bd-pvs64 targetEndpoint: a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T18:03:15Z" message: 'load-balancer-api-external: tcp connection to a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.223829ms message: 'load-balancer-api-external: tcp connection to a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:57:15Z" - latency: 7.803368ms message: 'load-balancer-api-external: resolved host name a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:57:15Z" - latency: 4.555344ms message: 'load-balancer-api-external: tcp connection to a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:56:15Z" - latency: 7.490784ms message: 'load-balancer-api-external: resolved host name a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:56:15Z" - latency: 6.006255ms message: 'load-balancer-api-external: tcp connection to a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:55:15Z" - latency: 6.676045ms message: 'load-balancer-api-external: resolved host name a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:55:15Z" - latency: 4.537729ms message: 'load-balancer-api-external: tcp connection to a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:54:15Z" - latency: 7.367369ms message: 'load-balancer-api-external: resolved host name a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:54:15Z" - latency: 5.259005ms message: 'load-balancer-api-external: tcp connection to a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:53:15Z" - latency: 7.496938ms message: 'load-balancer-api-external: resolved host name a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:53:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:57:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-87-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-87.ec2.internal uid: 46211dd9-948a-4956-a3a6-d2cef8ece05c resourceVersion: "41123" uid: 7094c2e9-9c4c-4071-92e7-37c886fdf4cd spec: sourcePod: network-check-source-8894fc9bd-pvs64 targetEndpoint: a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T18:03:15Z" message: 'load-balancer-api-internal: tcp connection to a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.411791ms message: 'load-balancer-api-internal: tcp connection to a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:57:15Z" - latency: 7.722844ms message: 'load-balancer-api-internal: resolved host name a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:57:15Z" - latency: 4.533071ms message: 'load-balancer-api-internal: tcp connection to a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:56:15Z" - latency: 7.470716ms message: 'load-balancer-api-internal: resolved host name a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:56:15Z" - latency: 5.99671ms message: 'load-balancer-api-internal: tcp connection to a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:55:15Z" - latency: 6.716984ms message: 'load-balancer-api-internal: resolved host name a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:55:15Z" - latency: 6.794904ms message: 'load-balancer-api-internal: tcp connection to a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:54:15Z" - latency: 7.327924ms message: 'load-balancer-api-internal: resolved host name a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:54:15Z" - latency: 5.233596ms message: 'load-balancer-api-internal: tcp connection to a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:53:15Z" - latency: 7.549634ms message: 'load-balancer-api-internal: resolved host name a21c5265adcc745b293b9873476d3c7f-e79b334eb58dc85a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:53:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:57:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-87-to-network-check-target-ip-10-0-131-144 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-87.ec2.internal uid: 46211dd9-948a-4956-a3a6-d2cef8ece05c resourceVersion: "39055" uid: 6f76c469-9d6d-4558-b920-a7caffdf9f1a spec: sourcePod: network-check-source-8894fc9bd-pvs64 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-23T18:04:15Z" message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.875116ms message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:53:15Z" - latency: 2.425207ms message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:52:15Z" - latency: 1.866293ms message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:51:15Z" - latency: 1.76327ms message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:50:15Z" - latency: 1.89212ms message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:49:15Z" - latency: 1.745599ms message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:48:15Z" - latency: 1.962098ms message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:47:15Z" - latency: 1.745025ms message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:46:15Z" - latency: 1.75315ms message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:45:15Z" - latency: 1.787911ms message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:57:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-87-to-network-check-target-ip-10-0-135-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-87.ec2.internal uid: 46211dd9-948a-4956-a3a6-d2cef8ece05c resourceVersion: "39054" uid: 11c42dda-c8c2-4339-8ffd-452712535abf spec: sourcePod: network-check-source-8894fc9bd-pvs64 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-23T18:04:15Z" message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 878.223µs message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:53:15Z" - latency: 1.303794ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:52:15Z" - latency: 1.069034ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:51:15Z" - latency: 895.029µs message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:50:15Z" - latency: 743.83µs message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:49:15Z" - latency: 1.31684ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:48:15Z" - latency: 835.387µs message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:47:15Z" - latency: 872.093µs message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:46:15Z" - latency: 826.457µs message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:45:15Z" - latency: 658.794µs message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:57:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-87-to-network-check-target-ip-10-0-142-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-87.ec2.internal uid: 46211dd9-948a-4956-a3a6-d2cef8ece05c resourceVersion: "39056" uid: e18f536b-4ed7-4a47-8bfe-fa2fc3fc37f9 spec: sourcePod: network-check-source-8894fc9bd-pvs64 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-23T18:04:15Z" message: 'network-check-target-ip-10-0-142-106: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.967404ms message: 'network-check-target-ip-10-0-142-106: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:53:15Z" - latency: 1.617136ms message: 'network-check-target-ip-10-0-142-106: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:52:15Z" - latency: 2.119258ms message: 'network-check-target-ip-10-0-142-106: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:51:15Z" - latency: 1.920095ms message: 'network-check-target-ip-10-0-142-106: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:50:15Z" - latency: 2.078794ms message: 'network-check-target-ip-10-0-142-106: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:49:15Z" - latency: 2.076772ms message: 'network-check-target-ip-10-0-142-106: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:48:15Z" - latency: 1.849001ms message: 'network-check-target-ip-10-0-142-106: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:47:15Z" - latency: 1.637449ms message: 'network-check-target-ip-10-0-142-106: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:46:15Z" - latency: 1.705556ms message: 'network-check-target-ip-10-0-142-106: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:45:15Z" - latency: 1.776288ms message: 'network-check-target-ip-10-0-142-106: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:57:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-87-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-87.ec2.internal uid: 46211dd9-948a-4956-a3a6-d2cef8ece05c resourceVersion: "41122" uid: 86a3ab3a-9741-4cd8-824e-8fc099b9faf8 spec: sourcePod: network-check-source-8894fc9bd-pvs64 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-23T18:03:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 897.699µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:57:15Z" - latency: 1.67508ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:57:15Z" - latency: 966.236µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:56:15Z" - latency: 1.625017ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:56:15Z" - latency: 1.152897ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:55:15Z" - latency: 1.595468ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:55:15Z" - latency: 752.089µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:54:15Z" - latency: 1.873098ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:54:15Z" - latency: 996.373µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:53:15Z" - latency: 1.691203ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:53:15Z" kind: List metadata: resourceVersion: ""