apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:37:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-55-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-55.ec2.internal uid: baa5b93f-1149-4cd6-83ab-19ced3288230 resourceVersion: "18504" uid: 719c6e51-83a0-4c3a-b48b-4aa70b010ff1 spec: sourcePod: network-check-source-989f8b8dc-r8rht targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T16:44:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.554763ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:51:59Z" - latency: 1.159413ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:50:59Z" - latency: 893.799µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:49:59Z" - latency: 935.723µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:48:59Z" - latency: 964.136µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:47:59Z" - latency: 1.112014ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:46:59Z" - latency: 1.02046ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:45:59Z" - latency: 800.401µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:44:59Z" - latency: 798.109µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:43:59Z" - latency: 902.532µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:42:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:37:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-55-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-55.ec2.internal uid: baa5b93f-1149-4cd6-83ab-19ced3288230 resourceVersion: "20595" uid: a551ae06-7da4-479d-964a-75aedba965c5 spec: sourcePod: network-check-source-989f8b8dc-r8rht targetEndpoint: af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T16:43:59Z" message: 'load-balancer-api-external: tcp connection to af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.588543ms message: 'load-balancer-api-external: tcp connection to af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:55:59Z" - latency: 10.243848ms message: 'load-balancer-api-external: resolved host name af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:55:59Z" - latency: 4.743874ms message: 'load-balancer-api-external: tcp connection to af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:54:59Z" - latency: 8.624255ms message: 'load-balancer-api-external: resolved host name af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:54:59Z" - latency: 8.185086ms message: 'load-balancer-api-external: tcp connection to af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:53:59Z" - latency: 8.644676ms message: 'load-balancer-api-external: resolved host name af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:53:59Z" - latency: 4.667702ms message: 'load-balancer-api-external: tcp connection to af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:52:59Z" - latency: 9.406227ms message: 'load-balancer-api-external: resolved host name af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:52:59Z" - latency: 6.067348ms message: 'load-balancer-api-external: tcp connection to af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:51:59Z" - latency: 9.007579ms message: 'load-balancer-api-external: resolved host name af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:51:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:37:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-55-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-55.ec2.internal uid: baa5b93f-1149-4cd6-83ab-19ced3288230 resourceVersion: "20593" uid: 837be1de-30e6-428b-be12-e9214bcc851e spec: sourcePod: network-check-source-989f8b8dc-r8rht targetEndpoint: af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T16:43:59Z" message: 'load-balancer-api-internal: tcp connection to af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.52508ms message: 'load-balancer-api-internal: tcp connection to af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:55:59Z" - latency: 10.193701ms message: 'load-balancer-api-internal: resolved host name af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:55:59Z" - latency: 4.870829ms message: 'load-balancer-api-internal: tcp connection to af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:54:59Z" - latency: 8.593129ms message: 'load-balancer-api-internal: resolved host name af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:54:59Z" - latency: 5.396211ms message: 'load-balancer-api-internal: tcp connection to af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:53:59Z" - latency: 8.575827ms message: 'load-balancer-api-internal: resolved host name af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:53:59Z" - latency: 4.494643ms message: 'load-balancer-api-internal: tcp connection to af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:52:59Z" - latency: 9.382339ms message: 'load-balancer-api-internal: resolved host name af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:52:59Z" - latency: 5.231282ms message: 'load-balancer-api-internal: tcp connection to af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:51:59Z" - latency: 9.004083ms message: 'load-balancer-api-internal: resolved host name af7f2b84ef9484ea6813e4e8b7f6462c-6b4ffba41140c197.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:51:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:37:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-55-to-network-check-target-ip-10-0-138-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-55.ec2.internal uid: baa5b93f-1149-4cd6-83ab-19ced3288230 resourceVersion: "18502" uid: 862f8eb7-cc6c-4d5e-99f2-aa687947aaed spec: sourcePod: network-check-source-989f8b8dc-r8rht targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:44:59Z" message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.517876ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:51:59Z" - latency: 2.589317ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:50:59Z" - latency: 2.094588ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:49:59Z" - latency: 2.115932ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:48:59Z" - latency: 2.31289ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:47:59Z" - latency: 1.965651ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:46:59Z" - latency: 2.549664ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:45:59Z" - latency: 2.291751ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:44:59Z" - latency: 2.001506ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:43:59Z" - latency: 1.75253ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:42:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:37:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-55-to-network-check-target-ip-10-0-138-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-55.ec2.internal uid: baa5b93f-1149-4cd6-83ab-19ced3288230 resourceVersion: "18501" uid: 8ec47472-9af9-4c44-aff4-7d8cb7a81832 spec: sourcePod: network-check-source-989f8b8dc-r8rht targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:44:59Z" message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 793.85µs message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:51:59Z" - latency: 1.347044ms message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:50:59Z" - latency: 1.33554ms message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:49:59Z" - latency: 878.156µs message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:48:59Z" - latency: 1.272217ms message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:47:59Z" - latency: 856.595µs message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:46:59Z" - latency: 1.303321ms message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:45:59Z" - latency: 828.31µs message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:44:59Z" - latency: 767.116µs message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:43:59Z" - latency: 922.916µs message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:42:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:37:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-55-to-network-check-target-ip-10-0-141-25 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-55.ec2.internal uid: baa5b93f-1149-4cd6-83ab-19ced3288230 resourceVersion: "18503" uid: 6459f4eb-142f-4fd3-ba5d-b18115e22655 spec: sourcePod: network-check-source-989f8b8dc-r8rht targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:44:59Z" message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.313093ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:51:59Z" - latency: 2.151945ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:50:59Z" - latency: 2.537768ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:49:59Z" - latency: 2.664084ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:48:59Z" - latency: 2.423195ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:47:59Z" - latency: 2.514624ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:46:59Z" - latency: 2.189367ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:45:59Z" - latency: 2.367095ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:44:59Z" - latency: 2.33488ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:43:59Z" - latency: 2.392551ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:42:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:37:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-55-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-55.ec2.internal uid: baa5b93f-1149-4cd6-83ab-19ced3288230 resourceVersion: "20591" uid: fc4b4a27-fc7a-40dd-8503-187edcb28d0b spec: sourcePod: network-check-source-989f8b8dc-r8rht targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T16:43:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.084236ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:55:59Z" - latency: 1.954955ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:55:59Z" - latency: 985.88µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:54:59Z" - latency: 1.952763ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:54:59Z" - latency: 1.125819ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:53:59Z" - latency: 1.775769ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:53:59Z" - latency: 954.3µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:52:59Z" - latency: 1.871639ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:52:59Z" - latency: 931.539µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:51:59Z" - latency: 1.789045ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:51:59Z" kind: List metadata: resourceVersion: ""