apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T00:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-102-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-102.ec2.internal uid: b0b37f34-536c-4ed8-ad5a-e7107dca9e8f resourceVersion: "96899" uid: 0fa87d66-e08a-4e55-ac1b-b77469f9be79 spec: sourcePod: network-check-source-65bdbbff45-2km27 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T00:15:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.413762ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:04:57Z" - latency: 929.442µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:03:57Z" - latency: 1.326013ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:02:57Z" - latency: 862.218µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:01:57Z" - latency: 756.211µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:00:57Z" - latency: 984.72µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:59:57Z" - latency: 996.293µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:58:57Z" - latency: 781.111µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:57:57Z" - latency: 827.477µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:56:57Z" - latency: 801.577µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:55:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T00:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-102-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-102.ec2.internal uid: b0b37f34-536c-4ed8-ad5a-e7107dca9e8f resourceVersion: "92400" uid: 429b8da0-09ad-41f0-86e2-e23dfd92ecce spec: sourcePod: network-check-source-65bdbbff45-2km27 targetEndpoint: ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T00:14:57Z" message: 'load-balancer-api-external: tcp connection to ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.659805ms message: 'load-balancer-api-external: tcp connection to ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:02:57Z" - latency: 8.829129ms message: 'load-balancer-api-external: resolved host name ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T01:02:57Z" - latency: 4.940103ms message: 'load-balancer-api-external: tcp connection to ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:01:57Z" - latency: 8.227046ms message: 'load-balancer-api-external: resolved host name ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T01:01:57Z" - latency: 4.429498ms message: 'load-balancer-api-external: tcp connection to ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:00:57Z" - latency: 6.902579ms message: 'load-balancer-api-external: resolved host name ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T01:00:57Z" - latency: 3.630661ms message: 'load-balancer-api-external: tcp connection to ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:59:57Z" - latency: 7.956435ms message: 'load-balancer-api-external: resolved host name ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T00:59:57Z" - latency: 5.307712ms message: 'load-balancer-api-external: tcp connection to ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:58:57Z" - latency: 12.22958ms message: 'load-balancer-api-external: resolved host name ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T00:58:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T00:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-102-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-102.ec2.internal uid: b0b37f34-536c-4ed8-ad5a-e7107dca9e8f resourceVersion: "92401" uid: 5f4a71c1-cbd3-4581-8beb-d1c7b3d77cd9 spec: sourcePod: network-check-source-65bdbbff45-2km27 targetEndpoint: ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T00:14:57Z" message: 'load-balancer-api-internal: tcp connection to ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.136512ms message: 'load-balancer-api-internal: tcp connection to ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:02:57Z" - latency: 8.778183ms message: 'load-balancer-api-internal: resolved host name ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T01:02:57Z" - latency: 4.893872ms message: 'load-balancer-api-internal: tcp connection to ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:01:57Z" - latency: 8.252962ms message: 'load-balancer-api-internal: resolved host name ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T01:01:57Z" - latency: 4.460793ms message: 'load-balancer-api-internal: tcp connection to ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:00:57Z" - latency: 6.849427ms message: 'load-balancer-api-internal: resolved host name ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T01:00:57Z" - latency: 4.320966ms message: 'load-balancer-api-internal: tcp connection to ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:59:57Z" - latency: 7.907092ms message: 'load-balancer-api-internal: resolved host name ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T00:59:57Z" - latency: 5.291463ms message: 'load-balancer-api-internal: tcp connection to ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:58:57Z" - latency: 12.178727ms message: 'load-balancer-api-internal: resolved host name ac5ed5a6561f743a4a44aec245915b79-2a56a4a0be243a74.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T00:58:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T00:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-102-to-network-check-target-ip-10-0-132-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-102.ec2.internal uid: b0b37f34-536c-4ed8-ad5a-e7107dca9e8f resourceVersion: "96897" uid: 4e642820-d8db-4685-9ead-59eb9d8e7dd0 spec: sourcePod: network-check-source-65bdbbff45-2km27 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T00:15:57Z" message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.314682ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:04:57Z" - latency: 2.135981ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:03:57Z" - latency: 2.053707ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:02:57Z" - latency: 2.304329ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:01:57Z" - latency: 2.106717ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:00:57Z" - latency: 2.125539ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:59:57Z" - latency: 2.12512ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:58:57Z" - latency: 2.05109ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:57:57Z" - latency: 2.442796ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:56:57Z" - latency: 2.273877ms message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:55:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T00:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-102-to-network-check-target-ip-10-0-134-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-102.ec2.internal uid: b0b37f34-536c-4ed8-ad5a-e7107dca9e8f resourceVersion: "96898" uid: 0a637c06-8d8b-4cd6-8d26-57e9b21c79ca spec: sourcePod: network-check-source-65bdbbff45-2km27 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T00:15:57Z" message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.360374ms message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:04:57Z" - latency: 2.294994ms message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:03:57Z" - latency: 2.415453ms message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:02:57Z" - latency: 2.518238ms message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:01:57Z" - latency: 2.271786ms message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:00:57Z" - latency: 2.00302ms message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:59:57Z" - latency: 2.461102ms message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:58:57Z" - latency: 2.372824ms message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:57:57Z" - latency: 2.448974ms message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:56:57Z" - latency: 2.468209ms message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:55:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T00:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-102-to-network-check-target-ip-10-0-138-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-102.ec2.internal uid: b0b37f34-536c-4ed8-ad5a-e7107dca9e8f resourceVersion: "96896" uid: 7f0a1d05-f7a2-4a3d-8ecf-d5ff6555315a spec: sourcePod: network-check-source-65bdbbff45-2km27 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T00:15:57Z" message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 770.66µs message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:04:57Z" - latency: 1.464812ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:03:57Z" - latency: 1.769273ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:02:57Z" - latency: 1.447938ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:01:57Z" - latency: 1.216788ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:00:57Z" - latency: 866.727µs message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:59:57Z" - latency: 1.069039ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:58:57Z" - latency: 946.591µs message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:57:57Z" - latency: 931.787µs message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:56:57Z" - latency: 1.711932ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:55:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T00:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-102-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-102.ec2.internal uid: b0b37f34-536c-4ed8-ad5a-e7107dca9e8f resourceVersion: "92399" uid: 500bad90-5bd4-4ad2-9359-3851ff12836b spec: sourcePod: network-check-source-65bdbbff45-2km27 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T00:14:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 861.032µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:02:57Z" - latency: 2.124613ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T01:02:57Z" - latency: 783.508µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:01:57Z" - latency: 1.628466ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T01:01:57Z" - latency: 1.220322ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T01:00:57Z" - latency: 1.741051ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T01:00:57Z" - latency: 878.938µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:59:57Z" - latency: 1.685333ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T00:59:57Z" - latency: 930.218µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:58:57Z" - latency: 1.587257ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T00:58:57Z" kind: List metadata: resourceVersion: ""