apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T04:03:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-120-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-120.ec2.internal uid: 7db2a9aa-991c-430c-bfa3-97d82418a063 resourceVersion: "24649" uid: a0e5a04c-4198-4de4-ad60-295bbd7e818d spec: sourcePod: network-check-source-8894fc9bd-55n56 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-21T04:10:10Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 962.143µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:17:10Z" - latency: 1.211356ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:16:10Z" - latency: 892.334µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:15:10Z" - latency: 907.615µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:14:10Z" - latency: 977.599µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:13:10Z" - latency: 952.921µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:12:10Z" - latency: 897.453µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:11:10Z" - latency: 1.257324ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:10:10Z" - latency: 1.360752ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:09:10Z" - latency: 1.074877ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:08:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T04:03:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-120-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-120.ec2.internal uid: 7db2a9aa-991c-430c-bfa3-97d82418a063 resourceVersion: "23569" uid: ba59e350-b09d-4331-8781-0f488eb896b0 spec: sourcePod: network-check-source-8894fc9bd-55n56 targetEndpoint: afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T04:09:10Z" message: 'load-balancer-api-external: tcp connection to afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.865832ms message: 'load-balancer-api-external: tcp connection to afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:15:10Z" - latency: 6.574809ms message: 'load-balancer-api-external: resolved host name afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:15:10Z" - latency: 4.431346ms message: 'load-balancer-api-external: tcp connection to afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:14:10Z" - latency: 8.320321ms message: 'load-balancer-api-external: resolved host name afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:14:10Z" - latency: 4.03239ms message: 'load-balancer-api-external: tcp connection to afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:13:10Z" - latency: 8.548667ms message: 'load-balancer-api-external: resolved host name afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:13:10Z" - latency: 3.866249ms message: 'load-balancer-api-external: tcp connection to afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:12:10Z" - latency: 6.939802ms message: 'load-balancer-api-external: resolved host name afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:12:10Z" - latency: 4.969534ms message: 'load-balancer-api-external: tcp connection to afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:11:10Z" - latency: 8.763936ms message: 'load-balancer-api-external: resolved host name afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:11:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T04:03:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-120-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-120.ec2.internal uid: 7db2a9aa-991c-430c-bfa3-97d82418a063 resourceVersion: "23570" uid: f02ddfd5-0a3e-49b3-9a8a-4b7fb3f5b3c6 spec: sourcePod: network-check-source-8894fc9bd-55n56 targetEndpoint: afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T04:09:10Z" message: 'load-balancer-api-internal: tcp connection to afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.888437ms message: 'load-balancer-api-internal: tcp connection to afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:15:10Z" - latency: 6.470661ms message: 'load-balancer-api-internal: resolved host name afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:15:10Z" - latency: 5.100607ms message: 'load-balancer-api-internal: tcp connection to afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:14:10Z" - latency: 8.352853ms message: 'load-balancer-api-internal: resolved host name afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:14:10Z" - latency: 4.790801ms message: 'load-balancer-api-internal: tcp connection to afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:13:10Z" - latency: 8.520465ms message: 'load-balancer-api-internal: resolved host name afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:13:10Z" - latency: 3.844676ms message: 'load-balancer-api-internal: tcp connection to afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:12:10Z" - latency: 7.009135ms message: 'load-balancer-api-internal: resolved host name afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:12:10Z" - latency: 4.924721ms message: 'load-balancer-api-internal: tcp connection to afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:11:10Z" - latency: 8.812376ms message: 'load-balancer-api-internal: resolved host name afc3150da08804c9e96450fab3ec4916-3af4c1e01c379e21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:11:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T04:03:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-120-to-network-check-target-ip-10-0-131-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-120.ec2.internal uid: 7db2a9aa-991c-430c-bfa3-97d82418a063 resourceVersion: "24648" uid: 9bf967d2-9894-46d6-ba73-e3d41d42fa89 spec: sourcePod: network-check-source-8894fc9bd-55n56 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T04:10:10Z" message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.362109ms message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:17:10Z" - latency: 2.292798ms message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:16:10Z" - latency: 2.306972ms message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:15:10Z" - latency: 2.253828ms message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:14:10Z" - latency: 2.169325ms message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:13:10Z" - latency: 2.141559ms message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:12:10Z" - latency: 2.323018ms message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:11:10Z" - latency: 2.23687ms message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:10:10Z" - latency: 2.148265ms message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:09:10Z" - latency: 2.267648ms message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:08:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T04:03:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-120-to-network-check-target-ip-10-0-134-136 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-120.ec2.internal uid: 7db2a9aa-991c-430c-bfa3-97d82418a063 resourceVersion: "24647" uid: 559944e6-1f22-498e-8622-23a59139e7d4 spec: sourcePod: network-check-source-8894fc9bd-55n56 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-21T04:10:10Z" message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.387459ms message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:17:10Z" - latency: 2.080429ms message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:16:10Z" - latency: 2.008121ms message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:15:10Z" - latency: 2.625493ms message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:14:10Z" - latency: 2.176235ms message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:13:10Z" - latency: 2.193823ms message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:12:10Z" - latency: 2.444ms message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:11:10Z" - latency: 2.218774ms message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:10:10Z" - latency: 2.893306ms message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:09:10Z" - latency: 2.27745ms message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:08:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T04:03:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-120-to-network-check-target-ip-10-0-138-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-120.ec2.internal uid: 7db2a9aa-991c-430c-bfa3-97d82418a063 resourceVersion: "24646" uid: 458d7c56-27dd-4c5e-8ef1-e71df0a48fe4 spec: sourcePod: network-check-source-8894fc9bd-55n56 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T04:10:10Z" message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 950.725µs message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:17:10Z" - latency: 899.614µs message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:16:10Z" - latency: 1.331627ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:15:10Z" - latency: 1.158064ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:14:10Z" - latency: 1.22139ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:13:10Z" - latency: 879.538µs message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:12:10Z" - latency: 1.2445ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:11:10Z" - latency: 984.236µs message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:10:10Z" - latency: 1.395508ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:09:10Z" - latency: 1.173147ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:08:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T04:03:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-120-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-120.ec2.internal uid: 7db2a9aa-991c-430c-bfa3-97d82418a063 resourceVersion: "23568" uid: 2da9d1bf-5592-4a28-ad5d-7f2591e091d4 spec: sourcePod: network-check-source-8894fc9bd-55n56 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-21T04:09:10Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 862.813µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:15:10Z" - latency: 1.632147ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T04:15:10Z" - latency: 886.02µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:14:10Z" - latency: 2.751806ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T04:14:10Z" - latency: 858.469µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:13:10Z" - latency: 2.253119ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T04:13:10Z" - latency: 1.09812ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:12:10Z" - latency: 2.002215ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T04:12:10Z" - latency: 877.187µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:11:10Z" - latency: 1.716995ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T04:11:10Z" kind: List metadata: resourceVersion: ""