apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:21:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-151-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-151.ec2.internal uid: d54b0f45-6f24-4d12-a114-ec6c53109749 resourceVersion: "55054" uid: 88be1102-9bda-468b-9ee1-3927384fba09 spec: sourcePod: network-check-source-869dcfcdcd-t89br targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T18:28:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.017628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:56:45Z" - latency: 860.631µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:55:45Z" - latency: 1.3226ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:54:45Z" - latency: 926.545µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:53:45Z" - latency: 991.235µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:52:45Z" - latency: 1.116971ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:51:45Z" - latency: 1.135746ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:50:45Z" - latency: 935.882µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:49:45Z" - latency: 1.161456ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:48:45Z" - latency: 972.15µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:47:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:21:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-151-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-151.ec2.internal uid: d54b0f45-6f24-4d12-a114-ec6c53109749 resourceVersion: "56145" uid: ca50bd8e-d1eb-4998-968a-106ea4545730 spec: sourcePod: network-check-source-869dcfcdcd-t89br targetEndpoint: acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T18:27:45Z" message: 'load-balancer-api-external: tcp connection to acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.582852ms message: 'load-balancer-api-external: tcp connection to acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:57:45Z" - latency: 9.81265ms message: 'load-balancer-api-external: resolved host name acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:57:45Z" - latency: 3.30394ms message: 'load-balancer-api-external: tcp connection to acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:56:45Z" - latency: 12.295598ms message: 'load-balancer-api-external: resolved host name acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:56:45Z" - latency: 5.432636ms message: 'load-balancer-api-external: tcp connection to acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:55:45Z" - latency: 10.818097ms message: 'load-balancer-api-external: resolved host name acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:55:45Z" - latency: 4.44733ms message: 'load-balancer-api-external: tcp connection to acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:54:45Z" - latency: 10.550398ms message: 'load-balancer-api-external: resolved host name acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:54:45Z" - latency: 3.438121ms message: 'load-balancer-api-external: tcp connection to acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:53:45Z" - latency: 9.32463ms message: 'load-balancer-api-external: resolved host name acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:53:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:21:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-151-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-151.ec2.internal uid: d54b0f45-6f24-4d12-a114-ec6c53109749 resourceVersion: "56144" uid: 15db6a02-dc27-4df8-b155-ac94dd38847b spec: sourcePod: network-check-source-869dcfcdcd-t89br targetEndpoint: acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T18:27:45Z" message: 'load-balancer-api-internal: tcp connection to acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.226053ms message: 'load-balancer-api-internal: tcp connection to acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:57:45Z" - latency: 9.831424ms message: 'load-balancer-api-internal: resolved host name acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:57:45Z" - latency: 4.782252ms message: 'load-balancer-api-internal: tcp connection to acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:56:45Z" - latency: 12.132815ms message: 'load-balancer-api-internal: resolved host name acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:56:45Z" - latency: 4.250901ms message: 'load-balancer-api-internal: tcp connection to acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:55:45Z" - latency: 10.906493ms message: 'load-balancer-api-internal: resolved host name acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:55:45Z" - latency: 4.540574ms message: 'load-balancer-api-internal: tcp connection to acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:54:45Z" - latency: 10.631952ms message: 'load-balancer-api-internal: resolved host name acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:54:45Z" - latency: 3.492664ms message: 'load-balancer-api-internal: tcp connection to acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:53:45Z" - latency: 9.365051ms message: 'load-balancer-api-internal: resolved host name acf8311961db64fd4a37062e1516f32e-2c49d6b0e4d378ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:53:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:21:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-151-to-network-check-target-ip-10-0-132-151 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-151.ec2.internal uid: d54b0f45-6f24-4d12-a114-ec6c53109749 resourceVersion: "55051" uid: 4c6fc20e-eab2-4813-bb56-7bcab0d76f3a spec: sourcePod: network-check-source-869dcfcdcd-t89br targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T18:28:45Z" message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.63638ms message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:56:45Z" - latency: 1.412597ms message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:55:45Z" - latency: 850.423µs message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:54:45Z" - latency: 1.422612ms message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:53:45Z" - latency: 850.255µs message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:52:45Z" - latency: 1.094793ms message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:51:45Z" - latency: 1.334635ms message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:50:45Z" - latency: 1.04561ms message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:49:45Z" - latency: 1.063457ms message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:48:45Z" - latency: 904.712µs message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:47:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:21:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-151-to-network-check-target-ip-10-0-141-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-151.ec2.internal uid: d54b0f45-6f24-4d12-a114-ec6c53109749 resourceVersion: "55052" uid: 76b9d242-78b9-47a6-be6f-29cd68a6c527 spec: sourcePod: network-check-source-869dcfcdcd-t89br targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T18:28:45Z" message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.526879ms message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:56:45Z" - latency: 2.893112ms message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:55:45Z" - latency: 2.722563ms message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:54:45Z" - latency: 2.396538ms message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:53:45Z" - latency: 2.414247ms message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:52:45Z" - latency: 2.82247ms message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:51:45Z" - latency: 2.639396ms message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:50:45Z" - latency: 2.546107ms message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:49:45Z" - latency: 2.425828ms message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:48:45Z" - latency: 2.314757ms message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:47:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:21:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-151-to-network-check-target-ip-10-0-143-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-151.ec2.internal uid: d54b0f45-6f24-4d12-a114-ec6c53109749 resourceVersion: "55053" uid: 343584dd-4776-4048-b9f1-1af931989c79 spec: sourcePod: network-check-source-869dcfcdcd-t89br targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T18:28:45Z" message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.603179ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:56:45Z" - latency: 2.122361ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:55:45Z" - latency: 2.71228ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:54:45Z" - latency: 2.781319ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:53:45Z" - latency: 2.175651ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:52:45Z" - latency: 2.73689ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:51:45Z" - latency: 2.205624ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:50:45Z" - latency: 2.643685ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:49:45Z" - latency: 2.525656ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:48:45Z" - latency: 2.867058ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:47:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:21:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-151-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-151.ec2.internal uid: d54b0f45-6f24-4d12-a114-ec6c53109749 resourceVersion: "56143" uid: 648ac996-64ab-4342-a2c7-57af9718d3c3 spec: sourcePod: network-check-source-869dcfcdcd-t89br targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T18:27:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 897.892µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:57:45Z" - latency: 1.715258ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:57:45Z" - latency: 823.954µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:56:45Z" - latency: 1.608793ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:56:45Z" - latency: 1.308945ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:55:45Z" - latency: 1.631435ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:55:45Z" - latency: 781.714µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:54:45Z" - latency: 2.038401ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:54:45Z" - latency: 819.538µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:53:45Z" - latency: 1.678458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:53:45Z" kind: List metadata: resourceVersion: ""