apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:44:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-190-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-190.ec2.internal uid: 929e9641-0a5e-42e0-838c-9d1cb65ba966 resourceVersion: "67473" uid: 057793e7-1669-450e-9b39-b06499e6deb0 spec: sourcePod: network-check-source-6f8b768455-qfll2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-16T12:51:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 842.108µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:19:24Z" - latency: 928.595µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:18:24Z" - latency: 1.166504ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:17:24Z" - latency: 830.447µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:16:24Z" - latency: 1.214663ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:15:24Z" - latency: 1.403587ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:14:24Z" - latency: 1.285988ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:13:24Z" - latency: 1.165611ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:12:24Z" - latency: 1.259511ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:11:24Z" - latency: 874.83µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:10:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:44:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-190-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-190.ec2.internal uid: 929e9641-0a5e-42e0-838c-9d1cb65ba966 resourceVersion: "68184" uid: 89b6eb98-db80-4d0d-b424-d9cec377f9d6 spec: sourcePod: network-check-source-6f8b768455-qfll2 targetEndpoint: a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T12:50:24Z" message: 'load-balancer-api-external: tcp connection to a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.889024ms message: 'load-balancer-api-external: tcp connection to a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:20:24Z" - latency: 10.901935ms message: 'load-balancer-api-external: resolved host name a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T13:20:24Z" - latency: 6.473361ms message: 'load-balancer-api-external: tcp connection to a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:19:24Z" - latency: 7.538008ms message: 'load-balancer-api-external: resolved host name a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T13:19:24Z" - latency: 4.796746ms message: 'load-balancer-api-external: tcp connection to a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:18:24Z" - latency: 7.65631ms message: 'load-balancer-api-external: resolved host name a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T13:18:24Z" - latency: 5.822782ms message: 'load-balancer-api-external: tcp connection to a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:17:24Z" - latency: 7.201686ms message: 'load-balancer-api-external: resolved host name a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T13:17:24Z" - latency: 5.774515ms message: 'load-balancer-api-external: tcp connection to a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:16:24Z" - latency: 7.363616ms message: 'load-balancer-api-external: resolved host name a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T13:16:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:44:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-190-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-190.ec2.internal uid: 929e9641-0a5e-42e0-838c-9d1cb65ba966 resourceVersion: "68183" uid: 57e088ee-965e-4b00-a07c-e425e4ef1dc5 spec: sourcePod: network-check-source-6f8b768455-qfll2 targetEndpoint: a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T12:50:24Z" message: 'load-balancer-api-internal: tcp connection to a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.885764ms message: 'load-balancer-api-internal: tcp connection to a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:20:24Z" - latency: 10.878804ms message: 'load-balancer-api-internal: resolved host name a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T13:20:24Z" - latency: 6.430386ms message: 'load-balancer-api-internal: tcp connection to a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:19:24Z" - latency: 7.503138ms message: 'load-balancer-api-internal: resolved host name a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T13:19:24Z" - latency: 4.804278ms message: 'load-balancer-api-internal: tcp connection to a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:18:24Z" - latency: 7.698259ms message: 'load-balancer-api-internal: resolved host name a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T13:18:24Z" - latency: 5.847552ms message: 'load-balancer-api-internal: tcp connection to a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:17:24Z" - latency: 7.209119ms message: 'load-balancer-api-internal: resolved host name a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T13:17:24Z" - latency: 4.884463ms message: 'load-balancer-api-internal: tcp connection to a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:16:24Z" - latency: 7.189307ms message: 'load-balancer-api-internal: resolved host name a9b6d18375cc3425db66e79ffa5f273a-8c822ea21934cb8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T13:16:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:44:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-190-to-network-check-target-ip-10-0-128-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-190.ec2.internal uid: 929e9641-0a5e-42e0-838c-9d1cb65ba966 resourceVersion: "67471" uid: 6deb9b32-3086-4e00-8745-8b0588d275f3 spec: sourcePod: network-check-source-6f8b768455-qfll2 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-16T12:51:24Z" message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.083538ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:19:24Z" - latency: 2.339279ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:18:24Z" - latency: 2.062756ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:17:24Z" - latency: 2.418275ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:16:24Z" - latency: 2.30809ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:15:24Z" - latency: 2.484169ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:14:24Z" - latency: 2.572397ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:13:24Z" - latency: 2.345541ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:12:24Z" - latency: 2.347362ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:11:24Z" - latency: 2.118274ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:10:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:44:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-190-to-network-check-target-ip-10-0-133-190 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-190.ec2.internal uid: 929e9641-0a5e-42e0-838c-9d1cb65ba966 resourceVersion: "67470" uid: 59878257-800e-48f4-8f94-7b8432694fef spec: sourcePod: network-check-source-6f8b768455-qfll2 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-16T12:51:24Z" message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.001492ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:19:24Z" - latency: 1.211439ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:18:24Z" - latency: 896.561µs message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:17:24Z" - latency: 1.550314ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:16:24Z" - latency: 947.692µs message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:15:24Z" - latency: 1.473363ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:14:24Z" - latency: 960.895µs message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:13:24Z" - latency: 1.00562ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:12:24Z" - latency: 979.355µs message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:11:24Z" - latency: 787.806µs message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:10:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:44:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-190-to-network-check-target-ip-10-0-143-72 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-190.ec2.internal uid: 929e9641-0a5e-42e0-838c-9d1cb65ba966 resourceVersion: "67472" uid: aeb311c9-bfaf-43a7-b309-6aab2dcdfc69 spec: sourcePod: network-check-source-6f8b768455-qfll2 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-16T12:51:24Z" message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.94863ms message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:19:24Z" - latency: 2.063733ms message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:18:24Z" - latency: 1.873405ms message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:17:24Z" - latency: 1.611552ms message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:16:24Z" - latency: 1.953491ms message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:15:24Z" - latency: 2.449974ms message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:14:24Z" - latency: 2.460172ms message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:13:24Z" - latency: 2.25965ms message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:12:24Z" - latency: 1.965573ms message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:11:24Z" - latency: 1.767432ms message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:10:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:44:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-190-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-190.ec2.internal uid: 929e9641-0a5e-42e0-838c-9d1cb65ba966 resourceVersion: "68180" uid: 4d3fee3a-923c-41d1-be4e-bbc0a609812a spec: sourcePod: network-check-source-6f8b768455-qfll2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-16T12:50:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 789.014µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:20:24Z" - latency: 2.728825ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T13:20:24Z" - latency: 939.145µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:19:24Z" - latency: 1.964279ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T13:19:24Z" - latency: 1.32013ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:18:24Z" - latency: 1.780051ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T13:18:24Z" - latency: 1.13439ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:17:24Z" - latency: 1.749996ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T13:17:24Z" - latency: 810.273µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T13:16:24Z" - latency: 2.166196ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T13:16:24Z" kind: List metadata: resourceVersion: ""