apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T08:42:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-14-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-14.us-west-1.compute.internal uid: b5d5b6ea-a8a8-4c95-9c71-3edbf1b4ce4b resourceVersion: "153039" uid: f1cb1937-5be9-437a-b780-58dd58f5bf7d spec: sourcePod: network-check-source-6f78d59f99-kvwlg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T08:49:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 940.134µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:27:31Z" - latency: 1.684577ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:26:31Z" - latency: 1.399683ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:25:31Z" - latency: 957.38µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:24:31Z" - latency: 1.282441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:23:31Z" - latency: 1.118381ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:22:31Z" - latency: 953.815µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:21:31Z" - latency: 1.286104ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:20:31Z" - latency: 1.320765ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:19:31Z" - latency: 1.290262ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:18:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T08:42:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-14-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-14.us-west-1.compute.internal uid: b5d5b6ea-a8a8-4c95-9c71-3edbf1b4ce4b resourceVersion: "155430" uid: 0ff67897-3911-44f9-b77b-e21727e2c92a spec: sourcePod: network-check-source-6f78d59f99-kvwlg targetEndpoint: aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T08:48:31Z" message: 'load-balancer-api-external: tcp connection to aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.137556ms message: 'load-balancer-api-external: tcp connection to aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:30:31Z" - latency: 6.916606ms message: 'load-balancer-api-external: resolved host name aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T10:30:31Z" - latency: 54.506535ms message: 'load-balancer-api-external: tcp connection to aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:29:31Z" - latency: 6.716074ms message: 'load-balancer-api-external: resolved host name aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T10:29:31Z" - latency: 53.726096ms message: 'load-balancer-api-external: tcp connection to aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:28:31Z" - latency: 6.119802ms message: 'load-balancer-api-external: resolved host name aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T10:28:31Z" - latency: 53.353273ms message: 'load-balancer-api-external: tcp connection to aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:27:31Z" - latency: 6.808991ms message: 'load-balancer-api-external: resolved host name aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T10:27:31Z" - latency: 54.896826ms message: 'load-balancer-api-external: tcp connection to aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:26:31Z" - latency: 10.490987ms message: 'load-balancer-api-external: resolved host name aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T10:26:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T08:42:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-14-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-14.us-west-1.compute.internal uid: b5d5b6ea-a8a8-4c95-9c71-3edbf1b4ce4b resourceVersion: "155429" uid: 999398eb-4423-40c3-be20-dd19415289b0 spec: sourcePod: network-check-source-6f78d59f99-kvwlg targetEndpoint: aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T08:48:31Z" message: 'load-balancer-api-internal: tcp connection to aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.579082ms message: 'load-balancer-api-internal: tcp connection to aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:30:31Z" - latency: 6.889013ms message: 'load-balancer-api-internal: resolved host name aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T10:30:31Z" - latency: 54.462134ms message: 'load-balancer-api-internal: tcp connection to aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:29:31Z" - latency: 6.76604ms message: 'load-balancer-api-internal: resolved host name aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T10:29:31Z" - latency: 53.756787ms message: 'load-balancer-api-internal: tcp connection to aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:28:31Z" - latency: 6.08483ms message: 'load-balancer-api-internal: resolved host name aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T10:28:31Z" - latency: 53.840132ms message: 'load-balancer-api-internal: tcp connection to aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:27:31Z" - latency: 6.777997ms message: 'load-balancer-api-internal: resolved host name aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T10:27:31Z" - latency: 53.895174ms message: 'load-balancer-api-internal: tcp connection to aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:26:31Z" - latency: 10.570288ms message: 'load-balancer-api-internal: resolved host name aaf99b2950bda4e3eb23748958ae1964-ce6ebf1c3713135a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T10:26:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T08:42:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-14-to-network-check-target-ip-10-0-131-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-14.us-west-1.compute.internal uid: b5d5b6ea-a8a8-4c95-9c71-3edbf1b4ce4b resourceVersion: "153038" uid: da9fb899-7224-4da3-a949-22a7822dbcce spec: sourcePod: network-check-source-6f78d59f99-kvwlg targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T08:49:31Z" message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.627407ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:27:31Z" - latency: 2.425513ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:26:31Z" - latency: 2.245447ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:25:31Z" - latency: 1.98709ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:24:31Z" - latency: 2.003058ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:23:31Z" - latency: 2.646884ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:22:31Z" - latency: 2.216347ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:21:31Z" - latency: 2.346664ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:20:31Z" - latency: 2.398578ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:19:31Z" - latency: 2.222623ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:18:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T08:42:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-14-to-network-check-target-ip-10-0-131-14 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-14.us-west-1.compute.internal uid: b5d5b6ea-a8a8-4c95-9c71-3edbf1b4ce4b resourceVersion: "153036" uid: 164bb7ee-2e1b-4755-9792-e1c3f2b625b9 spec: sourcePod: network-check-source-6f78d59f99-kvwlg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T08:49:31Z" message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.476511ms message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:27:31Z" - latency: 1.498485ms message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:26:31Z" - latency: 1.031379ms message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:25:31Z" - latency: 964.49µs message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:24:31Z" - latency: 957.649µs message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:23:31Z" - latency: 1.24632ms message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:22:31Z" - latency: 1.015249ms message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:21:31Z" - latency: 1.297502ms message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:20:31Z" - latency: 1.026545ms message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:19:31Z" - latency: 935.947µs message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:18:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T08:42:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-14-to-network-check-target-ip-10-0-139-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-14.us-west-1.compute.internal uid: b5d5b6ea-a8a8-4c95-9c71-3edbf1b4ce4b resourceVersion: "153037" uid: 90367e53-0ec0-4989-a5e4-c801b722737a spec: sourcePod: network-check-source-6f78d59f99-kvwlg targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T08:49:31Z" message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.921736ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:27:31Z" - latency: 2.132237ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:26:31Z" - latency: 2.006136ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:25:31Z" - latency: 1.990466ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:24:31Z" - latency: 2.158009ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:23:31Z" - latency: 2.243863ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:22:31Z" - latency: 1.962791ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:21:31Z" - latency: 2.201228ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:20:31Z" - latency: 2.198222ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:19:31Z" - latency: 2.051169ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:18:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T08:42:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-14-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-14.us-west-1.compute.internal uid: b5d5b6ea-a8a8-4c95-9c71-3edbf1b4ce4b resourceVersion: "155428" uid: a31ad63f-9dc8-4ef9-8da5-b96d20e603e3 spec: sourcePod: network-check-source-6f78d59f99-kvwlg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T08:48:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.024716ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:30:31Z" - latency: 2.125577ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T10:30:31Z" - latency: 1.035579ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:29:31Z" - latency: 2.012703ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T10:29:31Z" - latency: 890.58µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:28:31Z" - latency: 1.725812ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T10:28:31Z" - latency: 1.407795ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:27:31Z" - latency: 1.997114ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T10:27:31Z" - latency: 972.607µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T10:26:31Z" - latency: 2.867843ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T10:26:31Z" kind: List metadata: resourceVersion: ""