apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T06:17:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-93-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-93.us-west-2.compute.internal uid: 0e2a77a2-d81a-4833-98c0-396bdbe1ac72 resourceVersion: "104456" uid: 0f73e61e-5c4e-47f2-8700-1d54dc08c411 spec: sourcePod: network-check-source-6f78d59f99-k9hcs targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T06:24:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.452642ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:20:47Z" - latency: 1.018228ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:19:47Z" - latency: 1.10201ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:18:47Z" - latency: 997.891µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:17:47Z" - latency: 1.645449ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:16:47Z" - latency: 865.463µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:15:47Z" - latency: 1.066654ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:14:47Z" - latency: 997.109µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:13:47Z" - latency: 1.024701ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:12:47Z" - latency: 789.264µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:11:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T06:17:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-93-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-93.us-west-2.compute.internal uid: 0e2a77a2-d81a-4833-98c0-396bdbe1ac72 resourceVersion: "107293" uid: e37dc548-72ce-45c6-bd07-4e749a46f26a spec: sourcePod: network-check-source-6f78d59f99-k9hcs targetEndpoint: af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T06:23:47Z" message: 'load-balancer-api-external: tcp connection to af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 48.913841ms message: 'load-balancer-api-external: tcp connection to af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:23:47Z" - latency: 6.237374ms message: 'load-balancer-api-external: resolved host name af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T07:23:47Z" - latency: 55.941414ms message: 'load-balancer-api-external: tcp connection to af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:22:47Z" - latency: 6.554087ms message: 'load-balancer-api-external: resolved host name af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T07:22:47Z" - latency: 55.465129ms message: 'load-balancer-api-external: tcp connection to af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:21:47Z" - latency: 10.032191ms message: 'load-balancer-api-external: resolved host name af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T07:21:47Z" - latency: 54.93885ms message: 'load-balancer-api-external: tcp connection to af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:20:47Z" - latency: 7.34274ms message: 'load-balancer-api-external: resolved host name af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T07:20:47Z" - latency: 49.242872ms message: 'load-balancer-api-external: tcp connection to af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:19:47Z" - latency: 6.27153ms message: 'load-balancer-api-external: resolved host name af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T07:19:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T06:17:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-93-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-93.us-west-2.compute.internal uid: 0e2a77a2-d81a-4833-98c0-396bdbe1ac72 resourceVersion: "107294" uid: 6c343c04-a43c-455a-be23-111f849b7a00 spec: sourcePod: network-check-source-6f78d59f99-k9hcs targetEndpoint: af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T06:23:47Z" message: 'load-balancer-api-internal: tcp connection to af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.3987ms message: 'load-balancer-api-internal: tcp connection to af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:23:47Z" - latency: 6.325184ms message: 'load-balancer-api-internal: resolved host name af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T07:23:47Z" - latency: 50.845672ms message: 'load-balancer-api-internal: tcp connection to af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:22:47Z" - latency: 6.511573ms message: 'load-balancer-api-internal: resolved host name af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T07:22:47Z" - latency: 56.159722ms message: 'load-balancer-api-internal: tcp connection to af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:21:47Z" - latency: 10.111964ms message: 'load-balancer-api-internal: resolved host name af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T07:21:47Z" - latency: 51.689485ms message: 'load-balancer-api-internal: tcp connection to af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:20:47Z" - latency: 7.385745ms message: 'load-balancer-api-internal: resolved host name af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T07:20:47Z" - latency: 49.038831ms message: 'load-balancer-api-internal: tcp connection to af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:19:47Z" - latency: 6.318626ms message: 'load-balancer-api-internal: resolved host name af4ae981bd91148c598c3a76754e16e4-db7866749802e67b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T07:19:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T06:17:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-93-to-network-check-target-ip-10-0-130-34 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-93.us-west-2.compute.internal uid: 0e2a77a2-d81a-4833-98c0-396bdbe1ac72 resourceVersion: "104454" uid: c2cc41ba-4eab-48fc-bdec-b5b592038df0 spec: sourcePod: network-check-source-6f78d59f99-k9hcs targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T06:24:47Z" message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.993423ms message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:20:47Z" - latency: 2.224296ms message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:19:47Z" - latency: 2.366054ms message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:18:47Z" - latency: 2.560623ms message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:17:47Z" - latency: 2.834893ms message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:16:47Z" - latency: 2.294054ms message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:15:47Z" - latency: 2.354457ms message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:14:47Z" - latency: 2.739027ms message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:13:47Z" - latency: 2.331026ms message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:12:47Z" - latency: 1.957934ms message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:11:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T06:17:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-93-to-network-check-target-ip-10-0-130-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-93.us-west-2.compute.internal uid: 0e2a77a2-d81a-4833-98c0-396bdbe1ac72 resourceVersion: "104453" uid: 64a65cbc-4181-4958-9dfc-6a60e30228ce spec: sourcePod: network-check-source-6f78d59f99-k9hcs targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T06:24:47Z" message: 'network-check-target-ip-10-0-130-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.094148ms message: 'network-check-target-ip-10-0-130-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:20:47Z" - latency: 1.145686ms message: 'network-check-target-ip-10-0-130-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:19:47Z" - latency: 986.373µs message: 'network-check-target-ip-10-0-130-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:18:47Z" - latency: 946.937µs message: 'network-check-target-ip-10-0-130-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:17:47Z" - latency: 1.153044ms message: 'network-check-target-ip-10-0-130-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:16:47Z" - latency: 829.226µs message: 'network-check-target-ip-10-0-130-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:15:47Z" - latency: 1.006276ms message: 'network-check-target-ip-10-0-130-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:14:47Z" - latency: 894.133µs message: 'network-check-target-ip-10-0-130-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:13:47Z" - latency: 1.127736ms message: 'network-check-target-ip-10-0-130-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:12:47Z" - latency: 760.52µs message: 'network-check-target-ip-10-0-130-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:11:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T06:17:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-93-to-network-check-target-ip-10-0-142-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-93.us-west-2.compute.internal uid: 0e2a77a2-d81a-4833-98c0-396bdbe1ac72 resourceVersion: "104664" uid: e91b9bb1-27ea-4574-921b-4a944e347731 spec: sourcePod: network-check-source-6f78d59f99-k9hcs targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T06:24:55Z" message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.582741ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:20:55Z" - latency: 1.973948ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:19:55Z" - latency: 874.452µs message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:18:55Z" - latency: 1.943576ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:17:55Z" - latency: 2.258046ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:16:55Z" - latency: 1.824539ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:15:55Z" - latency: 2.187291ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:14:55Z" - latency: 1.777221ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:13:55Z" - latency: 2.706525ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:12:55Z" - latency: 617.736µs message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:11:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T06:17:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-93-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-93.us-west-2.compute.internal uid: 0e2a77a2-d81a-4833-98c0-396bdbe1ac72 resourceVersion: "107289" uid: 37beb641-6736-45ee-ae8c-cf20311ef7f2 spec: sourcePod: network-check-source-6f78d59f99-k9hcs targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T06:23:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 885.287µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:23:47Z" - latency: 1.66773ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T07:23:47Z" - latency: 1.074373ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:22:47Z" - latency: 1.569171ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T07:22:47Z" - latency: 2.013054ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:21:47Z" - latency: 1.641326ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T07:21:47Z" - latency: 1.027863ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:20:47Z" - latency: 2.252006ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T07:20:47Z" - latency: 882.924µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T07:19:47Z" - latency: 1.587927ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T07:19:47Z" kind: List metadata: resourceVersion: ""