apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:56:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-96-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-96.ec2.internal uid: b34d435f-84a6-4893-a181-4973976621a3 resourceVersion: "30910" uid: 3e419cdb-ce0f-48da-9f24-10d13aab9ccd spec: sourcePod: network-check-source-56d84b9f44-7kjcv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T02:03:46Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.306691ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:10:46Z" - latency: 1.251797ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:09:46Z" - latency: 1.229956ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:08:46Z" - latency: 1.215941ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:07:46Z" - latency: 1.501558ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:06:46Z" - latency: 1.121819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:05:46Z" - latency: 1.327329ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:04:46Z" - latency: 872.333µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:03:46Z" - latency: 1.125468ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:02:46Z" - latency: 910.678µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:01:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:56:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-96-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-96.ec2.internal uid: b34d435f-84a6-4893-a181-4973976621a3 resourceVersion: "29373" uid: 43101248-d8a5-431d-b2d1-f85cb1be37d1 spec: sourcePod: network-check-source-56d84b9f44-7kjcv targetEndpoint: a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T02:02:46Z" message: 'load-balancer-api-external: tcp connection to a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.192579ms message: 'load-balancer-api-external: tcp connection to a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:08:46Z" - latency: 8.681146ms message: 'load-balancer-api-external: resolved host name a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:08:46Z" - latency: 4.503281ms message: 'load-balancer-api-external: tcp connection to a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:07:46Z" - latency: 8.277666ms message: 'load-balancer-api-external: resolved host name a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:07:46Z" - latency: 4.676455ms message: 'load-balancer-api-external: tcp connection to a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:06:46Z" - latency: 9.139878ms message: 'load-balancer-api-external: resolved host name a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:06:46Z" - latency: 5.677672ms message: 'load-balancer-api-external: tcp connection to a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:05:46Z" - latency: 6.887617ms message: 'load-balancer-api-external: resolved host name a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:05:46Z" - latency: 6.571684ms message: 'load-balancer-api-external: tcp connection to a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:04:46Z" - latency: 6.503654ms message: 'load-balancer-api-external: resolved host name a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:04:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:56:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-96-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-96.ec2.internal uid: b34d435f-84a6-4893-a181-4973976621a3 resourceVersion: "29374" uid: 193900e5-7034-44a7-8e2f-b2f528be426e spec: sourcePod: network-check-source-56d84b9f44-7kjcv targetEndpoint: a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T02:02:46Z" message: 'load-balancer-api-internal: tcp connection to a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.728129ms message: 'load-balancer-api-internal: tcp connection to a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:08:46Z" - latency: 8.647435ms message: 'load-balancer-api-internal: resolved host name a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:08:46Z" - latency: 4.06627ms message: 'load-balancer-api-internal: tcp connection to a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:07:46Z" - latency: 8.170559ms message: 'load-balancer-api-internal: resolved host name a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:07:46Z" - latency: 4.749035ms message: 'load-balancer-api-internal: tcp connection to a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:06:46Z" - latency: 9.074267ms message: 'load-balancer-api-internal: resolved host name a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:06:46Z" - latency: 5.679921ms message: 'load-balancer-api-internal: tcp connection to a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:05:46Z" - latency: 6.840182ms message: 'load-balancer-api-internal: resolved host name a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:05:46Z" - latency: 3.935543ms message: 'load-balancer-api-internal: tcp connection to a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:04:46Z" - latency: 6.430375ms message: 'load-balancer-api-internal: resolved host name a3efe92f4706546beb4f3315e0229341-8e5c3f17aaeee22f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:04:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:56:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-96-to-network-check-target-ip-10-0-135-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-96.ec2.internal uid: b34d435f-84a6-4893-a181-4973976621a3 resourceVersion: "30906" uid: a4f14321-5098-492a-9f66-6bbeed5c996d spec: sourcePod: network-check-source-56d84b9f44-7kjcv targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T02:03:46Z" message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 992.89µs message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:10:46Z" - latency: 859.639µs message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:09:46Z" - latency: 873.793µs message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:08:46Z" - latency: 810.18µs message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:07:46Z" - latency: 1.731008ms message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:06:46Z" - latency: 897.507µs message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:05:46Z" - latency: 1.34118ms message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:04:46Z" - latency: 1.517803ms message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:03:46Z" - latency: 872.898µs message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:02:46Z" - latency: 1.781712ms message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:01:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:56:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-96-to-network-check-target-ip-10-0-138-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-96.ec2.internal uid: b34d435f-84a6-4893-a181-4973976621a3 resourceVersion: "30908" uid: 80a72aa6-e7b0-45ef-85b0-1f6498b80aa8 spec: sourcePod: network-check-source-56d84b9f44-7kjcv targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T02:03:46Z" message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.750033ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:10:46Z" - latency: 2.459372ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:09:46Z" - latency: 2.49747ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:08:46Z" - latency: 2.02491ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:07:46Z" - latency: 2.4943ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:06:46Z" - latency: 2.213284ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:05:46Z" - latency: 2.285965ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:04:46Z" - latency: 2.374457ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:03:46Z" - latency: 2.546527ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:02:46Z" - latency: 2.764202ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:01:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:56:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-96-to-network-check-target-ip-10-0-142-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-96.ec2.internal uid: b34d435f-84a6-4893-a181-4973976621a3 resourceVersion: "30907" uid: cd2a16ed-389f-43b4-ac2b-a4f0ae4df3a4 spec: sourcePod: network-check-source-56d84b9f44-7kjcv targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T02:03:46Z" message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.266318ms message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:10:46Z" - latency: 2.415379ms message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:09:46Z" - latency: 2.114021ms message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:08:46Z" - latency: 2.131592ms message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:07:46Z" - latency: 2.682921ms message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:06:46Z" - latency: 2.792522ms message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:05:46Z" - latency: 2.148314ms message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:04:46Z" - latency: 2.431062ms message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:03:46Z" - latency: 2.457441ms message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:02:46Z" - latency: 2.655999ms message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:01:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:56:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-96-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-96.ec2.internal uid: b34d435f-84a6-4893-a181-4973976621a3 resourceVersion: "29372" uid: e47a830b-3a4e-450c-8fb8-ca7f218d8a82 spec: sourcePod: network-check-source-56d84b9f44-7kjcv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T02:02:46Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 807.518µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:08:46Z" - latency: 1.734784ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T02:08:46Z" - latency: 958.885µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:07:46Z" - latency: 1.754604ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T02:07:46Z" - latency: 809.453µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:06:46Z" - latency: 2.606273ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T02:06:46Z" - latency: 1.216657ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:05:46Z" - latency: 1.919691ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T02:05:46Z" - latency: 805.151µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:04:46Z" - latency: 1.694234ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T02:04:46Z" kind: List metadata: resourceVersion: ""