apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:45:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-221-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-221.ec2.internal uid: 6a5af3b9-8623-453b-949a-f64cf26db2dd resourceVersion: "54959" uid: ef269902-6611-498c-802b-85a90a78e457 spec: sourcePod: network-check-source-989f8b8dc-dvgc9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T15:52:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.285975ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:20:19Z" - latency: 1.054859ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:19Z" - latency: 929.925µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:19Z" - latency: 1.507454ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:19Z" - latency: 1.177525ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:19Z" - latency: 1.767415ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:19Z" - latency: 858.664µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:14:19Z" - latency: 902.981µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:13:19Z" - latency: 1.080907ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:12:19Z" - latency: 823.803µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:11:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:45:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-221-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-221.ec2.internal uid: 6a5af3b9-8623-453b-949a-f64cf26db2dd resourceVersion: "56044" uid: e0162aec-b421-4bcb-a896-1a16f4218421 spec: sourcePod: network-check-source-989f8b8dc-dvgc9 targetEndpoint: a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T15:51:19Z" message: 'load-balancer-api-external: tcp connection to a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.681554ms message: 'load-balancer-api-external: tcp connection to a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:21:19Z" - latency: 8.249571ms message: 'load-balancer-api-external: resolved host name a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:21:19Z" - latency: 4.096353ms message: 'load-balancer-api-external: tcp connection to a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:20:19Z" - latency: 8.66889ms message: 'load-balancer-api-external: resolved host name a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:20:19Z" - latency: 2.936158ms message: 'load-balancer-api-external: tcp connection to a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:19Z" - latency: 7.19936ms message: 'load-balancer-api-external: resolved host name a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:19:19Z" - latency: 2.937143ms message: 'load-balancer-api-external: tcp connection to a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:19Z" - latency: 7.123721ms message: 'load-balancer-api-external: resolved host name a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:18:19Z" - latency: 4.268876ms message: 'load-balancer-api-external: tcp connection to a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:19Z" - latency: 7.715228ms message: 'load-balancer-api-external: resolved host name a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:17:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:45:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-221-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-221.ec2.internal uid: 6a5af3b9-8623-453b-949a-f64cf26db2dd resourceVersion: "56045" uid: a7dc1833-8a76-47cb-87b8-278f810da104 spec: sourcePod: network-check-source-989f8b8dc-dvgc9 targetEndpoint: a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T15:51:19Z" message: 'load-balancer-api-internal: tcp connection to a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.686213ms message: 'load-balancer-api-internal: tcp connection to a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:21:19Z" - latency: 8.302936ms message: 'load-balancer-api-internal: resolved host name a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:21:19Z" - latency: 4.875101ms message: 'load-balancer-api-internal: tcp connection to a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:20:19Z" - latency: 8.779625ms message: 'load-balancer-api-internal: resolved host name a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:20:19Z" - latency: 4.841828ms message: 'load-balancer-api-internal: tcp connection to a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:19Z" - latency: 7.166489ms message: 'load-balancer-api-internal: resolved host name a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:19:19Z" - latency: 2.92998ms message: 'load-balancer-api-internal: tcp connection to a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:19Z" - latency: 7.194945ms message: 'load-balancer-api-internal: resolved host name a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:18:19Z" - latency: 4.263598ms message: 'load-balancer-api-internal: tcp connection to a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:19Z" - latency: 7.837277ms message: 'load-balancer-api-internal: resolved host name a3bc0dabaed8f47e897d087234e89926-dcda53dd3b55c5ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:17:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:45:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-221-to-network-check-target-ip-10-0-128-7 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-221.ec2.internal uid: 6a5af3b9-8623-453b-949a-f64cf26db2dd resourceVersion: "54958" uid: 9ba69a47-2c8a-4afb-a442-91a8ce9225f7 spec: sourcePod: network-check-source-989f8b8dc-dvgc9 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:52:19Z" message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.460202ms message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:20:19Z" - latency: 2.26755ms message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:19Z" - latency: 1.994467ms message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:19Z" - latency: 2.404262ms message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:19Z" - latency: 2.366594ms message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:19Z" - latency: 2.797068ms message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:19Z" - latency: 2.231305ms message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:14:19Z" - latency: 2.034706ms message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:13:19Z" - latency: 2.724583ms message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:12:19Z" - latency: 1.926024ms message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:11:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:45:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-221-to-network-check-target-ip-10-0-131-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-221.ec2.internal uid: 6a5af3b9-8623-453b-949a-f64cf26db2dd resourceVersion: "54956" uid: c3b0cff6-af2e-4097-a183-ad4704024ad4 spec: sourcePod: network-check-source-989f8b8dc-dvgc9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:52:19Z" message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.767µs message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:20:19Z" - latency: 860.98µs message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:19Z" - latency: 1.109243ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:19Z" - latency: 1.142069ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:19Z" - latency: 1.2207ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:19Z" - latency: 1.505423ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:19Z" - latency: 1.071473ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:14:19Z" - latency: 743.395µs message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:13:19Z" - latency: 913.534µs message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:12:19Z" - latency: 1.289762ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:11:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:45:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-221-to-network-check-target-ip-10-0-132-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-221.ec2.internal uid: 6a5af3b9-8623-453b-949a-f64cf26db2dd resourceVersion: "54957" uid: cdf5fb6a-4b42-4ea1-980f-443501fe7a5c spec: sourcePod: network-check-source-989f8b8dc-dvgc9 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:52:19Z" message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.369667ms message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:20:19Z" - latency: 2.84723ms message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:19Z" - latency: 2.138588ms message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:19Z" - latency: 2.438507ms message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:19Z" - latency: 2.442905ms message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:19Z" - latency: 3.009701ms message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:19Z" - latency: 2.038086ms message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:14:19Z" - latency: 2.268178ms message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:13:19Z" - latency: 2.944635ms message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:12:19Z" - latency: 2.007961ms message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:11:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:45:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-221-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-221.ec2.internal uid: 6a5af3b9-8623-453b-949a-f64cf26db2dd resourceVersion: "56043" uid: 238a91ae-5c86-4513-87bc-eaed91356709 spec: sourcePod: network-check-source-989f8b8dc-dvgc9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T15:51:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 789.172µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:21:19Z" - latency: 1.865509ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:21:19Z" - latency: 884.482µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:20:19Z" - latency: 1.838369ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:20:19Z" - latency: 689.652µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:19Z" - latency: 1.624906ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:19:19Z" - latency: 868.317µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:19Z" - latency: 1.716189ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:18:19Z" - latency: 829.87µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:19Z" - latency: 1.95621ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:17:19Z" kind: List metadata: resourceVersion: ""