apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:14:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-160-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-160.ec2.internal uid: ddc36ba0-f04e-44d0-86bc-fafe5aa78111 resourceVersion: "55435" uid: 47b2f1c6-f1d3-4668-a62d-f791c349e602 spec: sourcePod: network-check-source-869dcfcdcd-dfqsk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T21:21:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.158563ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:49:36Z" - latency: 942.373µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:48:36Z" - latency: 1.250987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:47:36Z" - latency: 1.164435ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:46:36Z" - latency: 943.004µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:45:36Z" - latency: 1.13326ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:44:36Z" - latency: 1.114901ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:43:36Z" - latency: 1.230273ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:42:36Z" - latency: 1.317932ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:41:36Z" - latency: 1.223809ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:40:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:14:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-160-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-160.ec2.internal uid: ddc36ba0-f04e-44d0-86bc-fafe5aa78111 resourceVersion: "56442" uid: 2256f578-72bc-4105-90a4-975f355fb107 spec: sourcePod: network-check-source-869dcfcdcd-dfqsk targetEndpoint: a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T21:20:36Z" message: 'load-balancer-api-external: tcp connection to a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.681084ms message: 'load-balancer-api-external: tcp connection to a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:50:36Z" - latency: 8.857449ms message: 'load-balancer-api-external: resolved host name a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:50:36Z" - latency: 5.194401ms message: 'load-balancer-api-external: tcp connection to a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:49:36Z" - latency: 8.989094ms message: 'load-balancer-api-external: resolved host name a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:49:36Z" - latency: 5.561756ms message: 'load-balancer-api-external: tcp connection to a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:48:36Z" - latency: 9.105052ms message: 'load-balancer-api-external: resolved host name a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:48:36Z" - latency: 4.630694ms message: 'load-balancer-api-external: tcp connection to a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:47:36Z" - latency: 9.67202ms message: 'load-balancer-api-external: resolved host name a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:47:36Z" - latency: 3.948403ms message: 'load-balancer-api-external: tcp connection to a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:46:36Z" - latency: 8.062647ms message: 'load-balancer-api-external: resolved host name a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:46:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:14:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-160-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-160.ec2.internal uid: ddc36ba0-f04e-44d0-86bc-fafe5aa78111 resourceVersion: "56443" uid: 1546f6b1-affe-4307-8609-2abc6eb2b1a0 spec: sourcePod: network-check-source-869dcfcdcd-dfqsk targetEndpoint: a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T21:20:36Z" message: 'load-balancer-api-internal: tcp connection to a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.698505ms message: 'load-balancer-api-internal: tcp connection to a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:50:36Z" - latency: 8.894769ms message: 'load-balancer-api-internal: resolved host name a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:50:36Z" - latency: 5.229257ms message: 'load-balancer-api-internal: tcp connection to a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:49:36Z" - latency: 9.007426ms message: 'load-balancer-api-internal: resolved host name a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:49:36Z" - latency: 5.52208ms message: 'load-balancer-api-internal: tcp connection to a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:48:36Z" - latency: 9.15791ms message: 'load-balancer-api-internal: resolved host name a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:48:36Z" - latency: 4.617207ms message: 'load-balancer-api-internal: tcp connection to a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:47:36Z" - latency: 9.700117ms message: 'load-balancer-api-internal: resolved host name a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:47:36Z" - latency: 3.970672ms message: 'load-balancer-api-internal: tcp connection to a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:46:36Z" - latency: 8.197493ms message: 'load-balancer-api-internal: resolved host name a6559d05eb16a467f894f3853ffe3173-1f419e91a4f43553.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:46:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:14:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-160-to-network-check-target-ip-10-0-131-147 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-160.ec2.internal uid: ddc36ba0-f04e-44d0-86bc-fafe5aa78111 resourceVersion: "55433" uid: 61a42d7b-bd69-4ada-b1fb-f9a85f0e3775 spec: sourcePod: network-check-source-869dcfcdcd-dfqsk targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T21:21:36Z" message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.273792ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:49:36Z" - latency: 1.938184ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:48:36Z" - latency: 1.8244ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:47:36Z" - latency: 2.039817ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:46:36Z" - latency: 2.014591ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:45:36Z" - latency: 1.99816ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:44:36Z" - latency: 1.962594ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:43:36Z" - latency: 2.185971ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:42:36Z" - latency: 2.01456ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:41:36Z" - latency: 1.872827ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:40:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:14:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-160-to-network-check-target-ip-10-0-136-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-160.ec2.internal uid: ddc36ba0-f04e-44d0-86bc-fafe5aa78111 resourceVersion: "55432" uid: d459e67f-d400-4a91-a7f0-01b8a18f7dbf spec: sourcePod: network-check-source-869dcfcdcd-dfqsk targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T21:21:36Z" message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 940.489µs message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:49:36Z" - latency: 851.541µs message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:48:36Z" - latency: 911.276µs message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:47:36Z" - latency: 1.04475ms message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:46:36Z" - latency: 1.115851ms message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:45:36Z" - latency: 980.299µs message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:44:36Z" - latency: 1.027522ms message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:43:36Z" - latency: 989.044µs message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:42:36Z" - latency: 1.168887ms message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:41:36Z" - latency: 927.741µs message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:40:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:14:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-160-to-network-check-target-ip-10-0-143-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-160.ec2.internal uid: ddc36ba0-f04e-44d0-86bc-fafe5aa78111 resourceVersion: "55434" uid: 987e0440-0224-4076-abb8-01d3bdec65d1 spec: sourcePod: network-check-source-869dcfcdcd-dfqsk targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-13T21:21:36Z" message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.256851ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:49:36Z" - latency: 2.307416ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:48:36Z" - latency: 2.287495ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:47:36Z" - latency: 2.179497ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:46:36Z" - latency: 2.312458ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:45:36Z" - latency: 2.266658ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:44:36Z" - latency: 2.164626ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:43:36Z" - latency: 2.150597ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:42:36Z" - latency: 2.240881ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:41:36Z" - latency: 2.104716ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:40:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:14:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-160-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-160.ec2.internal uid: ddc36ba0-f04e-44d0-86bc-fafe5aa78111 resourceVersion: "56440" uid: eed6f1f3-8e28-4aad-8d83-d318737f1013 spec: sourcePod: network-check-source-869dcfcdcd-dfqsk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T21:20:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 870.805µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:50:36Z" - latency: 2.093643ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:50:36Z" - latency: 945.356µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:49:36Z" - latency: 1.790106ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:49:36Z" - latency: 769.987µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:48:36Z" - latency: 2.057855ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:48:36Z" - latency: 923.551µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:47:36Z" - latency: 2.046425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:47:36Z" - latency: 1.223788ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:46:36Z" - latency: 1.846119ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:46:36Z" kind: List metadata: resourceVersion: ""