apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T22:08:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-77-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-77.ec2.internal uid: f3ae052c-f27e-4ed4-9a62-9c1d9b24c364 resourceVersion: "45339" uid: 3c31b04a-226c-4275-b5c3-9b9b364b13c6 spec: sourcePod: network-check-source-dbd9cf844-pgkht targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-06T22:15:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.229589ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:36:31Z" - latency: 1.136184ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:35:31Z" - latency: 1.106272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:34:31Z" - latency: 1.126058ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:33:31Z" - latency: 823.008µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:32:31Z" - latency: 859.956µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:31:31Z" - latency: 1.490819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:30:31Z" - latency: 1.122124ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:29:31Z" - latency: 985.164µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:28:31Z" - latency: 1.0056ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:27:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T22:08:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-77-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-77.ec2.internal uid: f3ae052c-f27e-4ed4-9a62-9c1d9b24c364 resourceVersion: "47325" uid: dbe8735a-0fc3-48d0-bbbb-844f15888895 spec: sourcePod: network-check-source-dbd9cf844-pgkht targetEndpoint: aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-06T22:14:31Z" message: 'load-balancer-api-external: tcp connection to aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.49002ms message: 'load-balancer-api-external: tcp connection to aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:38:31Z" - latency: 6.631251ms message: 'load-balancer-api-external: resolved host name aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T22:38:31Z" - latency: 5.591209ms message: 'load-balancer-api-external: tcp connection to aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:37:31Z" - latency: 6.242788ms message: 'load-balancer-api-external: resolved host name aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T22:37:31Z" - latency: 5.791404ms message: 'load-balancer-api-external: tcp connection to aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:36:31Z" - latency: 7.115125ms message: 'load-balancer-api-external: resolved host name aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T22:36:31Z" - latency: 4.968693ms message: 'load-balancer-api-external: tcp connection to aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:35:31Z" - latency: 6.785637ms message: 'load-balancer-api-external: resolved host name aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T22:35:31Z" - latency: 4.677082ms message: 'load-balancer-api-external: tcp connection to aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:34:31Z" - latency: 7.058831ms message: 'load-balancer-api-external: resolved host name aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T22:34:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T22:08:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-77-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-77.ec2.internal uid: f3ae052c-f27e-4ed4-9a62-9c1d9b24c364 resourceVersion: "47324" uid: 5dfbdcb4-a172-460c-9811-04d57eb56b4f spec: sourcePod: network-check-source-dbd9cf844-pgkht targetEndpoint: aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-06T22:14:31Z" message: 'load-balancer-api-internal: tcp connection to aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.249521ms message: 'load-balancer-api-internal: tcp connection to aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:38:31Z" - latency: 6.552286ms message: 'load-balancer-api-internal: resolved host name aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T22:38:31Z" - latency: 5.562667ms message: 'load-balancer-api-internal: tcp connection to aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:37:31Z" - latency: 6.330084ms message: 'load-balancer-api-internal: resolved host name aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T22:37:31Z" - latency: 5.830592ms message: 'load-balancer-api-internal: tcp connection to aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:36:31Z" - latency: 7.033538ms message: 'load-balancer-api-internal: resolved host name aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T22:36:31Z" - latency: 4.922462ms message: 'load-balancer-api-internal: tcp connection to aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:35:31Z" - latency: 6.866794ms message: 'load-balancer-api-internal: resolved host name aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T22:35:31Z" - latency: 4.956003ms message: 'load-balancer-api-internal: tcp connection to aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:34:31Z" - latency: 6.985174ms message: 'load-balancer-api-internal: resolved host name aa73ee21efe13474da4547d68cf50311-b7350afd508ab27e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T22:34:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T22:08:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-77-to-network-check-target-ip-10-0-136-77 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-77.ec2.internal uid: f3ae052c-f27e-4ed4-9a62-9c1d9b24c364 resourceVersion: "45336" uid: 0f164f99-7225-4d3c-abb0-9168bf8bbbe4 spec: sourcePod: network-check-source-dbd9cf844-pgkht targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-06T22:15:31Z" message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.368258ms message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:36:31Z" - latency: 791.608µs message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:35:31Z" - latency: 767.471µs message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:34:31Z" - latency: 1.448512ms message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:33:31Z" - latency: 849.292µs message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:32:31Z" - latency: 1.014603ms message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:31:31Z" - latency: 895.037µs message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:30:31Z" - latency: 843.274µs message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:29:31Z" - latency: 1.319683ms message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:28:31Z" - latency: 870.066µs message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:27:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T22:08:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-77-to-network-check-target-ip-10-0-139-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-77.ec2.internal uid: f3ae052c-f27e-4ed4-9a62-9c1d9b24c364 resourceVersion: "45337" uid: 4b5b6637-3b86-4236-9a52-537738afc58e spec: sourcePod: network-check-source-dbd9cf844-pgkht targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-06T22:15:31Z" message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.248832ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:36:31Z" - latency: 1.950434ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:35:31Z" - latency: 1.954906ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:34:31Z" - latency: 2.144697ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:33:31Z" - latency: 2.201284ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:32:31Z" - latency: 1.765748ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:31:31Z" - latency: 1.969443ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:30:31Z" - latency: 1.833395ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:29:31Z" - latency: 2.203771ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:28:31Z" - latency: 2.072184ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:27:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T22:08:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-77-to-network-check-target-ip-10-0-141-122 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-77.ec2.internal uid: f3ae052c-f27e-4ed4-9a62-9c1d9b24c364 resourceVersion: "45338" uid: e0d1ed57-d7c3-43b0-80ec-840f65fd7f4a spec: sourcePod: network-check-source-dbd9cf844-pgkht targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-06T22:15:31Z" message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.615183ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:36:31Z" - latency: 2.429686ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:35:31Z" - latency: 2.296683ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:34:31Z" - latency: 2.45485ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:33:31Z" - latency: 2.035856ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:32:31Z" - latency: 2.245712ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:31:31Z" - latency: 2.123065ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:30:31Z" - latency: 2.251712ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:29:31Z" - latency: 2.15791ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:28:31Z" - latency: 2.304165ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:27:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T22:08:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-77-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-77.ec2.internal uid: f3ae052c-f27e-4ed4-9a62-9c1d9b24c364 resourceVersion: "47323" uid: 6b34b916-4975-4a23-9345-029fbfc6a999 spec: sourcePod: network-check-source-dbd9cf844-pgkht targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-06T22:14:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 935.625µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:38:31Z" - latency: 1.779593ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T22:38:31Z" - latency: 1.009095ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:37:31Z" - latency: 1.689304ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T22:37:31Z" - latency: 845.434µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:36:31Z" - latency: 2.211425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T22:36:31Z" - latency: 935.165µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:35:31Z" - latency: 1.840363ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T22:35:31Z" - latency: 886.874µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T22:34:31Z" - latency: 2.008272ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T22:34:31Z" kind: List metadata: resourceVersion: ""