apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T08:10:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-248-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-248.ec2.internal uid: a3c42907-37a3-4cbf-a79b-fdd662cd7cbd resourceVersion: "20524" uid: 799c843a-bc6f-433b-8c5f-be5e66c87c14 spec: sourcePod: network-check-source-7d88cb55d8-sfx7h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T08:17:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 914.393µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:31:44Z" - latency: 960.269µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:30:44Z" - latency: 1.035023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:29:44Z" - latency: 929.397µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:28:44Z" - latency: 1.045855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:27:44Z" - latency: 1.044869ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:26:44Z" - latency: 1.007551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:25:44Z" - latency: 997.559µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:24:44Z" - latency: 972.79µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:23:44Z" - latency: 1.047061ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:22:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T08:10:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-248-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-248.ec2.internal uid: a3c42907-37a3-4cbf-a79b-fdd662cd7cbd resourceVersion: "22130" uid: e4ddee6b-f900-42e6-8ebf-16ea1b49465e spec: sourcePod: network-check-source-7d88cb55d8-sfx7h targetEndpoint: a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T08:16:44Z" message: 'load-balancer-api-external: tcp connection to a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.499052ms message: 'load-balancer-api-external: tcp connection to a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:34:44Z" - latency: 8.350898ms message: 'load-balancer-api-external: resolved host name a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T08:34:44Z" - latency: 4.405998ms message: 'load-balancer-api-external: tcp connection to a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:33:44Z" - latency: 9.040486ms message: 'load-balancer-api-external: resolved host name a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T08:33:44Z" - latency: 5.338545ms message: 'load-balancer-api-external: tcp connection to a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:32:44Z" - latency: 14.615789ms message: 'load-balancer-api-external: resolved host name a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T08:32:44Z" - latency: 5.420862ms message: 'load-balancer-api-external: tcp connection to a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:31:44Z" - latency: 9.340597ms message: 'load-balancer-api-external: resolved host name a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T08:31:44Z" - latency: 4.742796ms message: 'load-balancer-api-external: tcp connection to a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:30:44Z" - latency: 8.933364ms message: 'load-balancer-api-external: resolved host name a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T08:30:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T08:10:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-248-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-248.ec2.internal uid: a3c42907-37a3-4cbf-a79b-fdd662cd7cbd resourceVersion: "22129" uid: 051f6f71-e2c7-47d6-bccc-f5bb64f011d3 spec: sourcePod: network-check-source-7d88cb55d8-sfx7h targetEndpoint: a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T08:16:44Z" message: 'load-balancer-api-internal: tcp connection to a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.333388ms message: 'load-balancer-api-internal: tcp connection to a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:34:44Z" - latency: 8.432419ms message: 'load-balancer-api-internal: resolved host name a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T08:34:44Z" - latency: 4.416401ms message: 'load-balancer-api-internal: tcp connection to a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:33:44Z" - latency: 9.003711ms message: 'load-balancer-api-internal: resolved host name a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T08:33:44Z" - latency: 5.291358ms message: 'load-balancer-api-internal: tcp connection to a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:32:44Z" - latency: 14.702463ms message: 'load-balancer-api-internal: resolved host name a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T08:32:44Z" - latency: 5.435227ms message: 'load-balancer-api-internal: tcp connection to a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:31:44Z" - latency: 9.279296ms message: 'load-balancer-api-internal: resolved host name a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T08:31:44Z" - latency: 4.725ms message: 'load-balancer-api-internal: tcp connection to a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:30:44Z" - latency: 9.041016ms message: 'load-balancer-api-internal: resolved host name a6df2de2eda174f88b2236593c42b026-f88b4d0f35c1bb41.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T08:30:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T08:10:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-248-to-network-check-target-ip-10-0-130-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-248.ec2.internal uid: a3c42907-37a3-4cbf-a79b-fdd662cd7cbd resourceVersion: "20521" uid: 9e29cfda-4ef9-443a-b490-80664f6ea24a spec: sourcePod: network-check-source-7d88cb55d8-sfx7h targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T08:17:44Z" message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 903.014µs message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:31:44Z" - latency: 847.798µs message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:30:44Z" - latency: 968.437µs message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:29:44Z" - latency: 886.487µs message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:28:44Z" - latency: 852.697µs message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:27:44Z" - latency: 965.576µs message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:26:44Z" - latency: 973.282µs message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:25:44Z" - latency: 1.191687ms message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:24:44Z" - latency: 824.907µs message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:23:44Z" - latency: 1.208179ms message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:22:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T08:10:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-248-to-network-check-target-ip-10-0-130-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-248.ec2.internal uid: a3c42907-37a3-4cbf-a79b-fdd662cd7cbd resourceVersion: "20522" uid: 053679a1-c9dd-41ea-85be-10bd42a4e666 spec: sourcePod: network-check-source-7d88cb55d8-sfx7h targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T08:17:44Z" message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.26049ms message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:31:44Z" - latency: 2.325746ms message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:30:44Z" - latency: 2.218363ms message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:29:44Z" - latency: 2.455565ms message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:28:44Z" - latency: 2.507217ms message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:27:44Z" - latency: 2.409032ms message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:26:44Z" - latency: 2.094246ms message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:25:44Z" - latency: 2.573343ms message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:24:44Z" - latency: 2.34395ms message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:23:44Z" - latency: 2.016922ms message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:22:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T08:10:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-248-to-network-check-target-ip-10-0-142-112 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-248.ec2.internal uid: a3c42907-37a3-4cbf-a79b-fdd662cd7cbd resourceVersion: "20523" uid: bec6e030-f947-4bfe-b85a-0b7f7d7f82de spec: sourcePod: network-check-source-7d88cb55d8-sfx7h targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T08:17:44Z" message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.200336ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:31:44Z" - latency: 2.071266ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:30:44Z" - latency: 2.193153ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:29:44Z" - latency: 2.508619ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:28:44Z" - latency: 2.211128ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:27:44Z" - latency: 2.251338ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:26:44Z" - latency: 2.287969ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:25:44Z" - latency: 2.141601ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:24:44Z" - latency: 2.329352ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:23:44Z" - latency: 2.212766ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:22:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T08:10:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-248-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-248.ec2.internal uid: a3c42907-37a3-4cbf-a79b-fdd662cd7cbd resourceVersion: "22128" uid: 12c3079b-fc7a-404f-910d-671065246dfe spec: sourcePod: network-check-source-7d88cb55d8-sfx7h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T08:16:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 978.84µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:34:44Z" - latency: 1.76574ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T08:34:44Z" - latency: 1.202714ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:33:44Z" - latency: 1.758809ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T08:33:44Z" - latency: 776.215µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:32:44Z" - latency: 1.688037ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T08:32:44Z" - latency: 961.971µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:31:44Z" - latency: 1.746677ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T08:31:44Z" - latency: 822.187µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T08:30:44Z" - latency: 1.628687ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T08:30:44Z" kind: List metadata: resourceVersion: ""