apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:42:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-180-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-180.us-west-2.compute.internal uid: 95cc2d32-770f-4596-8388-aa371e00c592 resourceVersion: "113532" uid: 690b905c-5281-461f-9185-efdf7267a12d spec: sourcePod: network-check-source-6f78d59f99-xrk8k targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T23:49:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.176275ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:52Z" - latency: 1.324685ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:52Z" - latency: 1.081529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:52Z" - latency: 1.239048ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:49:52Z" - latency: 1.260423ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:48:52Z" - latency: 1.494779ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:47:52Z" - latency: 1.038074ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:46:52Z" - latency: 1.329293ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:45:52Z" - latency: 1.387333ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:44:52Z" - latency: 1.338904ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:43:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:42:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-180-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-180.us-west-2.compute.internal uid: 95cc2d32-770f-4596-8388-aa371e00c592 resourceVersion: "114911" uid: 3eec4b29-0bc1-46f0-9f98-cd7159aec4eb spec: sourcePod: network-check-source-6f78d59f99-xrk8k targetEndpoint: ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T23:48:52Z" message: 'load-balancer-api-external: tcp connection to ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 50.850698ms message: 'load-balancer-api-external: tcp connection to ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:54:52Z" - latency: 7.03432ms message: 'load-balancer-api-external: resolved host name ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:54:52Z" - latency: 64.280382ms message: 'load-balancer-api-external: tcp connection to ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:53:52Z" - latency: 11.483356ms message: 'load-balancer-api-external: resolved host name ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:53:52Z" - latency: 52.726668ms message: 'load-balancer-api-external: tcp connection to ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:52Z" - latency: 8.902416ms message: 'load-balancer-api-external: resolved host name ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:52:52Z" - latency: 55.202655ms message: 'load-balancer-api-external: tcp connection to ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:52Z" - latency: 6.436792ms message: 'load-balancer-api-external: resolved host name ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:51:52Z" - latency: 52.670378ms message: 'load-balancer-api-external: tcp connection to ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:52Z" - latency: 7.647866ms message: 'load-balancer-api-external: resolved host name ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:50:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:42:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-180-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-180.us-west-2.compute.internal uid: 95cc2d32-770f-4596-8388-aa371e00c592 resourceVersion: "114912" uid: dad73d80-710b-4281-aebf-698d824d0b71 spec: sourcePod: network-check-source-6f78d59f99-xrk8k targetEndpoint: ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T23:48:52Z" message: 'load-balancer-api-internal: tcp connection to ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.192297ms message: 'load-balancer-api-internal: tcp connection to ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:54:52Z" - latency: 7.11305ms message: 'load-balancer-api-internal: resolved host name ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:54:52Z" - latency: 63.91824ms message: 'load-balancer-api-internal: tcp connection to ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:53:52Z" - latency: 11.519935ms message: 'load-balancer-api-internal: resolved host name ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:53:52Z" - latency: 52.668561ms message: 'load-balancer-api-internal: tcp connection to ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:52Z" - latency: 8.926339ms message: 'load-balancer-api-internal: resolved host name ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:52:52Z" - latency: 51.987787ms message: 'load-balancer-api-internal: tcp connection to ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:52Z" - latency: 6.384184ms message: 'load-balancer-api-internal: resolved host name ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:51:52Z" - latency: 52.64033ms message: 'load-balancer-api-internal: tcp connection to ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:52Z" - latency: 7.567973ms message: 'load-balancer-api-internal: resolved host name ade377f6ef8974a73ad19fd7b7959d61-5b50151745721f56.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:50:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:42:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-180-to-network-check-target-ip-10-0-131-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-180.us-west-2.compute.internal uid: 95cc2d32-770f-4596-8388-aa371e00c592 resourceVersion: "113531" uid: a971140b-5694-4645-9aa5-7c9912a61122 spec: sourcePod: network-check-source-6f78d59f99-xrk8k targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T23:49:52Z" message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.535606ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:52Z" - latency: 2.434723ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:52Z" - latency: 2.386253ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:52Z" - latency: 2.368062ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:49:52Z" - latency: 2.207236ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:48:52Z" - latency: 2.205649ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:47:52Z" - latency: 2.186287ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:46:52Z" - latency: 2.853704ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:45:52Z" - latency: 2.606616ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:44:52Z" - latency: 2.30811ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:43:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:43:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-180-to-network-check-target-ip-10-0-139-66 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-180.us-west-2.compute.internal uid: 95cc2d32-770f-4596-8388-aa371e00c592 resourceVersion: "113699" uid: 1730bbcf-e48e-4af6-bce4-2fe3fb4a7f28 spec: sourcePod: network-check-source-6f78d59f99-xrk8k targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T23:50:03Z" message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.530868ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:53:03Z" - latency: 2.561584ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:03Z" - latency: 2.615365ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:03Z" - latency: 5.963075ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:03Z" - latency: 5.859352ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:49:03Z" - latency: 3.001316ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:48:03Z" - latency: 2.817806ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:47:03Z" - latency: 2.571155ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:46:03Z" - latency: 9.859877ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:45:03Z" - latency: 2.443814ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:44:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:42:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-180-to-network-check-target-ip-10-0-141-180 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-180.us-west-2.compute.internal uid: 95cc2d32-770f-4596-8388-aa371e00c592 resourceVersion: "113530" uid: ae3735c1-cce4-41a1-a62a-10b124c2d1ec spec: sourcePod: network-check-source-6f78d59f99-xrk8k targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T23:49:52Z" message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.622813ms message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:52Z" - latency: 1.116661ms message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:52Z" - latency: 945.655µs message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:52Z" - latency: 1.406524ms message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:49:52Z" - latency: 1.011674ms message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:48:52Z" - latency: 1.151403ms message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:47:52Z" - latency: 1.094776ms message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:46:52Z" - latency: 1.341704ms message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:45:52Z" - latency: 993.518µs message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:44:52Z" - latency: 1.723289ms message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:43:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:42:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-180-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-180.us-west-2.compute.internal uid: 95cc2d32-770f-4596-8388-aa371e00c592 resourceVersion: "114908" uid: ca02a10a-d2eb-4300-98b4-79addc4fc887 spec: sourcePod: network-check-source-6f78d59f99-xrk8k targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T23:48:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 807.358µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:54:52Z" - latency: 1.98833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:54:52Z" - latency: 843.83µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:53:52Z" - latency: 1.847657ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:53:52Z" - latency: 981.596µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:52Z" - latency: 2.560574ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:52:52Z" - latency: 947.791µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:52Z" - latency: 1.909952ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:51:52Z" - latency: 1.035766ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:52Z" - latency: 2.880144ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:50:52Z" kind: List metadata: resourceVersion: ""