apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-111-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-111.ec2.internal uid: 67aecb85-7703-4005-9d23-7b2b04c5983f resourceVersion: "25687" uid: 4df83a45-45f1-42be-bc0f-5c5f300bd8a2 spec: sourcePod: network-check-source-7d88cb55d8-fgw4v targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T10:39:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 924.956µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:00:21Z" - latency: 1.005317ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:59:21Z" - latency: 1.101505ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:58:21Z" - latency: 985.183µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:57:21Z" - latency: 1.244501ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:56:21Z" - latency: 1.134151ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:55:21Z" - latency: 932.086µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:54:21Z" - latency: 925.924µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:53:21Z" - latency: 1.426923ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:52:21Z" - latency: 1.062601ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:51:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-111-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-111.ec2.internal uid: 67aecb85-7703-4005-9d23-7b2b04c5983f resourceVersion: "26802" uid: f3671eb3-685f-4f97-9733-9ebcf6bcf9d5 spec: sourcePod: network-check-source-7d88cb55d8-fgw4v targetEndpoint: aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T10:38:21Z" message: 'load-balancer-api-external: tcp connection to aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.758777ms message: 'load-balancer-api-external: tcp connection to aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:02:21Z" - latency: 6.663123ms message: 'load-balancer-api-external: resolved host name aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:02:21Z" - latency: 5.427989ms message: 'load-balancer-api-external: tcp connection to aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:01:21Z" - latency: 7.834233ms message: 'load-balancer-api-external: resolved host name aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:01:21Z" - latency: 5.615774ms message: 'load-balancer-api-external: tcp connection to aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:00:21Z" - latency: 7.577485ms message: 'load-balancer-api-external: resolved host name aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:00:21Z" - latency: 5.028577ms message: 'load-balancer-api-external: tcp connection to aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:59:21Z" - latency: 7.109896ms message: 'load-balancer-api-external: resolved host name aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T10:59:21Z" - latency: 4.650472ms message: 'load-balancer-api-external: tcp connection to aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:58:21Z" - latency: 7.338499ms message: 'load-balancer-api-external: resolved host name aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T10:58:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-111-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-111.ec2.internal uid: 67aecb85-7703-4005-9d23-7b2b04c5983f resourceVersion: "26803" uid: 33999a75-7295-4e3b-9fb2-532443ee555f spec: sourcePod: network-check-source-7d88cb55d8-fgw4v targetEndpoint: aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T10:38:21Z" message: 'load-balancer-api-internal: tcp connection to aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.766795ms message: 'load-balancer-api-internal: tcp connection to aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:02:21Z" - latency: 6.586757ms message: 'load-balancer-api-internal: resolved host name aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:02:21Z" - latency: 4.767878ms message: 'load-balancer-api-internal: tcp connection to aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:01:21Z" - latency: 7.796948ms message: 'load-balancer-api-internal: resolved host name aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:01:21Z" - latency: 5.682986ms message: 'load-balancer-api-internal: tcp connection to aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:00:21Z" - latency: 7.517385ms message: 'load-balancer-api-internal: resolved host name aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:00:21Z" - latency: 4.100311ms message: 'load-balancer-api-internal: tcp connection to aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:59:21Z" - latency: 7.184306ms message: 'load-balancer-api-internal: resolved host name aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T10:59:21Z" - latency: 4.285472ms message: 'load-balancer-api-internal: tcp connection to aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:58:21Z" - latency: 7.414784ms message: 'load-balancer-api-internal: resolved host name aae0bb24fa90045569a013bee65d6aeb-cff4e5ff9402362b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T10:58:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-111-to-network-check-target-ip-10-0-133-233 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-111.ec2.internal uid: 67aecb85-7703-4005-9d23-7b2b04c5983f resourceVersion: "25686" uid: f56615cc-599f-4cf2-8e74-b1ebabe4148b spec: sourcePod: network-check-source-7d88cb55d8-fgw4v targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T10:39:21Z" message: 'network-check-target-ip-10-0-133-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.122024ms message: 'network-check-target-ip-10-0-133-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:00:21Z" - latency: 1.90531ms message: 'network-check-target-ip-10-0-133-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:59:21Z" - latency: 2.283009ms message: 'network-check-target-ip-10-0-133-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:58:21Z" - latency: 2.376407ms message: 'network-check-target-ip-10-0-133-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:57:21Z" - latency: 2.059234ms message: 'network-check-target-ip-10-0-133-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:56:21Z" - latency: 2.248355ms message: 'network-check-target-ip-10-0-133-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:55:21Z" - latency: 2.408059ms message: 'network-check-target-ip-10-0-133-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:54:21Z" - latency: 2.263888ms message: 'network-check-target-ip-10-0-133-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:53:21Z" - latency: 2.503071ms message: 'network-check-target-ip-10-0-133-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:52:21Z" - latency: 2.032966ms message: 'network-check-target-ip-10-0-133-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:51:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-111-to-network-check-target-ip-10-0-137-111 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-111.ec2.internal uid: 67aecb85-7703-4005-9d23-7b2b04c5983f resourceVersion: "25684" uid: 53c41e8d-ffac-4b5f-9a22-8a3b01f13496 spec: sourcePod: network-check-source-7d88cb55d8-fgw4v targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T10:39:21Z" message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 888.865µs message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:00:21Z" - latency: 793.949µs message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:59:21Z" - latency: 877.573µs message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:58:21Z" - latency: 771.348µs message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:57:21Z" - latency: 846.422µs message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:56:21Z" - latency: 877.184µs message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:55:21Z" - latency: 872.941µs message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:54:21Z" - latency: 886.259µs message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:53:21Z" - latency: 1.561205ms message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:52:21Z" - latency: 878.447µs message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:51:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-111-to-network-check-target-ip-10-0-138-43 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-111.ec2.internal uid: 67aecb85-7703-4005-9d23-7b2b04c5983f resourceVersion: "25685" uid: e230da32-bd2d-4e46-9438-87efb7b93ad4 spec: sourcePod: network-check-source-7d88cb55d8-fgw4v targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T10:39:21Z" message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.070903ms message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:00:21Z" - latency: 2.46251ms message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:59:21Z" - latency: 2.338641ms message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:58:21Z" - latency: 2.087704ms message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:57:21Z" - latency: 2.292489ms message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:56:21Z" - latency: 2.185772ms message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:55:21Z" - latency: 2.100479ms message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:54:21Z" - latency: 1.997404ms message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:53:21Z" - latency: 2.090138ms message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:52:21Z" - latency: 2.617247ms message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:51:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-111-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-111.ec2.internal uid: 67aecb85-7703-4005-9d23-7b2b04c5983f resourceVersion: "26801" uid: a48923b5-c332-4f2a-a379-166935a00fe0 spec: sourcePod: network-check-source-7d88cb55d8-fgw4v targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T10:38:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 838.578µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:02:21Z" - latency: 1.61791ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T11:02:21Z" - latency: 881.193µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:01:21Z" - latency: 2.062496ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T11:01:21Z" - latency: 1.207535ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:00:21Z" - latency: 1.76055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T11:00:21Z" - latency: 895.873µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:59:21Z" - latency: 1.542548ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T10:59:21Z" - latency: 1.330011ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T10:58:21Z" - latency: 1.778841ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T10:58:21Z" kind: List metadata: resourceVersion: ""