apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:34:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-33-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-33.us-west-1.compute.internal uid: 20c68377-cb5e-4031-81b7-7d3fc102f0a3 resourceVersion: "101676" uid: c6cf82d0-5dac-4cc0-b34d-4cdc76e15224 spec: sourcePod: network-check-source-6f78d59f99-mvlvw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T01:41:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.604499ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:37:24Z" - latency: 1.323055ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:36:24Z" - latency: 1.096862ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:35:24Z" - latency: 1.212159ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:34:24Z" - latency: 1.395274ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:33:24Z" - latency: 1.205343ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:32:24Z" - latency: 1.311965ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:31:24Z" - latency: 1.268996ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:30:24Z" - latency: 1.079573ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:29:24Z" - latency: 1.463802ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:28:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:34:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-33-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-33.us-west-1.compute.internal uid: 20c68377-cb5e-4031-81b7-7d3fc102f0a3 resourceVersion: "103928" uid: bb669816-ffc8-43b6-9fb9-06ca0dc2ec25 spec: sourcePod: network-check-source-6f78d59f99-mvlvw targetEndpoint: a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T01:40:24Z" message: 'load-balancer-api-external: tcp connection to a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.17569ms message: 'load-balancer-api-external: tcp connection to a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:40:24Z" - latency: 7.259197ms message: 'load-balancer-api-external: resolved host name a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:40:24Z" - latency: 53.450425ms message: 'load-balancer-api-external: tcp connection to a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:39:24Z" - latency: 6.881038ms message: 'load-balancer-api-external: resolved host name a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:39:24Z" - latency: 53.500639ms message: 'load-balancer-api-external: tcp connection to a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:38:24Z" - latency: 6.552834ms message: 'load-balancer-api-external: resolved host name a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:38:24Z" - latency: 54.363216ms message: 'load-balancer-api-external: tcp connection to a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:37:24Z" - latency: 8.575837ms message: 'load-balancer-api-external: resolved host name a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:37:24Z" - latency: 54.014372ms message: 'load-balancer-api-external: tcp connection to a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:36:24Z" - latency: 6.580222ms message: 'load-balancer-api-external: resolved host name a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:36:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:34:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-33-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-33.us-west-1.compute.internal uid: 20c68377-cb5e-4031-81b7-7d3fc102f0a3 resourceVersion: "103927" uid: a8046a53-772c-49be-af06-40951ce0a7da spec: sourcePod: network-check-source-6f78d59f99-mvlvw targetEndpoint: a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T01:40:24Z" message: 'load-balancer-api-internal: tcp connection to a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.132938ms message: 'load-balancer-api-internal: tcp connection to a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:40:24Z" - latency: 7.346006ms message: 'load-balancer-api-internal: resolved host name a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:40:24Z" - latency: 53.501218ms message: 'load-balancer-api-internal: tcp connection to a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:39:24Z" - latency: 6.821631ms message: 'load-balancer-api-internal: resolved host name a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:39:24Z" - latency: 53.484414ms message: 'load-balancer-api-internal: tcp connection to a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:38:24Z" - latency: 6.65807ms message: 'load-balancer-api-internal: resolved host name a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:38:24Z" - latency: 54.323597ms message: 'load-balancer-api-internal: tcp connection to a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:37:24Z" - latency: 8.548776ms message: 'load-balancer-api-internal: resolved host name a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:37:24Z" - latency: 54.817958ms message: 'load-balancer-api-internal: tcp connection to a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:36:24Z" - latency: 6.543488ms message: 'load-balancer-api-internal: resolved host name a86811a309f80445ca4534cfcca7e946-0363337bf0817064.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:36:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:34:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-33-to-network-check-target-ip-10-0-135-33 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-33.us-west-1.compute.internal uid: 20c68377-cb5e-4031-81b7-7d3fc102f0a3 resourceVersion: "101673" uid: 2d104aa8-23ce-4bad-98b8-bc66f9312708 spec: sourcePod: network-check-source-6f78d59f99-mvlvw targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T01:41:24Z" message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.120357ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:37:24Z" - latency: 1.143464ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:36:24Z" - latency: 1.250745ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:35:24Z" - latency: 1.594913ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:34:24Z" - latency: 1.222086ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:33:24Z" - latency: 1.283578ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:32:24Z" - latency: 1.301817ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:31:24Z" - latency: 1.539214ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:30:24Z" - latency: 1.08085ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:29:24Z" - latency: 1.131657ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:28:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:34:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-33-to-network-check-target-ip-10-0-138-75 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-33.us-west-1.compute.internal uid: 20c68377-cb5e-4031-81b7-7d3fc102f0a3 resourceVersion: "101674" uid: 82f6b3b5-6fb0-48b8-a4dd-c9292721e794 spec: sourcePod: network-check-source-6f78d59f99-mvlvw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T01:41:24Z" message: 'network-check-target-ip-10-0-138-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.32063ms message: 'network-check-target-ip-10-0-138-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:37:24Z" - latency: 2.484744ms message: 'network-check-target-ip-10-0-138-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:36:24Z" - latency: 2.456045ms message: 'network-check-target-ip-10-0-138-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:35:24Z" - latency: 2.661045ms message: 'network-check-target-ip-10-0-138-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:34:24Z" - latency: 2.460052ms message: 'network-check-target-ip-10-0-138-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:33:24Z" - latency: 2.513558ms message: 'network-check-target-ip-10-0-138-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:32:24Z" - latency: 2.793632ms message: 'network-check-target-ip-10-0-138-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:31:24Z" - latency: 2.465648ms message: 'network-check-target-ip-10-0-138-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:30:24Z" - latency: 2.790379ms message: 'network-check-target-ip-10-0-138-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:29:24Z" - latency: 2.600022ms message: 'network-check-target-ip-10-0-138-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:28:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:34:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-33-to-network-check-target-ip-10-0-141-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-33.us-west-1.compute.internal uid: 20c68377-cb5e-4031-81b7-7d3fc102f0a3 resourceVersion: "101675" uid: 3c3ab076-dde3-4c1c-b4e7-9fa034f3b250 spec: sourcePod: network-check-source-6f78d59f99-mvlvw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T01:41:24Z" message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.674509ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:37:24Z" - latency: 2.813774ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:36:24Z" - latency: 2.242189ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:35:24Z" - latency: 2.754653ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:34:24Z" - latency: 2.304192ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:33:24Z" - latency: 2.834763ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:32:24Z" - latency: 2.243876ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:31:24Z" - latency: 2.287842ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:30:24Z" - latency: 2.835992ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:29:24Z" - latency: 2.383934ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:28:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:34:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-33-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-33.us-west-1.compute.internal uid: 20c68377-cb5e-4031-81b7-7d3fc102f0a3 resourceVersion: "103925" uid: 41828893-7d4d-4812-90dc-6e70678ce49d spec: sourcePod: network-check-source-6f78d59f99-mvlvw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T01:40:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.504934ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:40:24Z" - latency: 2.067422ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:40:24Z" - latency: 1.003734ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:39:24Z" - latency: 2.210823ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:39:24Z" - latency: 907.763µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:38:24Z" - latency: 1.953382ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:38:24Z" - latency: 963.646µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:37:24Z" - latency: 2.030685ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:37:24Z" - latency: 901.977µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:36:24Z" - latency: 2.094945ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:36:24Z" kind: List metadata: resourceVersion: ""