apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:14:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: 95dc67e4-50ef-4129-9e91-fed3c174d1c7 resourceVersion: "82343" uid: 9f56674d-0fd4-4612-81da-2f1e331e76e7 spec: sourcePod: network-check-source-7d88cb55d8-mjcr9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T15:21:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.174839ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:17:37Z" - latency: 1.273463ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:16:37Z" - latency: 1.418606ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:15:37Z" - latency: 1.009368ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:14:37Z" - latency: 887.978µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:13:37Z" - latency: 1.443429ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:12:37Z" - latency: 1.055342ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:11:37Z" - latency: 991.536µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:10:37Z" - latency: 972.788µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:09:37Z" - latency: 1.502994ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:08:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:14:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: 95dc67e4-50ef-4129-9e91-fed3c174d1c7 resourceVersion: "79171" uid: d461b7d0-03ad-4c55-8142-7623450407d2 spec: sourcePod: network-check-source-7d88cb55d8-mjcr9 targetEndpoint: aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T15:20:37Z" message: 'load-balancer-api-external: tcp connection to aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.753891ms message: 'load-balancer-api-external: tcp connection to aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:14:37Z" - latency: 6.923661ms message: 'load-balancer-api-external: resolved host name aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:14:37Z" - latency: 5.323765ms message: 'load-balancer-api-external: tcp connection to aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:13:37Z" - latency: 7.583339ms message: 'load-balancer-api-external: resolved host name aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:13:37Z" - latency: 4.783029ms message: 'load-balancer-api-external: tcp connection to aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:12:37Z" - latency: 7.431225ms message: 'load-balancer-api-external: resolved host name aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:12:37Z" - latency: 5.498635ms message: 'load-balancer-api-external: tcp connection to aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:11:37Z" - latency: 7.31774ms message: 'load-balancer-api-external: resolved host name aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:11:37Z" - latency: 4.159651ms message: 'load-balancer-api-external: tcp connection to aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:10:37Z" - latency: 7.880172ms message: 'load-balancer-api-external: resolved host name aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:10:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:14:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: 95dc67e4-50ef-4129-9e91-fed3c174d1c7 resourceVersion: "79172" uid: 25d83e3a-dd97-4676-8331-15478f364826 spec: sourcePod: network-check-source-7d88cb55d8-mjcr9 targetEndpoint: aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T15:20:37Z" message: 'load-balancer-api-internal: tcp connection to aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.996848ms message: 'load-balancer-api-internal: tcp connection to aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:14:37Z" - latency: 7.0507ms message: 'load-balancer-api-internal: resolved host name aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:14:37Z" - latency: 5.258766ms message: 'load-balancer-api-internal: tcp connection to aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:13:37Z" - latency: 7.709899ms message: 'load-balancer-api-internal: resolved host name aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:13:37Z" - latency: 4.354616ms message: 'load-balancer-api-internal: tcp connection to aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:12:37Z" - latency: 7.607935ms message: 'load-balancer-api-internal: resolved host name aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:12:37Z" - latency: 5.507408ms message: 'load-balancer-api-internal: tcp connection to aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:11:37Z" - latency: 7.099007ms message: 'load-balancer-api-internal: resolved host name aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:11:37Z" - latency: 4.656416ms message: 'load-balancer-api-internal: tcp connection to aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:10:37Z" - latency: 8.065919ms message: 'load-balancer-api-internal: resolved host name aed12b225ffab4dde8a4b0483c4c04c4-e410d5ed484cf098.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:10:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:14:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-network-check-target-ip-10-0-130-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: 95dc67e4-50ef-4129-9e91-fed3c174d1c7 resourceVersion: "82340" uid: 74f30d62-d6d0-41f2-b193-11891fe1974c spec: sourcePod: network-check-source-7d88cb55d8-mjcr9 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T15:21:37Z" message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.325485ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:17:37Z" - latency: 1.143328ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:16:37Z" - latency: 828.852µs message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:15:37Z" - latency: 883.734µs message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:14:37Z" - latency: 1.00706ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:13:37Z" - latency: 1.356411ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:12:37Z" - latency: 1.599751ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:11:37Z" - latency: 1.406374ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:10:37Z" - latency: 969.281µs message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:09:37Z" - latency: 1.274279ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:08:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:14:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-network-check-target-ip-10-0-135-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: 95dc67e4-50ef-4129-9e91-fed3c174d1c7 resourceVersion: "82341" uid: cdd57db0-462f-4e96-a15c-de888a3cb97d spec: sourcePod: network-check-source-7d88cb55d8-mjcr9 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T15:21:37Z" message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.60786ms message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:17:37Z" - latency: 2.031977ms message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:16:37Z" - latency: 1.960158ms message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:15:37Z" - latency: 1.987406ms message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:14:37Z" - latency: 2.121213ms message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:13:37Z" - latency: 2.349241ms message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:12:37Z" - latency: 2.181137ms message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:11:37Z" - latency: 2.205563ms message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:10:37Z" - latency: 2.70584ms message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:09:37Z" - latency: 3.276264ms message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:08:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:14:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-network-check-target-ip-10-0-136-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: 95dc67e4-50ef-4129-9e91-fed3c174d1c7 resourceVersion: "82342" uid: 5ec71f6e-5c3f-49aa-b35a-e73d9ea0da04 spec: sourcePod: network-check-source-7d88cb55d8-mjcr9 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T15:21:37Z" message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.438494ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:17:37Z" - latency: 2.860636ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:16:37Z" - latency: 2.397738ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:15:37Z" - latency: 2.148579ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:14:37Z" - latency: 2.548151ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:13:37Z" - latency: 2.469791ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:12:37Z" - latency: 2.421201ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:11:37Z" - latency: 2.656699ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:10:37Z" - latency: 2.092723ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:09:37Z" - latency: 3.256366ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:08:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:14:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: 95dc67e4-50ef-4129-9e91-fed3c174d1c7 resourceVersion: "79170" uid: 9d154f3a-2597-4ef5-b02b-a2c2430954b5 spec: sourcePod: network-check-source-7d88cb55d8-mjcr9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T15:20:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 991.951µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:14:37Z" - latency: 2.086115ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T16:14:37Z" - latency: 1.059864ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:13:37Z" - latency: 2.705636ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T16:13:37Z" - latency: 928.143µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:12:37Z" - latency: 2.690201ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T16:12:37Z" - latency: 1.051171ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:11:37Z" - latency: 1.73132ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T16:11:37Z" - latency: 1.036625ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:10:37Z" - latency: 2.910799ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T16:10:37Z" kind: List metadata: resourceVersion: ""