apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T13:51:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-17-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-17.ec2.internal uid: 2c34ecac-243d-4447-a3b3-a47f29e795c0 resourceVersion: "44823" uid: bad2119c-f0ba-44a2-bd9e-8c522a609eb1 spec: sourcePod: network-check-source-56d84b9f44-655gw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-03T13:58:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.087054ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:19:40Z" - latency: 1.011169ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:18:40Z" - latency: 1.078187ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:17:40Z" - latency: 972.731µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:16:40Z" - latency: 804.911µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:15:40Z" - latency: 1.027035ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:14:40Z" - latency: 792.213µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:13:40Z" - latency: 987.498µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:12:40Z" - latency: 1.386357ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:11:40Z" - latency: 864.916µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:10:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T13:51:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-17-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-17.ec2.internal uid: 2c34ecac-243d-4447-a3b3-a47f29e795c0 resourceVersion: "47333" uid: 6dfd2319-541b-4888-ac26-fdfc52213fda spec: sourcePod: network-check-source-56d84b9f44-655gw targetEndpoint: ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T13:57:40Z" message: 'load-balancer-api-external: tcp connection to ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.062646ms message: 'load-balancer-api-external: tcp connection to ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:21:40Z" - latency: 6.492313ms message: 'load-balancer-api-external: resolved host name ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T14:21:40Z" - latency: 4.44775ms message: 'load-balancer-api-external: tcp connection to ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:20:40Z" - latency: 6.541034ms message: 'load-balancer-api-external: resolved host name ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T14:20:40Z" - latency: 5.334257ms message: 'load-balancer-api-external: tcp connection to ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:19:40Z" - latency: 6.596611ms message: 'load-balancer-api-external: resolved host name ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T14:19:40Z" - latency: 5.608859ms message: 'load-balancer-api-external: tcp connection to ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:18:40Z" - latency: 7.063559ms message: 'load-balancer-api-external: resolved host name ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T14:18:40Z" - latency: 4.682012ms message: 'load-balancer-api-external: tcp connection to ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:17:40Z" - latency: 6.78923ms message: 'load-balancer-api-external: resolved host name ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T14:17:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T13:51:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-17-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-17.ec2.internal uid: 2c34ecac-243d-4447-a3b3-a47f29e795c0 resourceVersion: "47332" uid: ed1f7c05-de34-4d3a-9206-8aa33ce9b82a spec: sourcePod: network-check-source-56d84b9f44-655gw targetEndpoint: ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T13:57:40Z" message: 'load-balancer-api-internal: tcp connection to ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.794554ms message: 'load-balancer-api-internal: tcp connection to ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:21:40Z" - latency: 6.398293ms message: 'load-balancer-api-internal: resolved host name ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T14:21:40Z" - latency: 4.475827ms message: 'load-balancer-api-internal: tcp connection to ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:20:40Z" - latency: 6.478795ms message: 'load-balancer-api-internal: resolved host name ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T14:20:40Z" - latency: 3.963015ms message: 'load-balancer-api-internal: tcp connection to ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:19:40Z" - latency: 6.610413ms message: 'load-balancer-api-internal: resolved host name ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T14:19:40Z" - latency: 5.578274ms message: 'load-balancer-api-internal: tcp connection to ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:18:40Z" - latency: 7.169026ms message: 'load-balancer-api-internal: resolved host name ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T14:18:40Z" - latency: 4.687181ms message: 'load-balancer-api-internal: tcp connection to ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:17:40Z" - latency: 6.704641ms message: 'load-balancer-api-internal: resolved host name ab1ad339f1ec34641bd3f477b66074a9-98d925e8e59b96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T14:17:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T13:51:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-17-to-network-check-target-ip-10-0-131-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-17.ec2.internal uid: 2c34ecac-243d-4447-a3b3-a47f29e795c0 resourceVersion: "44820" uid: f4ac0724-e4cc-49ce-b7ff-455823f9ba1b spec: sourcePod: network-check-source-56d84b9f44-655gw targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T13:58:40Z" message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.324298ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:19:40Z" - latency: 840.398µs message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:18:40Z" - latency: 859.73µs message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:17:40Z" - latency: 993.921µs message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:16:40Z" - latency: 1.045231ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:15:40Z" - latency: 1.333739ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:14:40Z" - latency: 1.170928ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:13:40Z" - latency: 855.08µs message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:12:40Z" - latency: 806.736µs message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:11:40Z" - latency: 1.113517ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:10:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T13:51:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-17-to-network-check-target-ip-10-0-139-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-17.ec2.internal uid: 2c34ecac-243d-4447-a3b3-a47f29e795c0 resourceVersion: "44821" uid: e4e6a5cd-b631-461d-8a90-7f5b0e18b248 spec: sourcePod: network-check-source-56d84b9f44-655gw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T13:58:40Z" message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.610927ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:19:40Z" - latency: 2.739931ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:18:40Z" - latency: 2.161315ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:17:40Z" - latency: 2.287646ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:16:40Z" - latency: 2.189794ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:15:40Z" - latency: 2.348275ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:14:40Z" - latency: 2.346322ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:13:40Z" - latency: 2.402549ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:12:40Z" - latency: 2.118834ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:11:40Z" - latency: 2.114917ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:10:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T13:51:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-17-to-network-check-target-ip-10-0-143-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-17.ec2.internal uid: 2c34ecac-243d-4447-a3b3-a47f29e795c0 resourceVersion: "44822" uid: 208483d5-fe2f-492c-a1f7-453098492a0e spec: sourcePod: network-check-source-56d84b9f44-655gw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-03T13:58:40Z" message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.258189ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:19:40Z" - latency: 2.298768ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:18:40Z" - latency: 2.211129ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:17:40Z" - latency: 2.230625ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:16:40Z" - latency: 1.988207ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:15:40Z" - latency: 2.239879ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:14:40Z" - latency: 2.196874ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:13:40Z" - latency: 1.970181ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:12:40Z" - latency: 1.976118ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:11:40Z" - latency: 1.66055ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:10:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T13:51:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-17-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-17.ec2.internal uid: 2c34ecac-243d-4447-a3b3-a47f29e795c0 resourceVersion: "47331" uid: ead72131-1424-4b65-9d28-3a62a75eb052 spec: sourcePod: network-check-source-56d84b9f44-655gw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-03T13:57:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 947.184µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:21:40Z" - latency: 1.646539ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T14:21:40Z" - latency: 1.223328ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:20:40Z" - latency: 1.924931ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T14:20:40Z" - latency: 1.251472ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:19:40Z" - latency: 1.657733ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T14:19:40Z" - latency: 1.007356ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:18:40Z" - latency: 1.682624ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T14:18:40Z" - latency: 1.129772ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T14:17:40Z" - latency: 1.681213ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T14:17:40Z" kind: List metadata: resourceVersion: ""