apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:20:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-93-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-93.ec2.internal uid: fa1ed6b9-8903-407c-9b37-94d5abf93fcc resourceVersion: "70345" uid: 6a146ecd-bd60-4cdf-b150-3e8f242fa003 spec: sourcePod: network-check-source-7d88cb55d8-vvlr8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T19:28:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.174217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:10:01Z" - latency: 1.206786ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:09:01Z" - latency: 1.281456ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:08:01Z" - latency: 1.165946ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:07:01Z" - latency: 878.306µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:06:01Z" - latency: 943.958µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:05:01Z" - latency: 1.116078ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:04:01Z" - latency: 1.16711ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:03:01Z" - latency: 1.211332ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:02:01Z" - latency: 1.01186ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:01:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:20:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-93-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-93.ec2.internal uid: fa1ed6b9-8903-407c-9b37-94d5abf93fcc resourceVersion: "69496" uid: d974cc37-671b-47ba-8d3f-f98752d93a14 spec: sourcePod: network-check-source-7d88cb55d8-vvlr8 targetEndpoint: acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T19:27:01Z" message: 'load-balancer-api-external: tcp connection to acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.153545ms message: 'load-balancer-api-external: tcp connection to acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:09:01Z" - latency: 6.574256ms message: 'load-balancer-api-external: resolved host name acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:09:01Z" - latency: 5.071933ms message: 'load-balancer-api-external: tcp connection to acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:08:01Z" - latency: 7.036823ms message: 'load-balancer-api-external: resolved host name acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:08:01Z" - latency: 4.253585ms message: 'load-balancer-api-external: tcp connection to acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:07:01Z" - latency: 6.39928ms message: 'load-balancer-api-external: resolved host name acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:07:01Z" - latency: 3.860826ms message: 'load-balancer-api-external: tcp connection to acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:06:01Z" - latency: 6.773862ms message: 'load-balancer-api-external: resolved host name acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:06:01Z" - latency: 5.435569ms message: 'load-balancer-api-external: tcp connection to acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:05:01Z" - latency: 6.547317ms message: 'load-balancer-api-external: resolved host name acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:05:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:20:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-93-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-93.ec2.internal uid: fa1ed6b9-8903-407c-9b37-94d5abf93fcc resourceVersion: "69497" uid: 374c269e-9642-4aa3-b54a-03de906595fb spec: sourcePod: network-check-source-7d88cb55d8-vvlr8 targetEndpoint: acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T19:27:01Z" message: 'load-balancer-api-internal: tcp connection to acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.164406ms message: 'load-balancer-api-internal: tcp connection to acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:09:01Z" - latency: 6.56482ms message: 'load-balancer-api-internal: resolved host name acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:09:01Z" - latency: 5.418216ms message: 'load-balancer-api-internal: tcp connection to acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:08:01Z" - latency: 7.069053ms message: 'load-balancer-api-internal: resolved host name acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:08:01Z" - latency: 3.826716ms message: 'load-balancer-api-internal: tcp connection to acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:07:01Z" - latency: 6.450299ms message: 'load-balancer-api-internal: resolved host name acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:07:01Z" - latency: 4.09857ms message: 'load-balancer-api-internal: tcp connection to acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:06:01Z" - latency: 6.736125ms message: 'load-balancer-api-internal: resolved host name acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:06:01Z" - latency: 4.617217ms message: 'load-balancer-api-internal: tcp connection to acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:05:01Z" - latency: 6.627017ms message: 'load-balancer-api-internal: resolved host name acca94548e1a6402592784ba0e48040a-a981d5c9b6979f5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:05:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:20:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-93-to-network-check-target-ip-10-0-128-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-93.ec2.internal uid: fa1ed6b9-8903-407c-9b37-94d5abf93fcc resourceVersion: "70343" uid: f7fa30c4-de57-4ecb-b968-f3b31d0dc748 spec: sourcePod: network-check-source-7d88cb55d8-vvlr8 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T19:28:01Z" message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.002864ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:10:01Z" - latency: 1.909471ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:09:01Z" - latency: 1.943075ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:08:01Z" - latency: 2.153138ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:07:01Z" - latency: 1.848113ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:06:01Z" - latency: 1.982295ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:05:01Z" - latency: 2.087002ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:04:01Z" - latency: 2.194025ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:03:01Z" - latency: 2.175533ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:02:01Z" - latency: 2.163812ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:01:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:20:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-93-to-network-check-target-ip-10-0-131-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-93.ec2.internal uid: fa1ed6b9-8903-407c-9b37-94d5abf93fcc resourceVersion: "70342" uid: 84ee42bd-9768-41c0-903f-701bf0fde4ea spec: sourcePod: network-check-source-7d88cb55d8-vvlr8 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T19:28:01Z" message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 944.327µs message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:10:01Z" - latency: 1.054267ms message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:09:01Z" - latency: 917.286µs message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:08:01Z" - latency: 887.761µs message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:07:01Z" - latency: 834.233µs message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:06:01Z" - latency: 1.03621ms message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:05:01Z" - latency: 1.005378ms message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:04:01Z" - latency: 943.32µs message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:03:01Z" - latency: 1.107939ms message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:02:01Z" - latency: 921.798µs message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:01:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:20:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-93-to-network-check-target-ip-10-0-140-204 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-93.ec2.internal uid: fa1ed6b9-8903-407c-9b37-94d5abf93fcc resourceVersion: "70344" uid: ae073f4b-864d-4208-a920-58101338ffb7 spec: sourcePod: network-check-source-7d88cb55d8-vvlr8 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T19:28:01Z" message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.066328ms message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:10:01Z" - latency: 1.955664ms message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:09:01Z" - latency: 1.939762ms message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:08:01Z" - latency: 2.154165ms message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:07:01Z" - latency: 1.673087ms message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:06:01Z" - latency: 1.84292ms message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:05:01Z" - latency: 2.265248ms message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:04:01Z" - latency: 2.21793ms message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:03:01Z" - latency: 2.349511ms message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:02:01Z" - latency: 2.1632ms message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:01:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:20:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-93-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-93.ec2.internal uid: fa1ed6b9-8903-407c-9b37-94d5abf93fcc resourceVersion: "69495" uid: 6d19810c-91c3-4d37-a51e-687c4ec471cd spec: sourcePod: network-check-source-7d88cb55d8-vvlr8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T19:27:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 993.742µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:09:01Z" - latency: 1.919623ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T20:09:01Z" - latency: 814.521µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:08:01Z" - latency: 1.830587ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T20:08:01Z" - latency: 1.01729ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:07:01Z" - latency: 1.797654ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T20:07:01Z" - latency: 811.677µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:06:01Z" - latency: 1.826417ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T20:06:01Z" - latency: 787.93µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:05:01Z" - latency: 1.616533ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T20:05:01Z" kind: List metadata: resourceVersion: ""