apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T00:56:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-44-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-44.ec2.internal uid: 7890d52b-1989-474f-af34-e06a6d442959 resourceVersion: "75813" uid: d8d90614-443e-4b26-899a-dde607ee269b spec: sourcePod: network-check-source-7d88cb55d8-xrzzl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T01:03:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 983.951µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:28Z" - latency: 1.181636ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:51:28Z" - latency: 1.769978ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:50:28Z" - latency: 1.033201ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:49:28Z" - latency: 1.573541ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:48:28Z" - latency: 1.02985ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:47:28Z" - latency: 1.24829ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:46:28Z" - latency: 1.145223ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:45:28Z" - latency: 1.50348ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:44:28Z" - latency: 1.077296ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:43:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T00:56:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-44-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-44.ec2.internal uid: 7890d52b-1989-474f-af34-e06a6d442959 resourceVersion: "79729" uid: 8d832126-517e-4b67-9de0-90e708c687aa spec: sourcePod: network-check-source-7d88cb55d8-xrzzl targetEndpoint: afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T01:02:28Z" message: 'load-balancer-api-external: tcp connection to afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.331842ms message: 'load-balancer-api-external: tcp connection to afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:28Z" - latency: 7.136891ms message: 'load-balancer-api-external: resolved host name afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:56:28Z" - latency: 4.544065ms message: 'load-balancer-api-external: tcp connection to afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:28Z" - latency: 6.94457ms message: 'load-balancer-api-external: resolved host name afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:55:28Z" - latency: 5.575569ms message: 'load-balancer-api-external: tcp connection to afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:54:28Z" - latency: 6.753202ms message: 'load-balancer-api-external: resolved host name afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:54:28Z" - latency: 5.282013ms message: 'load-balancer-api-external: tcp connection to afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:53:28Z" - latency: 7.288971ms message: 'load-balancer-api-external: resolved host name afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:53:28Z" - latency: 4.273444ms message: 'load-balancer-api-external: tcp connection to afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:28Z" - latency: 7.789002ms message: 'load-balancer-api-external: resolved host name afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:52:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T00:56:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-44-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-44.ec2.internal uid: 7890d52b-1989-474f-af34-e06a6d442959 resourceVersion: "79730" uid: 0fdfb5ad-9e6c-42bd-bd4e-5f7e75dcb8c9 spec: sourcePod: network-check-source-7d88cb55d8-xrzzl targetEndpoint: afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T01:02:28Z" message: 'load-balancer-api-internal: tcp connection to afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.103712ms message: 'load-balancer-api-internal: tcp connection to afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:28Z" - latency: 7.21318ms message: 'load-balancer-api-internal: resolved host name afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:56:28Z" - latency: 4.543264ms message: 'load-balancer-api-internal: tcp connection to afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:28Z" - latency: 6.872616ms message: 'load-balancer-api-internal: resolved host name afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:55:28Z" - latency: 5.609378ms message: 'load-balancer-api-internal: tcp connection to afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:54:28Z" - latency: 6.630254ms message: 'load-balancer-api-internal: resolved host name afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:54:28Z" - latency: 5.299966ms message: 'load-balancer-api-internal: tcp connection to afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:53:28Z" - latency: 7.260327ms message: 'load-balancer-api-internal: resolved host name afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:53:28Z" - latency: 5.594237ms message: 'load-balancer-api-internal: tcp connection to afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:28Z" - latency: 7.737742ms message: 'load-balancer-api-internal: resolved host name afec2574f58554198b2bdecc84cc978c-75182989f48b2d15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:52:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T00:56:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-44-to-network-check-target-ip-10-0-132-238 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-44.ec2.internal uid: 7890d52b-1989-474f-af34-e06a6d442959 resourceVersion: "75811" uid: b8f0bb27-dd26-4989-bc24-cab9a5e83296 spec: sourcePod: network-check-source-7d88cb55d8-xrzzl targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T01:03:28Z" message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.252787ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:28Z" - latency: 2.244077ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:51:28Z" - latency: 2.624787ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:50:28Z" - latency: 2.437499ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:49:28Z" - latency: 2.607363ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:48:28Z" - latency: 2.170108ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:47:28Z" - latency: 2.356816ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:46:28Z" - latency: 2.559652ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:45:28Z" - latency: 2.474186ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:44:28Z" - latency: 2.339431ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:43:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T00:56:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-44-to-network-check-target-ip-10-0-132-44 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-44.ec2.internal uid: 7890d52b-1989-474f-af34-e06a6d442959 resourceVersion: "75810" uid: a1bb1577-bc2d-4fec-99dc-61f2379e337d spec: sourcePod: network-check-source-7d88cb55d8-xrzzl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T01:03:28Z" message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.003196ms message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:28Z" - latency: 1.051419ms message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:51:28Z" - latency: 1.316453ms message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:50:28Z" - latency: 985.554µs message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:49:28Z" - latency: 1.75644ms message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:48:28Z" - latency: 917.339µs message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:47:28Z" - latency: 1.183841ms message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:46:28Z" - latency: 1.498368ms message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:45:28Z" - latency: 1.483666ms message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:44:28Z" - latency: 978.248µs message: 'network-check-target-ip-10-0-132-44: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:43:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T00:56:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-44-to-network-check-target-ip-10-0-138-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-44.ec2.internal uid: 7890d52b-1989-474f-af34-e06a6d442959 resourceVersion: "75812" uid: 05fcdb6c-c5fa-4ba3-837c-6253d6ce7022 spec: sourcePod: network-check-source-7d88cb55d8-xrzzl targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T01:03:28Z" message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.441204ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:28Z" - latency: 2.248893ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:51:28Z" - latency: 2.275294ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:50:28Z" - latency: 2.528534ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:49:28Z" - latency: 2.559805ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:48:28Z" - latency: 2.453457ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:47:28Z" - latency: 2.179065ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:46:28Z" - latency: 2.757955ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:45:28Z" - latency: 2.256816ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:44:28Z" - latency: 2.414588ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:43:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T00:56:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-44-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-44.ec2.internal uid: 7890d52b-1989-474f-af34-e06a6d442959 resourceVersion: "79728" uid: edf4560f-40e0-49c3-a6b5-ad9c334e1363 spec: sourcePod: network-check-source-7d88cb55d8-xrzzl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T01:02:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.12851ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:28Z" - latency: 1.846167ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:56:28Z" - latency: 1.11326ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:28Z" - latency: 1.802486ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:55:28Z" - latency: 1.037047ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:54:28Z" - latency: 1.735445ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:54:28Z" - latency: 981.878µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:53:28Z" - latency: 1.775549ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:53:28Z" - latency: 997.556µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:28Z" - latency: 2.313358ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:52:28Z" kind: List metadata: resourceVersion: ""