apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:34:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-27-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-27.ec2.internal uid: dfba8160-af5a-4547-bf6c-27b5ce9e7436 resourceVersion: "18707" uid: 228e47ec-c916-4166-82fd-482ad60a834e spec: sourcePod: network-check-source-8894fc9bd-m789j targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T21:42:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 964.419µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:49:00Z" - latency: 910.117µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:48:00Z" - latency: 865.779µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:47:00Z" - latency: 1.09805ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:46:00Z" - latency: 1.353192ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:45:00Z" - latency: 920.424µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:44:00Z" - latency: 823.719µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:43:00Z" - latency: 1.111067ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:42:00Z" - latency: 912.931µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:41:00Z" - latency: 1.042476ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:40:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:34:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-27-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-27.ec2.internal uid: dfba8160-af5a-4547-bf6c-27b5ce9e7436 resourceVersion: "20861" uid: 24958294-c787-44cd-9779-2dd5ecf2fa76 spec: sourcePod: network-check-source-8894fc9bd-m789j targetEndpoint: a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:41:00Z" message: 'load-balancer-api-external: tcp connection to a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.8953ms message: 'load-balancer-api-external: tcp connection to a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:53:00Z" - latency: 6.783435ms message: 'load-balancer-api-external: resolved host name a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:53:00Z" - latency: 4.636005ms message: 'load-balancer-api-external: tcp connection to a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:52:00Z" - latency: 6.370657ms message: 'load-balancer-api-external: resolved host name a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:52:00Z" - latency: 4.121119ms message: 'load-balancer-api-external: tcp connection to a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:51:00Z" - latency: 6.727567ms message: 'load-balancer-api-external: resolved host name a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:51:00Z" - latency: 4.325414ms message: 'load-balancer-api-external: tcp connection to a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:50:00Z" - latency: 7.203388ms message: 'load-balancer-api-external: resolved host name a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:50:00Z" - latency: 5.637493ms message: 'load-balancer-api-external: tcp connection to a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:49:00Z" - latency: 6.476461ms message: 'load-balancer-api-external: resolved host name a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:49:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:34:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-27-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-27.ec2.internal uid: dfba8160-af5a-4547-bf6c-27b5ce9e7436 resourceVersion: "20860" uid: cebb4d5d-f2e0-426c-b65f-f14c8906600d spec: sourcePod: network-check-source-8894fc9bd-m789j targetEndpoint: a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:41:00Z" message: 'load-balancer-api-internal: tcp connection to a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.385728ms message: 'load-balancer-api-internal: tcp connection to a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:53:00Z" - latency: 6.731297ms message: 'load-balancer-api-internal: resolved host name a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:53:00Z" - latency: 4.688678ms message: 'load-balancer-api-internal: tcp connection to a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:52:00Z" - latency: 6.294079ms message: 'load-balancer-api-internal: resolved host name a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:52:00Z" - latency: 3.323324ms message: 'load-balancer-api-internal: tcp connection to a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:51:00Z" - latency: 6.630517ms message: 'load-balancer-api-internal: resolved host name a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:51:00Z" - latency: 4.341472ms message: 'load-balancer-api-internal: tcp connection to a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:50:00Z" - latency: 7.253093ms message: 'load-balancer-api-internal: resolved host name a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:50:00Z" - latency: 5.573783ms message: 'load-balancer-api-internal: tcp connection to a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:49:00Z" - latency: 6.579452ms message: 'load-balancer-api-internal: resolved host name a0f69c500efa64a1ca520c6849262390-71c93e29e5a731ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:49:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:34:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-27-to-network-check-target-ip-10-0-134-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-27.ec2.internal uid: dfba8160-af5a-4547-bf6c-27b5ce9e7436 resourceVersion: "18706" uid: c3956271-4cef-44ea-a5ee-fc6d61701264 spec: sourcePod: network-check-source-8894fc9bd-m789j targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:42:00Z" message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.933426ms message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:49:00Z" - latency: 1.905602ms message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:48:00Z" - latency: 1.909973ms message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:47:00Z" - latency: 2.139298ms message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:46:00Z" - latency: 2.243601ms message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:45:00Z" - latency: 2.09691ms message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:44:00Z" - latency: 1.856362ms message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:43:00Z" - latency: 2.255813ms message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:42:00Z" - latency: 1.890473ms message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:41:00Z" - latency: 2.134476ms message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:40:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:34:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-27-to-network-check-target-ip-10-0-135-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-27.ec2.internal uid: dfba8160-af5a-4547-bf6c-27b5ce9e7436 resourceVersion: "18704" uid: 9a771e9a-2525-434e-94b3-8da57bcbf380 spec: sourcePod: network-check-source-8894fc9bd-m789j targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:42:00Z" message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 769.164µs message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:49:00Z" - latency: 690.795µs message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:48:00Z" - latency: 884.853µs message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:47:00Z" - latency: 799.752µs message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:46:00Z" - latency: 1.343645ms message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:45:00Z" - latency: 796.227µs message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:44:00Z" - latency: 794.355µs message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:43:00Z" - latency: 790.265µs message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:42:00Z" - latency: 693.802µs message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:41:00Z" - latency: 936.862µs message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:40:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:34:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-27-to-network-check-target-ip-10-0-142-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-27.ec2.internal uid: dfba8160-af5a-4547-bf6c-27b5ce9e7436 resourceVersion: "18705" uid: cf8ddd9e-790f-460b-92be-4ddd7d12f284 spec: sourcePod: network-check-source-8894fc9bd-m789j targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:42:00Z" message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.885362ms message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:49:00Z" - latency: 1.941436ms message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:48:00Z" - latency: 1.877515ms message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:47:00Z" - latency: 2.207781ms message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:46:00Z" - latency: 2.628625ms message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:45:00Z" - latency: 1.937736ms message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:44:00Z" - latency: 1.971705ms message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:43:00Z" - latency: 1.730481ms message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:42:00Z" - latency: 2.012991ms message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:41:00Z" - latency: 2.057136ms message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:40:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:34:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-27-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-27.ec2.internal uid: dfba8160-af5a-4547-bf6c-27b5ce9e7436 resourceVersion: "20859" uid: e2fd0e9a-1a37-43cb-9878-50e785b204b8 spec: sourcePod: network-check-source-8894fc9bd-m789j targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T21:41:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 841.97µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:53:00Z" - latency: 3.996242ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:53:00Z" - latency: 1.372429ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:52:00Z" - latency: 1.478642ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:52:00Z" - latency: 848.246µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:51:00Z" - latency: 1.531269ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:51:00Z" - latency: 812.942µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:50:00Z" - latency: 1.74095ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:50:00Z" - latency: 910.957µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:49:00Z" - latency: 1.820781ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:49:00Z" kind: List metadata: resourceVersion: ""