apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T12:48:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-160-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-160.ec2.internal uid: 63f269fe-85ad-485a-a7bb-f65a81939fd0 resourceVersion: "61190" uid: ed7a936d-0e7e-4616-85c3-53fa474f6c7d spec: sourcePod: network-check-source-869dcfcdcd-zr865 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T12:55:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 962.879µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:30:23Z" - latency: 994.758µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:29:23Z" - latency: 1.139439ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:28:23Z" - latency: 890.888µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:27:23Z" - latency: 1.225723ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:26:23Z" - latency: 1.497115ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:25:23Z" - latency: 1.055758ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:24:23Z" - latency: 1.008818ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:23:23Z" - latency: 901.74µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:22:23Z" - latency: 1.854674ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:21:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T12:48:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-160-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-160.ec2.internal uid: 63f269fe-85ad-485a-a7bb-f65a81939fd0 resourceVersion: "61192" uid: b788a20b-3e27-40bc-9010-d86eb8bcf299 spec: sourcePod: network-check-source-869dcfcdcd-zr865 targetEndpoint: a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T12:54:23Z" message: 'load-balancer-api-external: tcp connection to a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.106857ms message: 'load-balancer-api-external: tcp connection to a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:30:23Z" - latency: 6.820496ms message: 'load-balancer-api-external: resolved host name a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T13:30:23Z" - latency: 4.044605ms message: 'load-balancer-api-external: tcp connection to a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:29:23Z" - latency: 6.861875ms message: 'load-balancer-api-external: resolved host name a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T13:29:23Z" - latency: 4.311143ms message: 'load-balancer-api-external: tcp connection to a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:28:23Z" - latency: 6.72348ms message: 'load-balancer-api-external: resolved host name a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T13:28:23Z" - latency: 3.1638ms message: 'load-balancer-api-external: tcp connection to a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:27:23Z" - latency: 6.024449ms message: 'load-balancer-api-external: resolved host name a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T13:27:23Z" - latency: 5.486027ms message: 'load-balancer-api-external: tcp connection to a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:26:23Z" - latency: 6.576236ms message: 'load-balancer-api-external: resolved host name a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T13:26:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T12:48:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-160-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-160.ec2.internal uid: 63f269fe-85ad-485a-a7bb-f65a81939fd0 resourceVersion: "61191" uid: 885bf8df-77cc-46b9-a64a-7d2c7d4acd49 spec: sourcePod: network-check-source-869dcfcdcd-zr865 targetEndpoint: a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T12:54:23Z" message: 'load-balancer-api-internal: tcp connection to a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.082696ms message: 'load-balancer-api-internal: tcp connection to a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:30:23Z" - latency: 6.868555ms message: 'load-balancer-api-internal: resolved host name a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T13:30:23Z" - latency: 4.09574ms message: 'load-balancer-api-internal: tcp connection to a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:29:23Z" - latency: 6.978921ms message: 'load-balancer-api-internal: resolved host name a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T13:29:23Z" - latency: 5.353671ms message: 'load-balancer-api-internal: tcp connection to a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:28:23Z" - latency: 6.75347ms message: 'load-balancer-api-internal: resolved host name a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T13:28:23Z" - latency: 3.224393ms message: 'load-balancer-api-internal: tcp connection to a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:27:23Z" - latency: 6.064632ms message: 'load-balancer-api-internal: resolved host name a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T13:27:23Z" - latency: 5.451597ms message: 'load-balancer-api-internal: tcp connection to a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:26:23Z" - latency: 6.635427ms message: 'load-balancer-api-internal: resolved host name a445d516cb8b3431899d52d6c49d715d-64481b4a5a95f7a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T13:26:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T12:48:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-160-to-network-check-target-ip-10-0-131-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-160.ec2.internal uid: 63f269fe-85ad-485a-a7bb-f65a81939fd0 resourceVersion: "61188" uid: a6765de6-8a9e-4738-b57f-1ce5e46f2d87 spec: sourcePod: network-check-source-869dcfcdcd-zr865 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T12:55:23Z" message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.327448ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:30:23Z" - latency: 2.418046ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:29:23Z" - latency: 2.483207ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:28:23Z" - latency: 2.572182ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:27:23Z" - latency: 2.527504ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:26:23Z" - latency: 2.313803ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:25:23Z" - latency: 2.485663ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:24:23Z" - latency: 2.159564ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:23:23Z" - latency: 2.282977ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:22:23Z" - latency: 2.363898ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:21:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T12:48:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-160-to-network-check-target-ip-10-0-138-198 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-160.ec2.internal uid: 63f269fe-85ad-485a-a7bb-f65a81939fd0 resourceVersion: "61187" uid: ca46d847-be76-4294-83fb-b3eb31ffb8b3 spec: sourcePod: network-check-source-869dcfcdcd-zr865 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T12:55:23Z" message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.174424ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:30:23Z" - latency: 2.374964ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:29:23Z" - latency: 2.248938ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:28:23Z" - latency: 2.441036ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:27:23Z" - latency: 2.375535ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:26:23Z" - latency: 1.966883ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:25:23Z" - latency: 2.166795ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:24:23Z" - latency: 2.122835ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:23:23Z" - latency: 2.5505ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:22:23Z" - latency: 2.400183ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:21:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T12:48:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-160-to-network-check-target-ip-10-0-139-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-160.ec2.internal uid: 63f269fe-85ad-485a-a7bb-f65a81939fd0 resourceVersion: "61186" uid: 02f86b54-ca69-40f8-9f24-858aba124352 spec: sourcePod: network-check-source-869dcfcdcd-zr865 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T12:55:23Z" message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 921.688µs message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:30:23Z" - latency: 1.000699ms message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:29:23Z" - latency: 941.764µs message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:28:23Z" - latency: 1.04109ms message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:27:23Z" - latency: 1.515682ms message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:26:23Z" - latency: 1.380415ms message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:25:23Z" - latency: 879.394µs message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:24:23Z" - latency: 839.365µs message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:23:23Z" - latency: 858.653µs message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:22:23Z" - latency: 755.708µs message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:21:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T12:48:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-160-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-160.ec2.internal uid: 63f269fe-85ad-485a-a7bb-f65a81939fd0 resourceVersion: "61189" uid: c9e54fbc-f43d-4d12-af20-6628f6400270 spec: sourcePod: network-check-source-869dcfcdcd-zr865 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T12:54:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.174044ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:30:23Z" - latency: 1.792543ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T13:30:23Z" - latency: 1.024253ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:29:23Z" - latency: 1.847126ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T13:29:23Z" - latency: 821.349µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:28:23Z" - latency: 1.795957ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T13:28:23Z" - latency: 894.631µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:27:23Z" - latency: 1.754013ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T13:27:23Z" - latency: 911.955µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T13:26:23Z" - latency: 1.768799ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T13:26:23Z" kind: List metadata: resourceVersion: ""