apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T15:07:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.ec2.internal uid: e30ece14-e04c-44ce-8682-51ea3f43837b resourceVersion: "83451" uid: cbb82918-766c-47cf-af7e-9f10e0a14608 spec: sourcePod: network-check-source-7bc5b6bf85-djs2t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T15:14:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.647681ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:24:03Z" - latency: 979.234µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:23:03Z" - latency: 1.165675ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:22:03Z" - latency: 791.705µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:21:03Z" - latency: 1.42653ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:20:03Z" - latency: 843.246µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:19:03Z" - latency: 825.52µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:18:03Z" - latency: 862.32µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:17:03Z" - latency: 1.270685ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:16:03Z" - latency: 1.319623ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:15:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T15:07:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.ec2.internal uid: e30ece14-e04c-44ce-8682-51ea3f43837b resourceVersion: "84284" uid: d64daa68-1752-4f5e-8b49-8fa73be8f5e4 spec: sourcePod: network-check-source-7bc5b6bf85-djs2t targetEndpoint: aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T15:13:03Z" message: 'load-balancer-api-external: tcp connection to aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.287341ms message: 'load-balancer-api-external: tcp connection to aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:25:03Z" - latency: 6.961443ms message: 'load-balancer-api-external: resolved host name aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T16:25:03Z" - latency: 3.649876ms message: 'load-balancer-api-external: tcp connection to aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:24:03Z" - latency: 7.634044ms message: 'load-balancer-api-external: resolved host name aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T16:24:03Z" - latency: 7.09686ms message: 'load-balancer-api-external: tcp connection to aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:23:03Z" - latency: 8.81886ms message: 'load-balancer-api-external: resolved host name aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T16:23:03Z" - latency: 5.143245ms message: 'load-balancer-api-external: tcp connection to aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:22:03Z" - latency: 9.815521ms message: 'load-balancer-api-external: resolved host name aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T16:22:03Z" - latency: 4.210078ms message: 'load-balancer-api-external: tcp connection to aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:21:03Z" - latency: 6.570829ms message: 'load-balancer-api-external: resolved host name aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T16:21:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T15:07:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.ec2.internal uid: e30ece14-e04c-44ce-8682-51ea3f43837b resourceVersion: "84285" uid: e8ea2107-4acc-4f8a-bc37-4b7cf872769d spec: sourcePod: network-check-source-7bc5b6bf85-djs2t targetEndpoint: aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T15:13:03Z" message: 'load-balancer-api-internal: tcp connection to aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.399573ms message: 'load-balancer-api-internal: tcp connection to aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:25:03Z" - latency: 6.840716ms message: 'load-balancer-api-internal: resolved host name aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T16:25:03Z" - latency: 5.741318ms message: 'load-balancer-api-internal: tcp connection to aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:24:03Z" - latency: 7.578312ms message: 'load-balancer-api-internal: resolved host name aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T16:24:03Z" - latency: 7.036535ms message: 'load-balancer-api-internal: tcp connection to aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:23:03Z" - latency: 8.703917ms message: 'load-balancer-api-internal: resolved host name aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T16:23:03Z" - latency: 5.173918ms message: 'load-balancer-api-internal: tcp connection to aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:22:03Z" - latency: 9.742754ms message: 'load-balancer-api-internal: resolved host name aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T16:22:03Z" - latency: 4.195758ms message: 'load-balancer-api-internal: tcp connection to aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:21:03Z" - latency: 6.480641ms message: 'load-balancer-api-internal: resolved host name aebaec80bdec04d0caf4c04b467143e7-90f226faf6d88d00.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T16:21:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T15:07:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-network-check-target-ip-10-0-129-25 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.ec2.internal uid: e30ece14-e04c-44ce-8682-51ea3f43837b resourceVersion: "83450" uid: 3583d41e-96af-47c5-b39f-9e0b2b70152a spec: sourcePod: network-check-source-7bc5b6bf85-djs2t targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T15:14:03Z" message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.242919ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:24:03Z" - latency: 2.296537ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:23:03Z" - latency: 2.29373ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:22:03Z" - latency: 2.295211ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:21:03Z" - latency: 2.610239ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:20:03Z" - latency: 1.957411ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:19:03Z" - latency: 2.279813ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:18:03Z" - latency: 2.049726ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:17:03Z" - latency: 2.225854ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:16:03Z" - latency: 2.249744ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:15:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T15:07:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-network-check-target-ip-10-0-130-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.ec2.internal uid: e30ece14-e04c-44ce-8682-51ea3f43837b resourceVersion: "83449" uid: 911f9d82-536e-4444-9152-06ef06d5d7d0 spec: sourcePod: network-check-source-7bc5b6bf85-djs2t targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T15:14:03Z" message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.782054ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:24:03Z" - latency: 2.009467ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:23:03Z" - latency: 2.280554ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:22:03Z" - latency: 1.790741ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:21:03Z" - latency: 2.030845ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:20:03Z" - latency: 1.580978ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:19:03Z" - latency: 1.691405ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:18:03Z" - latency: 1.851555ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:17:03Z" - latency: 1.962188ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:16:03Z" - latency: 1.707652ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:15:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T15:07:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-network-check-target-ip-10-0-135-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.ec2.internal uid: e30ece14-e04c-44ce-8682-51ea3f43837b resourceVersion: "83448" uid: 83ff441b-b67d-46cd-a0d3-235c22a2f0eb spec: sourcePod: network-check-source-7bc5b6bf85-djs2t targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T15:14:03Z" message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 898.204µs message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:24:03Z" - latency: 1.06082ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:23:03Z" - latency: 944.491µs message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:22:03Z" - latency: 1.196375ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:21:03Z" - latency: 1.445819ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:20:03Z" - latency: 811.676µs message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:19:03Z" - latency: 867.765µs message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:18:03Z" - latency: 1.370885ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:17:03Z" - latency: 948.909µs message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:16:03Z" - latency: 932.485µs message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:15:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T15:07:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.ec2.internal uid: e30ece14-e04c-44ce-8682-51ea3f43837b resourceVersion: "84283" uid: 9b767243-caf1-4389-bb9d-ed53be3cba0c spec: sourcePod: network-check-source-7bc5b6bf85-djs2t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T15:13:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 959.279µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:25:03Z" - latency: 1.86415ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T16:25:03Z" - latency: 981.379µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:24:03Z" - latency: 1.872976ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T16:24:03Z" - latency: 928.403µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:23:03Z" - latency: 2.231946ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T16:23:03Z" - latency: 1.194518ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:22:03Z" - latency: 1.730261ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T16:22:03Z" - latency: 1.160233ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T16:21:03Z" - latency: 1.734947ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T16:21:03Z" kind: List metadata: resourceVersion: ""