apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:08:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-231-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-231.ec2.internal uid: e746ff65-8bf7-4529-b4c4-31215b5da346 resourceVersion: "24089" uid: c5f72d59-8fa3-4675-8759-5287a07aa578 spec: sourcePod: network-check-source-8894fc9bd-svqbc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-21T10:15:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 926.902µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:22:47Z" - latency: 1.062175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:21:47Z" - latency: 1.124267ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:20:47Z" - latency: 1.244812ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:19:47Z" - latency: 1.046762ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:18:47Z" - latency: 1.240441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:17:47Z" - latency: 1.003556ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:16:47Z" - latency: 972.993µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:15:47Z" - latency: 1.050578ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:14:47Z" - latency: 738.964µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:13:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:08:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-231-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-231.ec2.internal uid: e746ff65-8bf7-4529-b4c4-31215b5da346 resourceVersion: "23006" uid: d88a4a40-36b2-464d-b658-7691565d7a59 spec: sourcePod: network-check-source-8894fc9bd-svqbc targetEndpoint: a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T10:14:47Z" message: 'load-balancer-api-external: tcp connection to a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.828378ms message: 'load-balancer-api-external: tcp connection to a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:20:47Z" - latency: 11.418167ms message: 'load-balancer-api-external: resolved host name a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:20:47Z" - latency: 4.701907ms message: 'load-balancer-api-external: tcp connection to a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:19:47Z" - latency: 8.30842ms message: 'load-balancer-api-external: resolved host name a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:19:47Z" - latency: 6.39392ms message: 'load-balancer-api-external: tcp connection to a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:18:47Z" - latency: 17.521238ms message: 'load-balancer-api-external: resolved host name a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:18:47Z" - latency: 5.244258ms message: 'load-balancer-api-external: tcp connection to a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:17:47Z" - latency: 10.28418ms message: 'load-balancer-api-external: resolved host name a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:17:47Z" - latency: 5.493302ms message: 'load-balancer-api-external: tcp connection to a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:16:47Z" - latency: 14.312169ms message: 'load-balancer-api-external: resolved host name a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:16:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:08:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-231-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-231.ec2.internal uid: e746ff65-8bf7-4529-b4c4-31215b5da346 resourceVersion: "23005" uid: aa8595e3-e96b-483c-8a76-777cacfb29b7 spec: sourcePod: network-check-source-8894fc9bd-svqbc targetEndpoint: a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T10:14:47Z" message: 'load-balancer-api-internal: tcp connection to a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.130258ms message: 'load-balancer-api-internal: tcp connection to a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:20:47Z" - latency: 11.449394ms message: 'load-balancer-api-internal: resolved host name a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:20:47Z" - latency: 4.713804ms message: 'load-balancer-api-internal: tcp connection to a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:19:47Z" - latency: 8.283319ms message: 'load-balancer-api-internal: resolved host name a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:19:47Z" - latency: 6.41405ms message: 'load-balancer-api-internal: tcp connection to a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:18:47Z" - latency: 17.55787ms message: 'load-balancer-api-internal: resolved host name a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:18:47Z" - latency: 5.228248ms message: 'load-balancer-api-internal: tcp connection to a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:17:47Z" - latency: 10.364934ms message: 'load-balancer-api-internal: resolved host name a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:17:47Z" - latency: 6.058716ms message: 'load-balancer-api-internal: tcp connection to a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:16:47Z" - latency: 14.370166ms message: 'load-balancer-api-internal: resolved host name a4cfcc79d650d4ac5bf67070fe5155ab-4446f6144fc4bed7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:16:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:08:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-231-to-network-check-target-ip-10-0-132-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-231.ec2.internal uid: e746ff65-8bf7-4529-b4c4-31215b5da346 resourceVersion: "24088" uid: 9107ebf0-74eb-44f3-b020-7e827b103620 spec: sourcePod: network-check-source-8894fc9bd-svqbc targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T10:15:47Z" message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.106016ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:22:47Z" - latency: 1.91476ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:21:47Z" - latency: 1.925427ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:20:47Z" - latency: 1.838224ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:19:47Z" - latency: 1.96731ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:18:47Z" - latency: 1.613122ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:17:47Z" - latency: 1.761562ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:16:47Z" - latency: 1.716959ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:15:47Z" - latency: 2.146409ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:14:47Z" - latency: 1.878919ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:13:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:08:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-231-to-network-check-target-ip-10-0-140-144 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-231.ec2.internal uid: e746ff65-8bf7-4529-b4c4-31215b5da346 resourceVersion: "24087" uid: d1ac3371-24f5-4eec-bfa0-c6e6117c738e spec: sourcePod: network-check-source-8894fc9bd-svqbc targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T10:15:47Z" message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.049317ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:22:47Z" - latency: 1.857922ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:21:47Z" - latency: 2.091944ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:20:47Z" - latency: 1.967299ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:19:47Z" - latency: 2.166039ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:18:47Z" - latency: 2.168028ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:17:47Z" - latency: 2.289185ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:16:47Z" - latency: 2.227338ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:15:47Z" - latency: 2.899386ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:14:47Z" - latency: 2.013651ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:13:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:08:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-231-to-network-check-target-ip-10-0-140-231 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-231.ec2.internal uid: e746ff65-8bf7-4529-b4c4-31215b5da346 resourceVersion: "24086" uid: 12c0b58b-e81d-4512-86c7-2ea2c55409ee spec: sourcePod: network-check-source-8894fc9bd-svqbc targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T10:15:47Z" message: 'network-check-target-ip-10-0-140-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.187089ms message: 'network-check-target-ip-10-0-140-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:22:47Z" - latency: 723.957µs message: 'network-check-target-ip-10-0-140-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:21:47Z" - latency: 809.276µs message: 'network-check-target-ip-10-0-140-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:20:47Z" - latency: 812.064µs message: 'network-check-target-ip-10-0-140-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:19:47Z" - latency: 1.486834ms message: 'network-check-target-ip-10-0-140-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:18:47Z" - latency: 789.851µs message: 'network-check-target-ip-10-0-140-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:17:47Z" - latency: 804.765µs message: 'network-check-target-ip-10-0-140-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:16:47Z" - latency: 783.113µs message: 'network-check-target-ip-10-0-140-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:15:47Z" - latency: 1.548165ms message: 'network-check-target-ip-10-0-140-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:14:47Z" - latency: 959.051µs message: 'network-check-target-ip-10-0-140-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:13:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:08:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-231-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-231.ec2.internal uid: e746ff65-8bf7-4529-b4c4-31215b5da346 resourceVersion: "23004" uid: 40888a3c-4960-4b8e-9ddb-688ceb9abe5a spec: sourcePod: network-check-source-8894fc9bd-svqbc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-21T10:14:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.175614ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:20:47Z" - latency: 1.882244ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T10:20:47Z" - latency: 875.754µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:19:47Z" - latency: 1.644706ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T10:19:47Z" - latency: 933.277µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:18:47Z" - latency: 2.382915ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T10:18:47Z" - latency: 1.115554ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:17:47Z" - latency: 2.038069ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T10:17:47Z" - latency: 933.648µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:16:47Z" - latency: 1.661883ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T10:16:47Z" kind: List metadata: resourceVersion: ""