apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T03:05:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-120-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-120.us-west-1.compute.internal uid: 8f9585d6-3b6f-4815-88a6-2900b9d03d3b resourceVersion: "159603" uid: 5279fec9-37af-4ab9-8b38-8e067014998f spec: sourcePod: network-check-source-6f78d59f99-tjzsm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T03:12:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.201534ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:50:29Z" - latency: 1.98928ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:49:29Z" - latency: 1.265412ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:48:29Z" - latency: 1.172033ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:47:29Z" - latency: 971.872µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:46:29Z" - latency: 1.141554ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:45:29Z" - latency: 959.627µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:44:29Z" - latency: 1.940801ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:43:29Z" - latency: 1.278091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:42:29Z" - latency: 895.998µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:41:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T03:05:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-120-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-120.us-west-1.compute.internal uid: 8f9585d6-3b6f-4815-88a6-2900b9d03d3b resourceVersion: "161691" uid: 89a54ac5-1c5e-451c-9ea5-93c2034a0689 spec: sourcePod: network-check-source-6f78d59f99-tjzsm targetEndpoint: a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T03:11:29Z" message: 'load-balancer-api-external: tcp connection to a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.965082ms message: 'load-balancer-api-external: tcp connection to a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:53:29Z" - latency: 6.296954ms message: 'load-balancer-api-external: resolved host name a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T04:53:29Z" - latency: 54.965183ms message: 'load-balancer-api-external: tcp connection to a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:52:29Z" - latency: 6.142927ms message: 'load-balancer-api-external: resolved host name a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T04:52:29Z" - latency: 54.169967ms message: 'load-balancer-api-external: tcp connection to a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:51:29Z" - latency: 6.742004ms message: 'load-balancer-api-external: resolved host name a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T04:51:29Z" - latency: 54.161239ms message: 'load-balancer-api-external: tcp connection to a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:50:29Z" - latency: 6.28061ms message: 'load-balancer-api-external: resolved host name a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T04:50:29Z" - latency: 54.423622ms message: 'load-balancer-api-external: tcp connection to a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:49:29Z" - latency: 10.071445ms message: 'load-balancer-api-external: resolved host name a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T04:49:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T03:05:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-120-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-120.us-west-1.compute.internal uid: 8f9585d6-3b6f-4815-88a6-2900b9d03d3b resourceVersion: "161690" uid: 2c669fa3-bae0-4700-aa72-61004dc7c608 spec: sourcePod: network-check-source-6f78d59f99-tjzsm targetEndpoint: a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T03:11:29Z" message: 'load-balancer-api-internal: tcp connection to a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.945076ms message: 'load-balancer-api-internal: tcp connection to a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:53:29Z" - latency: 6.385168ms message: 'load-balancer-api-internal: resolved host name a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T04:53:29Z" - latency: 54.523686ms message: 'load-balancer-api-internal: tcp connection to a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:52:29Z" - latency: 6.207717ms message: 'load-balancer-api-internal: resolved host name a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T04:52:29Z" - latency: 54.238092ms message: 'load-balancer-api-internal: tcp connection to a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:51:29Z" - latency: 6.838606ms message: 'load-balancer-api-internal: resolved host name a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T04:51:29Z" - latency: 54.191429ms message: 'load-balancer-api-internal: tcp connection to a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:50:29Z" - latency: 6.26813ms message: 'load-balancer-api-internal: resolved host name a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T04:50:29Z" - latency: 53.698842ms message: 'load-balancer-api-internal: tcp connection to a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:49:29Z" - latency: 10.380916ms message: 'load-balancer-api-internal: resolved host name a058e290254ff44d893eba1331bf9de6-33cafa47f6ec0d31.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T04:49:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T03:05:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-120-to-network-check-target-ip-10-0-136-7 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-120.us-west-1.compute.internal uid: 8f9585d6-3b6f-4815-88a6-2900b9d03d3b resourceVersion: "159602" uid: a4d16230-ad57-4847-8941-f8d6a1f71ea1 spec: sourcePod: network-check-source-6f78d59f99-tjzsm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T03:12:29Z" message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.567322ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:50:29Z" - latency: 3.148566ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:49:29Z" - latency: 2.598905ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:48:29Z" - latency: 2.609324ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:47:29Z" - latency: 2.625169ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:46:29Z" - latency: 3.095963ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:45:29Z" - latency: 2.313454ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:44:29Z" - latency: 2.536545ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:43:29Z" - latency: 2.830312ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:42:29Z" - latency: 2.205234ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:41:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T03:05:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-120-to-network-check-target-ip-10-0-138-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-120.us-west-1.compute.internal uid: 8f9585d6-3b6f-4815-88a6-2900b9d03d3b resourceVersion: "159601" uid: 32242427-f0d4-4394-9e95-eae11c28192e spec: sourcePod: network-check-source-6f78d59f99-tjzsm targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T03:12:29Z" message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.174282ms message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:50:29Z" - latency: 4.713862ms message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:49:29Z" - latency: 2.420591ms message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:48:29Z" - latency: 2.476661ms message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:47:29Z" - latency: 2.451751ms message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:46:29Z" - latency: 2.422578ms message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:45:29Z" - latency: 2.151458ms message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:44:29Z" - latency: 2.432671ms message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:43:29Z" - latency: 2.366378ms message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:42:29Z" - latency: 2.032464ms message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:41:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T03:05:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-120-to-network-check-target-ip-10-0-138-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-120.us-west-1.compute.internal uid: 8f9585d6-3b6f-4815-88a6-2900b9d03d3b resourceVersion: "159600" uid: 08d9b90b-174b-43a4-975b-afeeea8a37df spec: sourcePod: network-check-source-6f78d59f99-tjzsm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T03:12:29Z" message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.021644ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:50:29Z" - latency: 3.315067ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:49:29Z" - latency: 1.605594ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:48:29Z" - latency: 1.337641ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:47:29Z" - latency: 988.565µs message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:46:29Z" - latency: 1.078687ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:45:29Z" - latency: 1.39364ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:44:29Z" - latency: 1.101063ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:43:29Z" - latency: 1.532532ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:42:29Z" - latency: 807.489µs message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:41:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T03:05:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-120-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-120.us-west-1.compute.internal uid: 8f9585d6-3b6f-4815-88a6-2900b9d03d3b resourceVersion: "161689" uid: ee4aad6c-500a-49d3-9ba6-603ff35af51f spec: sourcePod: network-check-source-6f78d59f99-tjzsm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T03:11:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.337938ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:53:29Z" - latency: 1.681694ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T04:53:29Z" - latency: 793.874µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:52:29Z" - latency: 1.825073ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T04:52:29Z" - latency: 922.142µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:51:29Z" - latency: 1.758045ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T04:51:29Z" - latency: 956.172µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:50:29Z" - latency: 1.844124ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T04:50:29Z" - latency: 1.419375ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T04:49:29Z" - latency: 3.734656ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T04:49:29Z" kind: List metadata: resourceVersion: ""