apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T13:02:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-236-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-236.us-east-2.compute.internal uid: bf0f7649-e941-44b2-a792-d5841d32c8ef resourceVersion: "66738" uid: 633ad86d-e3d1-4795-b285-6fb41c74d6aa spec: sourcePod: network-check-source-6f78d59f99-h2pxh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T13:09:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.535471ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:30:18Z" - latency: 1.482819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:29:18Z" - latency: 974.129µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:28:18Z" - latency: 1.123675ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:27:18Z" - latency: 1.179653ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:26:18Z" - latency: 1.017709ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:25:18Z" - latency: 1.293233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:24:18Z" - latency: 1.994833ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:23:18Z" - latency: 1.575286ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:22:18Z" - latency: 1.243994ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:21:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T13:02:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-236-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-236.us-east-2.compute.internal uid: bf0f7649-e941-44b2-a792-d5841d32c8ef resourceVersion: "69699" uid: 2bfe5890-333e-4180-abf6-79b56cb1b487 spec: sourcePod: network-check-source-6f78d59f99-h2pxh targetEndpoint: a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T13:08:18Z" message: 'load-balancer-api-external: tcp connection to a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.30873ms message: 'load-balancer-api-external: tcp connection to a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:32:18Z" - latency: 7.486602ms message: 'load-balancer-api-external: resolved host name a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:32:18Z" - latency: 6.862726ms message: 'load-balancer-api-external: tcp connection to a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:31:18Z" - latency: 12.859628ms message: 'load-balancer-api-external: resolved host name a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:31:18Z" - latency: 5.926777ms message: 'load-balancer-api-external: tcp connection to a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:30:18Z" - latency: 9.383857ms message: 'load-balancer-api-external: resolved host name a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:30:18Z" - latency: 7.835897ms message: 'load-balancer-api-external: tcp connection to a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:29:18Z" - latency: 10.241364ms message: 'load-balancer-api-external: resolved host name a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:29:18Z" - latency: 5.161523ms message: 'load-balancer-api-external: tcp connection to a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:28:18Z" - latency: 8.275432ms message: 'load-balancer-api-external: resolved host name a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:28:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T13:02:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-236-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-236.us-east-2.compute.internal uid: bf0f7649-e941-44b2-a792-d5841d32c8ef resourceVersion: "69700" uid: 66742c4a-c65f-4a7b-a0a0-afdb96927cc6 spec: sourcePod: network-check-source-6f78d59f99-h2pxh targetEndpoint: a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T13:08:18Z" message: 'load-balancer-api-internal: tcp connection to a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.758919ms message: 'load-balancer-api-internal: tcp connection to a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:32:18Z" - latency: 7.478698ms message: 'load-balancer-api-internal: resolved host name a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:32:18Z" - latency: 6.341507ms message: 'load-balancer-api-internal: tcp connection to a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:31:18Z" - latency: 12.925566ms message: 'load-balancer-api-internal: resolved host name a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:31:18Z" - latency: 5.898505ms message: 'load-balancer-api-internal: tcp connection to a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:30:18Z" - latency: 9.334189ms message: 'load-balancer-api-internal: resolved host name a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:30:18Z" - latency: 7.790128ms message: 'load-balancer-api-internal: tcp connection to a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:29:18Z" - latency: 10.312878ms message: 'load-balancer-api-internal: resolved host name a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:29:18Z" - latency: 5.147798ms message: 'load-balancer-api-internal: tcp connection to a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:28:18Z" - latency: 8.240145ms message: 'load-balancer-api-internal: resolved host name a8cd97a079c9d41069d65b8b66cd23df-b2c8350ca9cbc67d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:28:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T13:02:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-236-to-network-check-target-ip-10-0-134-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-236.us-east-2.compute.internal uid: bf0f7649-e941-44b2-a792-d5841d32c8ef resourceVersion: "66735" uid: ba143029-b124-4c85-be20-33eed16af6a3 spec: sourcePod: network-check-source-6f78d59f99-h2pxh targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T13:09:18Z" message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.011701ms message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:30:18Z" - latency: 1.059544ms message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:29:18Z" - latency: 1.822678ms message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:28:18Z" - latency: 1.581388ms message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:27:18Z" - latency: 1.713949ms message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:26:18Z" - latency: 1.062921ms message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:25:18Z" - latency: 1.007124ms message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:24:18Z" - latency: 1.493447ms message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:23:18Z" - latency: 1.502532ms message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:22:18Z" - latency: 1.097022ms message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:21:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T13:02:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-236-to-network-check-target-ip-10-0-137-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-236.us-east-2.compute.internal uid: bf0f7649-e941-44b2-a792-d5841d32c8ef resourceVersion: "66736" uid: 75232a23-b61c-42e7-a246-b193574bd723 spec: sourcePod: network-check-source-6f78d59f99-h2pxh targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T13:09:18Z" message: 'network-check-target-ip-10-0-137-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.503706ms message: 'network-check-target-ip-10-0-137-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:30:18Z" - latency: 2.582786ms message: 'network-check-target-ip-10-0-137-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:29:18Z" - latency: 2.185675ms message: 'network-check-target-ip-10-0-137-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:28:18Z" - latency: 2.497772ms message: 'network-check-target-ip-10-0-137-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:27:18Z" - latency: 2.391707ms message: 'network-check-target-ip-10-0-137-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:26:18Z" - latency: 2.52432ms message: 'network-check-target-ip-10-0-137-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:25:18Z" - latency: 2.490731ms message: 'network-check-target-ip-10-0-137-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:24:18Z" - latency: 2.717169ms message: 'network-check-target-ip-10-0-137-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:23:18Z" - latency: 2.541835ms message: 'network-check-target-ip-10-0-137-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:22:18Z" - latency: 2.743348ms message: 'network-check-target-ip-10-0-137-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:21:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T13:02:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-236-to-network-check-target-ip-10-0-141-83 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-236.us-east-2.compute.internal uid: bf0f7649-e941-44b2-a792-d5841d32c8ef resourceVersion: "66737" uid: 8aea491e-a7a6-4787-a880-c6aa43f2bea8 spec: sourcePod: network-check-source-6f78d59f99-h2pxh targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T13:09:18Z" message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.669516ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:30:18Z" - latency: 2.303384ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:29:18Z" - latency: 2.458108ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:28:18Z" - latency: 2.973765ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:27:18Z" - latency: 2.375505ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:26:18Z" - latency: 2.700929ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:25:18Z" - latency: 2.395027ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:24:18Z" - latency: 3.175448ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:23:18Z" - latency: 2.891886ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:22:18Z" - latency: 2.463295ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:21:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T13:02:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-236-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-236.us-east-2.compute.internal uid: bf0f7649-e941-44b2-a792-d5841d32c8ef resourceVersion: "69697" uid: 848a82b0-8f8b-4fc1-b458-73aa2053e70a spec: sourcePod: network-check-source-6f78d59f99-h2pxh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T13:08:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.081365ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:32:18Z" - latency: 2.329721ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:32:18Z" - latency: 1.257726ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:31:18Z" - latency: 2.297146ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:31:18Z" - latency: 1.168821ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:30:18Z" - latency: 1.833397ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:30:18Z" - latency: 1.159964ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:29:18Z" - latency: 2.036449ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:29:18Z" - latency: 926.349µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:28:18Z" - latency: 2.024704ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:28:18Z" kind: List metadata: resourceVersion: ""