apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:37:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-175-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-175.ec2.internal uid: 49fa9730-adab-4e69-9cc0-7d37508c0d9a resourceVersion: "21767" uid: 871ec2ba-42a9-4bcc-b2c6-fc9b5c7e4567 spec: sourcePod: network-check-source-869dcfcdcd-ws5t8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T17: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.088936ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:58:59Z" - latency: 1.059114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:57:59Z" - latency: 1.101155ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:56:59Z" - latency: 849.785µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:55:59Z" - latency: 922.031µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:54:59Z" - latency: 898.716µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:53:59Z" - latency: 1.00454ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:52:59Z" - latency: 944.922µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:51:59Z" - latency: 954.066µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:50:59Z" - latency: 764.482µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:49:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:37:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-175-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-175.ec2.internal uid: 49fa9730-adab-4e69-9cc0-7d37508c0d9a resourceVersion: "20148" uid: 8a6a718c-83e9-4300-939f-a84425ee8de7 spec: sourcePod: network-check-source-869dcfcdcd-ws5t8 targetEndpoint: a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:43:59Z" message: 'load-balancer-api-external: tcp connection to a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.961046ms message: 'load-balancer-api-external: tcp connection to a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:55:59Z" - latency: 8.362745ms message: 'load-balancer-api-external: resolved host name a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:55:59Z" - latency: 4.152241ms message: 'load-balancer-api-external: tcp connection to a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:54:59Z" - latency: 7.705499ms message: 'load-balancer-api-external: resolved host name a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:54:59Z" - latency: 4.29787ms message: 'load-balancer-api-external: tcp connection to a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:53:59Z" - latency: 7.935889ms message: 'load-balancer-api-external: resolved host name a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:53:59Z" - latency: 4.894234ms message: 'load-balancer-api-external: tcp connection to a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:52:59Z" - latency: 10.105564ms message: 'load-balancer-api-external: resolved host name a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:52:59Z" - latency: 4.137957ms message: 'load-balancer-api-external: tcp connection to a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:51:59Z" - latency: 7.780306ms message: 'load-balancer-api-external: resolved host name a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:51:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:37:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-175-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-175.ec2.internal uid: 49fa9730-adab-4e69-9cc0-7d37508c0d9a resourceVersion: "20149" uid: d2cd3c61-0390-4311-91f9-7b8efc9e0f82 spec: sourcePod: network-check-source-869dcfcdcd-ws5t8 targetEndpoint: a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:43:59Z" message: 'load-balancer-api-internal: tcp connection to a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.131335ms message: 'load-balancer-api-internal: tcp connection to a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:55:59Z" - latency: 8.385093ms message: 'load-balancer-api-internal: resolved host name a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:55:59Z" - latency: 4.169701ms message: 'load-balancer-api-internal: tcp connection to a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:54:59Z" - latency: 7.674137ms message: 'load-balancer-api-internal: resolved host name a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:54:59Z" - latency: 4.648881ms message: 'load-balancer-api-internal: tcp connection to a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:53:59Z" - latency: 7.990931ms message: 'load-balancer-api-internal: resolved host name a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:53:59Z" - latency: 4.861023ms message: 'load-balancer-api-internal: tcp connection to a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:52:59Z" - latency: 10.156709ms message: 'load-balancer-api-internal: resolved host name a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:52:59Z" - latency: 4.124845ms message: 'load-balancer-api-internal: tcp connection to a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:51:59Z" - latency: 7.897487ms message: 'load-balancer-api-internal: resolved host name a7916f319f0a840ab94ab92ebc7afcf5-73cf4c096c61ee42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:51:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:37:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-175-to-network-check-target-ip-10-0-130-5 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-175.ec2.internal uid: 49fa9730-adab-4e69-9cc0-7d37508c0d9a resourceVersion: "21765" uid: f64c97f8-8dc6-4ed8-b5a4-651ad527a90d spec: sourcePod: network-check-source-869dcfcdcd-ws5t8 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:44:59Z" message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.021791ms message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:58:59Z" - latency: 2.287469ms message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:57:59Z" - latency: 2.256626ms message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:56:59Z" - latency: 2.198563ms message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:55:59Z" - latency: 2.159121ms message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:54:59Z" - latency: 2.303062ms message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:53:59Z" - latency: 2.135914ms message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:52:59Z" - latency: 2.152976ms message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:51:59Z" - latency: 2.410832ms message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:50:59Z" - latency: 2.32761ms message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:49:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:37:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-175-to-network-check-target-ip-10-0-132-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-175.ec2.internal uid: 49fa9730-adab-4e69-9cc0-7d37508c0d9a resourceVersion: "21766" uid: e6abe7c3-f826-412c-823f-8e2f42acfe55 spec: sourcePod: network-check-source-869dcfcdcd-ws5t8 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:44:59Z" message: 'network-check-target-ip-10-0-132-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.542518ms message: 'network-check-target-ip-10-0-132-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:58:59Z" - latency: 2.339059ms message: 'network-check-target-ip-10-0-132-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:57:59Z" - latency: 2.314608ms message: 'network-check-target-ip-10-0-132-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:56:59Z" - latency: 2.137855ms message: 'network-check-target-ip-10-0-132-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:55:59Z" - latency: 2.301707ms message: 'network-check-target-ip-10-0-132-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:54:59Z" - latency: 2.582793ms message: 'network-check-target-ip-10-0-132-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:53:59Z" - latency: 2.450176ms message: 'network-check-target-ip-10-0-132-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:52:59Z" - latency: 2.305488ms message: 'network-check-target-ip-10-0-132-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:51:59Z" - latency: 2.109132ms message: 'network-check-target-ip-10-0-132-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:50:59Z" - latency: 2.246261ms message: 'network-check-target-ip-10-0-132-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:49:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:37:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-175-to-network-check-target-ip-10-0-143-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-175.ec2.internal uid: 49fa9730-adab-4e69-9cc0-7d37508c0d9a resourceVersion: "21764" uid: 939bbd8f-94df-4ddb-95eb-07e51bcca45d spec: sourcePod: network-check-source-869dcfcdcd-ws5t8 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:44:59Z" message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 754.491µs message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:58:59Z" - latency: 835.442µs message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:57:59Z" - latency: 1.188814ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:56:59Z" - latency: 831.318µs message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:55:59Z" - latency: 1.180605ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:54:59Z" - latency: 1.008125ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:53:59Z" - latency: 830.976µs message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:52:59Z" - latency: 757.221µs message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:51:59Z" - latency: 1.313731ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:50:59Z" - latency: 790.932µs message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:49:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:37:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-175-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-175.ec2.internal uid: 49fa9730-adab-4e69-9cc0-7d37508c0d9a resourceVersion: "20147" uid: 1052c9a5-a2da-4977-87ef-b6b2564e7c83 spec: sourcePod: network-check-source-869dcfcdcd-ws5t8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T17: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.016554ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:55:59Z" - latency: 2.426923ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:55:59Z" - latency: 853.543µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:54:59Z" - latency: 1.558467ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:54:59Z" - latency: 1.136265ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:53:59Z" - latency: 1.720933ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:53:59Z" - latency: 1.036921ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:52:59Z" - latency: 1.782043ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:52:59Z" - latency: 851.853µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:51:59Z" - latency: 1.538752ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:51:59Z" kind: List metadata: resourceVersion: ""