apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:44:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-11-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-11.ec2.internal uid: 027ff2d4-2aeb-4f54-9cd0-4e09be531eae resourceVersion: "37101" uid: 430b7664-37a0-4e39-93ca-57ba71a86e8b spec: sourcePod: network-check-source-6f8b768455-h5ntg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-16T18:51:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 907.12µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:33:05Z" - latency: 866.761µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:32:05Z" - latency: 1.350291ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:31:05Z" - latency: 794.331µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:30:05Z" - latency: 933.989µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:29:05Z" - latency: 865.324µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:28:05Z" - latency: 874.851µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:27:05Z" - latency: 1.02368ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:26:05Z" - latency: 1.247308ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:25:05Z" - latency: 1.035746ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:24:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:44:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-11-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-11.ec2.internal uid: 027ff2d4-2aeb-4f54-9cd0-4e09be531eae resourceVersion: "36729" uid: b7ca5d9b-f1e7-4d6e-80d8-c9fc3bb9cf7b spec: sourcePod: network-check-source-6f8b768455-h5ntg targetEndpoint: a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T18:50:05Z" message: 'load-balancer-api-external: tcp connection to a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.964393ms message: 'load-balancer-api-external: tcp connection to a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:32:05Z" - latency: 7.396064ms message: 'load-balancer-api-external: resolved host name a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:32:05Z" - latency: 4.994188ms message: 'load-balancer-api-external: tcp connection to a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:31:05Z" - latency: 8.7752ms message: 'load-balancer-api-external: resolved host name a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:31:05Z" - latency: 5.606082ms message: 'load-balancer-api-external: tcp connection to a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:30:05Z" - latency: 8.514518ms message: 'load-balancer-api-external: resolved host name a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:30:05Z" - latency: 3.579639ms message: 'load-balancer-api-external: tcp connection to a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:29:05Z" - latency: 7.416472ms message: 'load-balancer-api-external: resolved host name a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:29:05Z" - latency: 6.234973ms message: 'load-balancer-api-external: tcp connection to a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:28:05Z" - latency: 8.170394ms message: 'load-balancer-api-external: resolved host name a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:28:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:44:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-11-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-11.ec2.internal uid: 027ff2d4-2aeb-4f54-9cd0-4e09be531eae resourceVersion: "36730" uid: 7a996833-7dfb-4936-a55e-e8f7af66f5a3 spec: sourcePod: network-check-source-6f8b768455-h5ntg targetEndpoint: a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T18:50:05Z" message: 'load-balancer-api-internal: tcp connection to a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.0629ms message: 'load-balancer-api-internal: tcp connection to a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:32:05Z" - latency: 7.420999ms message: 'load-balancer-api-internal: resolved host name a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:32:05Z" - latency: 4.986415ms message: 'load-balancer-api-internal: tcp connection to a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:31:05Z" - latency: 8.742931ms message: 'load-balancer-api-internal: resolved host name a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:31:05Z" - latency: 5.702015ms message: 'load-balancer-api-internal: tcp connection to a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:30:05Z" - latency: 8.533901ms message: 'load-balancer-api-internal: resolved host name a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:30:05Z" - latency: 4.722014ms message: 'load-balancer-api-internal: tcp connection to a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:29:05Z" - latency: 7.492469ms message: 'load-balancer-api-internal: resolved host name a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:29:05Z" - latency: 6.521699ms message: 'load-balancer-api-internal: tcp connection to a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:28:05Z" - latency: 8.219005ms message: 'load-balancer-api-internal: resolved host name a07401aff5db543f08534d2730386358-d8ec3ebe09596537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:28:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:44:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-11-to-network-check-target-ip-10-0-135-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-11.ec2.internal uid: 027ff2d4-2aeb-4f54-9cd0-4e09be531eae resourceVersion: "37098" uid: 1e333708-eb36-47b5-bcf7-84947eced63e spec: sourcePod: network-check-source-6f8b768455-h5ntg targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-16T18:51:05Z" message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 830.14µs message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:33:05Z" - latency: 872.796µs message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:32:05Z" - latency: 1.564291ms message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:31:05Z" - latency: 1.117736ms message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:30:05Z" - latency: 912.8µs message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:29:05Z" - latency: 867.779µs message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:28:05Z" - latency: 1.299536ms message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:27:05Z" - latency: 959.808µs message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:26:05Z" - latency: 1.276761ms message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:25:05Z" - latency: 1.097119ms message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:24:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:44:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-11-to-network-check-target-ip-10-0-136-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-11.ec2.internal uid: 027ff2d4-2aeb-4f54-9cd0-4e09be531eae resourceVersion: "37099" uid: 827d3f48-7172-4772-b087-a0a5a8a01cf5 spec: sourcePod: network-check-source-6f8b768455-h5ntg targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-16T18:51:05Z" message: 'network-check-target-ip-10-0-136-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.943833ms message: 'network-check-target-ip-10-0-136-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:33:05Z" - latency: 1.990401ms message: 'network-check-target-ip-10-0-136-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:32:05Z" - latency: 2.151575ms message: 'network-check-target-ip-10-0-136-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:31:05Z" - latency: 1.893442ms message: 'network-check-target-ip-10-0-136-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:30:05Z" - latency: 1.957207ms message: 'network-check-target-ip-10-0-136-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:29:05Z" - latency: 2.073388ms message: 'network-check-target-ip-10-0-136-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:28:05Z" - latency: 2.096811ms message: 'network-check-target-ip-10-0-136-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:27:05Z" - latency: 2.248492ms message: 'network-check-target-ip-10-0-136-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:26:05Z" - latency: 2.024798ms message: 'network-check-target-ip-10-0-136-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:25:05Z" - latency: 1.96666ms message: 'network-check-target-ip-10-0-136-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:24:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:44:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-11-to-network-check-target-ip-10-0-139-72 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-11.ec2.internal uid: 027ff2d4-2aeb-4f54-9cd0-4e09be531eae resourceVersion: "37100" uid: 6ff44829-ad41-4103-8674-5af899326504 spec: sourcePod: network-check-source-6f8b768455-h5ntg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-16T18:51:05Z" message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.365034ms message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:33:05Z" - latency: 2.327083ms message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:32:05Z" - latency: 2.539729ms message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:31:05Z" - latency: 2.373123ms message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:30:05Z" - latency: 2.323516ms message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:29:05Z" - latency: 2.483136ms message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:28:05Z" - latency: 2.387203ms message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:27:05Z" - latency: 2.413538ms message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:26:05Z" - latency: 2.382328ms message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:25:05Z" - latency: 2.374839ms message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:24:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:44:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-11-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-11.ec2.internal uid: 027ff2d4-2aeb-4f54-9cd0-4e09be531eae resourceVersion: "36728" uid: df8dce8c-b6da-45b2-8437-1b16a19483c3 spec: sourcePod: network-check-source-6f8b768455-h5ntg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-16T18:50:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.20072ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:32:05Z" - latency: 1.656026ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:32:05Z" - latency: 903.742µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:31:05Z" - latency: 2.213885ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:31:05Z" - latency: 885.902µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:30:05Z" - latency: 1.784387ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:30:05Z" - latency: 858.991µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:29:05Z" - latency: 1.981965ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:29:05Z" - latency: 1.162291ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:28:05Z" - latency: 1.682758ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:28:05Z" kind: List metadata: resourceVersion: ""