apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T00:15:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-86-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-86.ec2.internal uid: fc5a3457-4126-44b3-91dd-e27699f1eaf6 resourceVersion: "44971" uid: 82751bf1-440c-4a0e-ad81-2d91bff07826 spec: sourcePod: network-check-source-dbd9cf844-r5kqd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T00:22:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.20442ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:43:17Z" - latency: 1.184975ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:42:17Z" - latency: 923.603µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:41:17Z" - latency: 871.946µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:40:17Z" - latency: 1.474851ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:39:17Z" - latency: 974.762µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:38:17Z" - latency: 1.042547ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:37:17Z" - latency: 1.160377ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:36:17Z" - latency: 860.98µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:35:17Z" - latency: 1.20878ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:34:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T00:15:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-86-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-86.ec2.internal uid: fc5a3457-4126-44b3-91dd-e27699f1eaf6 resourceVersion: "47135" uid: 7b152cda-a94d-463e-ae61-5c9a38b347d4 spec: sourcePod: network-check-source-dbd9cf844-r5kqd targetEndpoint: a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T00:21:17Z" message: 'load-balancer-api-external: tcp connection to a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.620976ms message: 'load-balancer-api-external: tcp connection to a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:45:17Z" - latency: 12.638188ms message: 'load-balancer-api-external: resolved host name a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:45:17Z" - latency: 3.415665ms message: 'load-balancer-api-external: tcp connection to a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:44:17Z" - latency: 10.152646ms message: 'load-balancer-api-external: resolved host name a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:44:17Z" - latency: 4.697029ms message: 'load-balancer-api-external: tcp connection to a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:43:17Z" - latency: 8.710868ms message: 'load-balancer-api-external: resolved host name a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:43:17Z" - latency: 4.501987ms message: 'load-balancer-api-external: tcp connection to a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:42:17Z" - latency: 11.704555ms message: 'load-balancer-api-external: resolved host name a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:42:17Z" - latency: 3.660355ms message: 'load-balancer-api-external: tcp connection to a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:41:17Z" - latency: 14.042618ms message: 'load-balancer-api-external: resolved host name a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:41:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T00:15:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-86-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-86.ec2.internal uid: fc5a3457-4126-44b3-91dd-e27699f1eaf6 resourceVersion: "47136" uid: 77df0e62-5b6d-4fe6-a934-a2d57a7159a4 spec: sourcePod: network-check-source-dbd9cf844-r5kqd targetEndpoint: a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T00:21:17Z" message: 'load-balancer-api-internal: tcp connection to a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.508778ms message: 'load-balancer-api-internal: tcp connection to a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:45:17Z" - latency: 12.707745ms message: 'load-balancer-api-internal: resolved host name a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:45:17Z" - latency: 3.426101ms message: 'load-balancer-api-internal: tcp connection to a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:44:17Z" - latency: 10.092622ms message: 'load-balancer-api-internal: resolved host name a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:44:17Z" - latency: 4.705628ms message: 'load-balancer-api-internal: tcp connection to a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:43:17Z" - latency: 8.672258ms message: 'load-balancer-api-internal: resolved host name a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:43:17Z" - latency: 4.460381ms message: 'load-balancer-api-internal: tcp connection to a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:42:17Z" - latency: 11.667879ms message: 'load-balancer-api-internal: resolved host name a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:42:17Z" - latency: 4.164018ms message: 'load-balancer-api-internal: tcp connection to a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:41:17Z" - latency: 13.989851ms message: 'load-balancer-api-internal: resolved host name a6a1285b76e844ababddd6cd63774daa-4aab003e93f3b8b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:41:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T00:15:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-86-to-network-check-target-ip-10-0-138-128 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-86.ec2.internal uid: fc5a3457-4126-44b3-91dd-e27699f1eaf6 resourceVersion: "44970" uid: 8ebd8beb-c5dc-42f8-aba4-10ec211702e9 spec: sourcePod: network-check-source-dbd9cf844-r5kqd targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T00:22:17Z" message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.469881ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:43:17Z" - latency: 2.272095ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:42:17Z" - latency: 2.47481ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:41:17Z" - latency: 2.395839ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:40:17Z" - latency: 2.499049ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:39:17Z" - latency: 2.309555ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:38:17Z" - latency: 2.451998ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:37:17Z" - latency: 2.401526ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:36:17Z" - latency: 2.588803ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:35:17Z" - latency: 2.309533ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:34:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T00:15:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-86-to-network-check-target-ip-10-0-138-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-86.ec2.internal uid: fc5a3457-4126-44b3-91dd-e27699f1eaf6 resourceVersion: "44969" uid: db2f2463-238f-4ef3-9ba5-33f26532c23b spec: sourcePod: network-check-source-dbd9cf844-r5kqd targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T00:22:17Z" message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.491989ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:43:17Z" - latency: 2.349232ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:42:17Z" - latency: 2.079524ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:41:17Z" - latency: 2.523548ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:40:17Z" - latency: 2.340282ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:39:17Z" - latency: 2.305672ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:38:17Z" - latency: 2.298637ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:37:17Z" - latency: 2.27001ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:36:17Z" - latency: 2.851897ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:35:17Z" - latency: 2.306248ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:34:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T00:15:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-86-to-network-check-target-ip-10-0-143-86 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-86.ec2.internal uid: fc5a3457-4126-44b3-91dd-e27699f1eaf6 resourceVersion: "44968" uid: 6dd296f5-e619-4424-adc7-0e70ef535fa3 spec: sourcePod: network-check-source-dbd9cf844-r5kqd targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T00:22:17Z" message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 858.474µs message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:43:17Z" - latency: 952.727µs message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:42:17Z" - latency: 1.106378ms message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:41:17Z" - latency: 950.167µs message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:40:17Z" - latency: 1.146332ms message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:39:17Z" - latency: 1.3327ms message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:38:17Z" - latency: 1.255453ms message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:37:17Z" - latency: 951.768µs message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:36:17Z" - latency: 933.592µs message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:35:17Z" - latency: 819.588µs message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:34:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T00:15:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-86-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-86.ec2.internal uid: fc5a3457-4126-44b3-91dd-e27699f1eaf6 resourceVersion: "47134" uid: 9358460a-b7cd-4a60-a185-17eb7f2d6744 spec: sourcePod: network-check-source-dbd9cf844-r5kqd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T00:21:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 949.298µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:45:17Z" - latency: 2.253095ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T00:45:17Z" - latency: 1.108344ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:44:17Z" - latency: 1.623529ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T00:44:17Z" - latency: 869.839µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:43:17Z" - latency: 1.74215ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T00:43:17Z" - latency: 860.088µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:42:17Z" - latency: 1.672047ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T00:42:17Z" - latency: 1.030684ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:41:17Z" - latency: 1.738373ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T00:41:17Z" kind: List metadata: resourceVersion: ""