apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T12:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-37-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-37.ec2.internal uid: 17187b0c-f8d9-44fe-83f3-4adb0b72921a resourceVersion: "62666" uid: 0efae046-7dff-4212-9b49-8f45030fc979 spec: sourcePod: network-check-source-7bc5b6bf85-6btjx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T12:20:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.089441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:55:06Z" - latency: 927.089µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:54:06Z" - latency: 1.071173ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:53:06Z" - latency: 1.238443ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:52:06Z" - latency: 1.031466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:51:06Z" - latency: 1.149254ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:50:06Z" - latency: 1.083704ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:49:06Z" - latency: 1.110424ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:48:06Z" - latency: 1.053121ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:47:06Z" - latency: 1.205878ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:46:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T12:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-37-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-37.ec2.internal uid: 17187b0c-f8d9-44fe-83f3-4adb0b72921a resourceVersion: "62669" uid: 11586de0-b59e-4836-a248-28836ddc0fec spec: sourcePod: network-check-source-7bc5b6bf85-6btjx targetEndpoint: a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T12:19:07Z" message: 'load-balancer-api-external: tcp connection to a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.545353ms message: 'load-balancer-api-external: tcp connection to a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:55:06Z" - latency: 9.102072ms message: 'load-balancer-api-external: resolved host name a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T12:55:06Z" - latency: 4.929499ms message: 'load-balancer-api-external: tcp connection to a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:54:06Z" - latency: 8.584219ms message: 'load-balancer-api-external: resolved host name a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T12:54:06Z" - latency: 4.217717ms message: 'load-balancer-api-external: tcp connection to a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:53:06Z" - latency: 12.380838ms message: 'load-balancer-api-external: resolved host name a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T12:53:06Z" - latency: 6.592116ms message: 'load-balancer-api-external: tcp connection to a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:52:06Z" - latency: 8.528205ms message: 'load-balancer-api-external: resolved host name a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T12:52:06Z" - latency: 5.621612ms message: 'load-balancer-api-external: tcp connection to a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:51:06Z" - latency: 8.580125ms message: 'load-balancer-api-external: resolved host name a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T12:51:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T12:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-37-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-37.ec2.internal uid: 17187b0c-f8d9-44fe-83f3-4adb0b72921a resourceVersion: "62668" uid: 5ff327b0-16eb-42f3-a8d8-bc821992f9bc spec: sourcePod: network-check-source-7bc5b6bf85-6btjx targetEndpoint: a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T12:19:06Z" message: 'load-balancer-api-internal: tcp connection to a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.559015ms message: 'load-balancer-api-internal: tcp connection to a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:55:06Z" - latency: 9.047069ms message: 'load-balancer-api-internal: resolved host name a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T12:55:06Z" - latency: 4.94851ms message: 'load-balancer-api-internal: tcp connection to a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:54:06Z" - latency: 8.629395ms message: 'load-balancer-api-internal: resolved host name a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T12:54:06Z" - latency: 3.834829ms message: 'load-balancer-api-internal: tcp connection to a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:53:06Z" - latency: 12.413881ms message: 'load-balancer-api-internal: resolved host name a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T12:53:06Z" - latency: 6.573902ms message: 'load-balancer-api-internal: tcp connection to a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:52:06Z" - latency: 8.596671ms message: 'load-balancer-api-internal: resolved host name a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T12:52:06Z" - latency: 5.607007ms message: 'load-balancer-api-internal: tcp connection to a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:51:06Z" - latency: 8.611638ms message: 'load-balancer-api-internal: resolved host name a64858f290c054d26a7968a74e2f324e-5059e8fd93225ac0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T12:51:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T12:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-37-to-network-check-target-ip-10-0-133-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-37.ec2.internal uid: 17187b0c-f8d9-44fe-83f3-4adb0b72921a resourceVersion: "62665" uid: 9187681e-2f57-4c89-9144-d36871061ba1 spec: sourcePod: network-check-source-7bc5b6bf85-6btjx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T12:20:06Z" message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.506935ms message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:55:06Z" - latency: 2.577177ms message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:54:06Z" - latency: 2.451056ms message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:53:06Z" - latency: 2.443812ms message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:52:06Z" - latency: 2.49387ms message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:51:06Z" - latency: 2.479459ms message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:50:06Z" - latency: 2.405728ms message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:49:06Z" - latency: 2.562038ms message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:48:06Z" - latency: 2.60473ms message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:47:06Z" - latency: 2.868644ms message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:46:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T12:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-37-to-network-check-target-ip-10-0-137-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-37.ec2.internal uid: 17187b0c-f8d9-44fe-83f3-4adb0b72921a resourceVersion: "62664" uid: 324fee3e-becc-4847-8dc2-6d1a3db8625d spec: sourcePod: network-check-source-7bc5b6bf85-6btjx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T12:20:06Z" message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.215407ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:55:06Z" - latency: 2.567731ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:54:06Z" - latency: 2.005982ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:53:06Z" - latency: 2.389477ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:52:06Z" - latency: 2.666181ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:51:06Z" - latency: 2.196585ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:50:06Z" - latency: 2.784266ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:49:06Z" - latency: 2.241592ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:48:06Z" - latency: 2.304902ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:47:06Z" - latency: 2.373912ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:46:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T12:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-37-to-network-check-target-ip-10-0-138-37 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-37.ec2.internal uid: 17187b0c-f8d9-44fe-83f3-4adb0b72921a resourceVersion: "62662" uid: 6e44b7ef-957d-4051-b734-a37992c82727 spec: sourcePod: network-check-source-7bc5b6bf85-6btjx targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-23T12:20:06Z" message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 912.682µs message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:55:06Z" - latency: 923.067µs message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:54:06Z" - latency: 872.629µs message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:53:06Z" - latency: 1.062586ms message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:52:06Z" - latency: 944.305µs message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:51:06Z" - latency: 1.402255ms message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:50:06Z" - latency: 918.947µs message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:49:06Z" - latency: 1.410657ms message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:48:06Z" - latency: 934.62µs message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:47:06Z" - latency: 1.267227ms message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:46:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T12:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-37-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-37.ec2.internal uid: 17187b0c-f8d9-44fe-83f3-4adb0b72921a resourceVersion: "62663" uid: 06b44acf-127b-425d-8df8-4d4a160aa2aa spec: sourcePod: network-check-source-7bc5b6bf85-6btjx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T12:19:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 789.438µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:55:06Z" - latency: 1.633817ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T12:55:06Z" - latency: 778.913µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:54:06Z" - latency: 1.881518ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T12:54:06Z" - latency: 1.07998ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:53:06Z" - latency: 2.27939ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T12:53:06Z" - latency: 930.071µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:52:06Z" - latency: 2.233346ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T12:52:06Z" - latency: 927.308µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T12:51:06Z" - latency: 1.671654ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T12:51:06Z" kind: List metadata: resourceVersion: ""