apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:17:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-106-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-106.ec2.internal uid: f9039d80-237b-4c7c-8b3b-29b9746f46f9 resourceVersion: "54014" uid: 8efb4e7f-5176-422f-9ead-7bae16050030 spec: sourcePod: network-check-source-989f8b8dc-ck4lm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T20:24: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.477034ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:52:31Z" - latency: 1.18571ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:51:31Z" - latency: 1.089687ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:50:31Z" - latency: 1.512542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:49:31Z" - latency: 907.494µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:48:31Z" - latency: 879.782µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:47:31Z" - latency: 1.188715ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:46:31Z" - latency: 1.283799ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:45:31Z" - latency: 882.661µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:44:31Z" - latency: 1.563369ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:43:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:17:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-106-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-106.ec2.internal uid: f9039d80-237b-4c7c-8b3b-29b9746f46f9 resourceVersion: "55014" uid: 9653b4f0-973d-489a-af4a-c99ef1bdbcfa spec: sourcePod: network-check-source-989f8b8dc-ck4lm targetEndpoint: a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T20:23:31Z" message: 'load-balancer-api-external: tcp connection to a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.128831ms message: 'load-balancer-api-external: tcp connection to a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:53:31Z" - latency: 8.97997ms message: 'load-balancer-api-external: resolved host name a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:53:31Z" - latency: 6.080869ms message: 'load-balancer-api-external: tcp connection to a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:52:31Z" - latency: 9.03487ms message: 'load-balancer-api-external: resolved host name a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:52:31Z" - latency: 5.535131ms message: 'load-balancer-api-external: tcp connection to a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:51:31Z" - latency: 9.038029ms message: 'load-balancer-api-external: resolved host name a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:51:31Z" - latency: 5.348738ms message: 'load-balancer-api-external: tcp connection to a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:50:31Z" - latency: 8.606788ms message: 'load-balancer-api-external: resolved host name a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:50:31Z" - latency: 5.671338ms message: 'load-balancer-api-external: tcp connection to a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:49:31Z" - latency: 9.20587ms message: 'load-balancer-api-external: resolved host name a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:49:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:17:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-106-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-106.ec2.internal uid: f9039d80-237b-4c7c-8b3b-29b9746f46f9 resourceVersion: "55015" uid: 8b73b8c1-8725-49bb-a610-cbc98edb08ca spec: sourcePod: network-check-source-989f8b8dc-ck4lm targetEndpoint: a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T20:23:31Z" message: 'load-balancer-api-internal: tcp connection to a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.388019ms message: 'load-balancer-api-internal: tcp connection to a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:53:31Z" - latency: 8.999175ms message: 'load-balancer-api-internal: resolved host name a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:53:31Z" - latency: 4.248822ms message: 'load-balancer-api-internal: tcp connection to a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:52:31Z" - latency: 9.061312ms message: 'load-balancer-api-internal: resolved host name a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:52:31Z" - latency: 5.577283ms message: 'load-balancer-api-internal: tcp connection to a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:51:31Z" - latency: 8.978993ms message: 'load-balancer-api-internal: resolved host name a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:51:31Z" - latency: 4.626431ms message: 'load-balancer-api-internal: tcp connection to a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:50:31Z" - latency: 8.577141ms message: 'load-balancer-api-internal: resolved host name a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:50:31Z" - latency: 5.622872ms message: 'load-balancer-api-internal: tcp connection to a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:49:31Z" - latency: 9.226575ms message: 'load-balancer-api-internal: resolved host name a4c376c0a0b144bccb8b60521bb996ff-542fe4622e2eb115.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:49:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:17:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-106-to-network-check-target-ip-10-0-130-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-106.ec2.internal uid: f9039d80-237b-4c7c-8b3b-29b9746f46f9 resourceVersion: "54012" uid: ae22c825-cc0b-47d1-adb1-a1d795ea1cc9 spec: sourcePod: network-check-source-989f8b8dc-ck4lm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:24:31Z" message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.197157ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:52:31Z" - latency: 1.769618ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:51:31Z" - latency: 2.099279ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:50:31Z" - latency: 2.578649ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:49:31Z" - latency: 1.970358ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:48:31Z" - latency: 1.723468ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:47:31Z" - latency: 1.986052ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:46:31Z" - latency: 2.05109ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:45:31Z" - latency: 2.052091ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:44:31Z" - latency: 2.144416ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:43:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:17:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-106-to-network-check-target-ip-10-0-133-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-106.ec2.internal uid: f9039d80-237b-4c7c-8b3b-29b9746f46f9 resourceVersion: "54013" uid: 3e356036-9cb5-4123-8f07-b8ec4f0cbf4a spec: sourcePod: network-check-source-989f8b8dc-ck4lm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:24:31Z" message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.334049ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:52:31Z" - latency: 773.1µs message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:51:31Z" - latency: 1.338762ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:50:31Z" - latency: 1.068263ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:49:31Z" - latency: 766.055µs message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:48:31Z" - latency: 755.7µs message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:47:31Z" - latency: 1.393707ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:46:31Z" - latency: 1.461708ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:45:31Z" - latency: 785.931µs message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:44:31Z" - latency: 775.364µs message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:43:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:45:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-106-to-network-check-target-ip-10-0-136-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-106.ec2.internal uid: f9039d80-237b-4c7c-8b3b-29b9746f46f9 resourceVersion: "54342" uid: c5789f0f-1863-4313-ab6e-d5547d5412a0 spec: sourcePod: network-check-source-989f8b8dc-ck4lm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:52:49Z" message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.211462ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:52:49Z" - latency: 2.078891ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:51:49Z" - latency: 2.406707ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:50:49Z" - latency: 2.241177ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:49:49Z" - latency: 2.602007ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:48:49Z" - latency: 2.760959ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:47:49Z" - latency: 2.642292ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:46:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:17:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-106-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-106.ec2.internal uid: f9039d80-237b-4c7c-8b3b-29b9746f46f9 resourceVersion: "55013" uid: 22fff9fe-5350-47f5-a257-c11f7d1beeb6 spec: sourcePod: network-check-source-989f8b8dc-ck4lm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T20:23:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.003155ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:53:31Z" - latency: 1.732222ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:53:31Z" - latency: 716.803µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:52:31Z" - latency: 2.254335ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:52:31Z" - latency: 2.021558ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:51:31Z" - latency: 1.741181ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:51:31Z" - latency: 768.965µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:50:31Z" - latency: 1.680502ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:50:31Z" - latency: 838.514µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:49:31Z" - latency: 1.966518ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:49:31Z" kind: List metadata: resourceVersion: ""