apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T03:06:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-172-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-172.ec2.internal uid: 98ba8341-7396-44b4-9f26-dc605ca65fa7 resourceVersion: "31322" uid: ad67f512-3767-4b18-a47c-8897c919fc5e spec: sourcePod: network-check-source-dbd9cf844-r2mfx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T03:13:09Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.03955ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:20:09Z" - latency: 930.952µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:19:09Z" - latency: 1.172477ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:18:09Z" - latency: 1.253136ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:17:09Z" - latency: 1.243042ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:16:09Z" - latency: 1.189756ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:15:09Z" - latency: 1.148943ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:14:09Z" - latency: 1.03258ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:13:09Z" - latency: 1.141843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:12:09Z" - latency: 1.179473ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:11:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T03:06:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-172-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-172.ec2.internal uid: 98ba8341-7396-44b4-9f26-dc605ca65fa7 resourceVersion: "30051" uid: 39a35cd1-9a6d-4ffc-aac3-d2f944c93e55 spec: sourcePod: network-check-source-dbd9cf844-r2mfx targetEndpoint: add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T03:12:09Z" message: 'load-balancer-api-external: tcp connection to add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.039766ms message: 'load-balancer-api-external: tcp connection to add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:18:09Z" - latency: 6.433099ms message: 'load-balancer-api-external: resolved host name add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T03:18:09Z" - latency: 4.963702ms message: 'load-balancer-api-external: tcp connection to add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:17:09Z" - latency: 6.803064ms message: 'load-balancer-api-external: resolved host name add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T03:17:09Z" - latency: 4.913794ms message: 'load-balancer-api-external: tcp connection to add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:16:09Z" - latency: 7.301024ms message: 'load-balancer-api-external: resolved host name add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T03:16:09Z" - latency: 4.484711ms message: 'load-balancer-api-external: tcp connection to add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:15:09Z" - latency: 7.891434ms message: 'load-balancer-api-external: resolved host name add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T03:15:09Z" - latency: 4.849299ms message: 'load-balancer-api-external: tcp connection to add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:14:09Z" - latency: 6.893843ms message: 'load-balancer-api-external: resolved host name add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T03:14:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T03:06:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-172-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-172.ec2.internal uid: 98ba8341-7396-44b4-9f26-dc605ca65fa7 resourceVersion: "30052" uid: a84dd0ee-07e3-4b9a-a083-42e88fefe78b spec: sourcePod: network-check-source-dbd9cf844-r2mfx targetEndpoint: add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T03:12:09Z" message: 'load-balancer-api-internal: tcp connection to add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.355673ms message: 'load-balancer-api-internal: tcp connection to add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:18:09Z" - latency: 6.51079ms message: 'load-balancer-api-internal: resolved host name add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T03:18:09Z" - latency: 4.992788ms message: 'load-balancer-api-internal: tcp connection to add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:17:09Z" - latency: 6.72947ms message: 'load-balancer-api-internal: resolved host name add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T03:17:09Z" - latency: 4.897097ms message: 'load-balancer-api-internal: tcp connection to add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:16:09Z" - latency: 7.368215ms message: 'load-balancer-api-internal: resolved host name add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T03:16:09Z" - latency: 4.449155ms message: 'load-balancer-api-internal: tcp connection to add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:15:09Z" - latency: 8.046935ms message: 'load-balancer-api-internal: resolved host name add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T03:15:09Z" - latency: 5.223126ms message: 'load-balancer-api-internal: tcp connection to add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:14:09Z" - latency: 6.947962ms message: 'load-balancer-api-internal: resolved host name add240b1245894d51a2ad8fbf0a79212-56a847a538f184b6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T03:14:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T03:06:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-172-to-network-check-target-ip-10-0-130-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-172.ec2.internal uid: 98ba8341-7396-44b4-9f26-dc605ca65fa7 resourceVersion: "31320" uid: 9b422edc-ebd2-49aa-9200-8b55f7ee1ba8 spec: sourcePod: network-check-source-dbd9cf844-r2mfx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T03:13:09Z" message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.203087ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:20:09Z" - latency: 2.212582ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:19:09Z" - latency: 1.756806ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:18:09Z" - latency: 2.029314ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:17:09Z" - latency: 1.877575ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:16:09Z" - latency: 1.895029ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:15:09Z" - latency: 2.249774ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:14:09Z" - latency: 2.297185ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:13:09Z" - latency: 1.770514ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:12:09Z" - latency: 2.253328ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:11:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T03:06:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-172-to-network-check-target-ip-10-0-130-255 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-172.ec2.internal uid: 98ba8341-7396-44b4-9f26-dc605ca65fa7 resourceVersion: "31321" uid: efc18ee5-4c9a-4db7-9e7b-8b0a29c47c13 spec: sourcePod: network-check-source-dbd9cf844-r2mfx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T03:13:09Z" message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.458137ms message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:20:09Z" - latency: 2.373039ms message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:19:09Z" - latency: 1.958303ms message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:18:09Z" - latency: 2.294322ms message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:17:09Z" - latency: 2.19116ms message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:16:09Z" - latency: 2.341565ms message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:15:09Z" - latency: 2.191623ms message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:14:09Z" - latency: 2.295715ms message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:13:09Z" - latency: 2.009819ms message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:12:09Z" - latency: 2.280742ms message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:11:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T03:06:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-172-to-network-check-target-ip-10-0-136-172 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-172.ec2.internal uid: 98ba8341-7396-44b4-9f26-dc605ca65fa7 resourceVersion: "31319" uid: 611834cc-c7b7-4410-a273-03de8e895e55 spec: sourcePod: network-check-source-dbd9cf844-r2mfx targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T03:13:09Z" message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.116666ms message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:20:09Z" - latency: 1.082538ms message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:19:09Z" - latency: 779.875µs message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:18:09Z" - latency: 960.918µs message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:17:09Z" - latency: 820.814µs message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:16:09Z" - latency: 893.611µs message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:15:09Z" - latency: 800.656µs message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:14:09Z" - latency: 1.319495ms message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:13:09Z" - latency: 859.675µs message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:12:09Z" - latency: 1.395408ms message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:11:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T03:06:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-172-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-172.ec2.internal uid: 98ba8341-7396-44b4-9f26-dc605ca65fa7 resourceVersion: "30050" uid: f80c5374-4425-4d06-9439-dc82822938de spec: sourcePod: network-check-source-dbd9cf844-r2mfx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T03:12:09Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 850.598µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:18:09Z" - latency: 2.084591ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T03:18:09Z" - latency: 869.182µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:17:09Z" - latency: 2.017811ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T03:17:09Z" - latency: 818.853µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:16:09Z" - latency: 1.888203ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T03:16:09Z" - latency: 1.175313ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:15:09Z" - latency: 1.670124ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T03:15:09Z" - latency: 803.495µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T03:14:09Z" - latency: 1.878651ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T03:14:09Z" kind: List metadata: resourceVersion: ""