apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T02:25:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-102-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-102.ec2.internal uid: d7f2bbe2-81d4-43d2-9e55-73bc32a1dd43 resourceVersion: "45788" uid: 83756a6d-2166-44db-895b-a9928dcf70d0 spec: sourcePod: network-check-source-dbd9cf844-lrnzj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T02:32:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 960.58µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:53:18Z" - latency: 777.682µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:52:18Z" - latency: 888.111µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:51:18Z" - latency: 1.22388ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:50:18Z" - latency: 957.7µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:49:18Z" - latency: 1.117362ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:48:18Z" - latency: 1.03585ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:47:18Z" - latency: 962.684µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:46:18Z" - latency: 1.263211ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:45:18Z" - latency: 1.433475ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:44:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T02:25:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-102-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-102.ec2.internal uid: d7f2bbe2-81d4-43d2-9e55-73bc32a1dd43 resourceVersion: "47979" uid: 14041ab8-4cf7-4c09-bd7a-842d2df2c932 spec: sourcePod: network-check-source-dbd9cf844-lrnzj targetEndpoint: a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T02:31:18Z" message: 'load-balancer-api-external: tcp connection to a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.963235ms message: 'load-balancer-api-external: tcp connection to a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:55:18Z" - latency: 6.531478ms message: 'load-balancer-api-external: resolved host name a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T02:55:18Z" - latency: 5.11199ms message: 'load-balancer-api-external: tcp connection to a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:54:18Z" - latency: 6.433131ms message: 'load-balancer-api-external: resolved host name a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T02:54:18Z" - latency: 4.607276ms message: 'load-balancer-api-external: tcp connection to a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:53:18Z" - latency: 6.577912ms message: 'load-balancer-api-external: resolved host name a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T02:53:18Z" - latency: 5.042818ms message: 'load-balancer-api-external: tcp connection to a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:52:18Z" - latency: 6.529623ms message: 'load-balancer-api-external: resolved host name a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T02:52:18Z" - latency: 5.395815ms message: 'load-balancer-api-external: tcp connection to a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:51:18Z" - latency: 7.298586ms message: 'load-balancer-api-external: resolved host name a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T02:51:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T02:25:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-102-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-102.ec2.internal uid: d7f2bbe2-81d4-43d2-9e55-73bc32a1dd43 resourceVersion: "47978" uid: ff5b761a-6d8e-468d-a053-9c079d86f1ac spec: sourcePod: network-check-source-dbd9cf844-lrnzj targetEndpoint: a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T02:31:18Z" message: 'load-balancer-api-internal: tcp connection to a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.944989ms message: 'load-balancer-api-internal: tcp connection to a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:55:18Z" - latency: 6.475128ms message: 'load-balancer-api-internal: resolved host name a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T02:55:18Z" - latency: 5.158639ms message: 'load-balancer-api-internal: tcp connection to a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:54:18Z" - latency: 6.392856ms message: 'load-balancer-api-internal: resolved host name a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T02:54:18Z" - latency: 5.200963ms message: 'load-balancer-api-internal: tcp connection to a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:53:18Z" - latency: 6.529194ms message: 'load-balancer-api-internal: resolved host name a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T02:53:18Z" - latency: 5.013496ms message: 'load-balancer-api-internal: tcp connection to a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:52:18Z" - latency: 6.583149ms message: 'load-balancer-api-internal: resolved host name a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T02:52:18Z" - latency: 5.444789ms message: 'load-balancer-api-internal: tcp connection to a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:51:18Z" - latency: 7.233503ms message: 'load-balancer-api-internal: resolved host name a726db9031d5d4768836e2a7b293bd88-f0565e309eb25176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T02:51:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T02:25:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-102-to-network-check-target-ip-10-0-128-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-102.ec2.internal uid: d7f2bbe2-81d4-43d2-9e55-73bc32a1dd43 resourceVersion: "45787" uid: 887dcd2d-9190-4614-840f-a670f7b505f4 spec: sourcePod: network-check-source-dbd9cf844-lrnzj targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T02:32:18Z" message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.932938ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:53:18Z" - latency: 1.525265ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:52:18Z" - latency: 2.162663ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:51:18Z" - latency: 1.882718ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:50:18Z" - latency: 1.310954ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:49:18Z" - latency: 1.73918ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:48:18Z" - latency: 1.847865ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:47:18Z" - latency: 2.28264ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:46:18Z" - latency: 2.089139ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:45:18Z" - latency: 2.115848ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:44:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T02:25:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-102-to-network-check-target-ip-10-0-133-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-102.ec2.internal uid: d7f2bbe2-81d4-43d2-9e55-73bc32a1dd43 resourceVersion: "45786" uid: b0eadaf0-7d69-4e03-befa-46c52336188d spec: sourcePod: network-check-source-dbd9cf844-lrnzj targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T02:32:18Z" message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.029468ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:53:18Z" - latency: 1.915685ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:52:18Z" - latency: 2.298579ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:51:18Z" - latency: 2.443801ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:50:18Z" - latency: 1.891079ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:49:18Z" - latency: 2.075831ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:48:18Z" - latency: 1.775832ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:47:18Z" - latency: 2.315301ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:46:18Z" - latency: 2.098672ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:45:18Z" - latency: 2.214441ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:44:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T02:25:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-102-to-network-check-target-ip-10-0-143-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-102.ec2.internal uid: d7f2bbe2-81d4-43d2-9e55-73bc32a1dd43 resourceVersion: "45785" uid: b55b2a78-fb7b-4595-ab86-d842fd3f5077 spec: sourcePod: network-check-source-dbd9cf844-lrnzj targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T02:32:18Z" message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.16004ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:53:18Z" - latency: 798.935µs message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:52:18Z" - latency: 1.469457ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:51:18Z" - latency: 1.322004ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:50:18Z" - latency: 1.001174ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:49:18Z" - latency: 1.043473ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:48:18Z" - latency: 858.569µs message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:47:18Z" - latency: 1.331433ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:46:18Z" - latency: 1.301202ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:45:18Z" - latency: 912.569µs message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:44:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T02:25:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-102-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-102.ec2.internal uid: d7f2bbe2-81d4-43d2-9e55-73bc32a1dd43 resourceVersion: "47977" uid: 5ad57607-7609-4cc4-90e6-ee5827967b28 spec: sourcePod: network-check-source-dbd9cf844-lrnzj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T02:31:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.070964ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:55:18Z" - latency: 2.076717ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T02:55:18Z" - latency: 1.143543ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:54:18Z" - latency: 1.687955ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T02:54:18Z" - latency: 868.05µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:53:18Z" - latency: 1.947656ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T02:53:18Z" - latency: 789.722µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:52:18Z" - latency: 1.739784ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T02:52:18Z" - latency: 965.503µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T02:51:18Z" - latency: 2.332515ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T02:51:18Z" kind: List metadata: resourceVersion: ""