apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:03:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-108-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-108.ec2.internal uid: 739338dc-0240-4d25-9a27-4d3cc6dbf5c2 resourceVersion: "61025" uid: a0be21f9-4289-4544-8a2f-ca223fc944a1 spec: sourcePod: network-check-source-869dcfcdcd-kpxf9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T19:10:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 684.992µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:45:14Z" - latency: 876.941µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:14Z" - latency: 1.060176ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:14Z" - latency: 932.319µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:14Z" - latency: 1.345698ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:14Z" - latency: 1.083697ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:14Z" - latency: 1.328531ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:14Z" - latency: 832.13µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:14Z" - latency: 907.197µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:37:14Z" - latency: 1.162874ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:36:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:03:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-108-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-108.ec2.internal uid: 739338dc-0240-4d25-9a27-4d3cc6dbf5c2 resourceVersion: "61029" uid: 420eff83-ed00-4a8f-9ed7-1b3e8192be12 spec: sourcePod: network-check-source-869dcfcdcd-kpxf9 targetEndpoint: a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T19:09:14Z" message: 'load-balancer-api-external: tcp connection to a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.871644ms message: 'load-balancer-api-external: tcp connection to a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:45:14Z" - latency: 8.694571ms message: 'load-balancer-api-external: resolved host name a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:45:14Z" - latency: 3.469252ms message: 'load-balancer-api-external: tcp connection to a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:14Z" - latency: 6.121949ms message: 'load-balancer-api-external: resolved host name a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:44:14Z" - latency: 4.86743ms message: 'load-balancer-api-external: tcp connection to a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:14Z" - latency: 8.273742ms message: 'load-balancer-api-external: resolved host name a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:43:14Z" - latency: 4.662746ms message: 'load-balancer-api-external: tcp connection to a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:14Z" - latency: 6.657505ms message: 'load-balancer-api-external: resolved host name a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:42:14Z" - latency: 5.041137ms message: 'load-balancer-api-external: tcp connection to a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:14Z" - latency: 7.996985ms message: 'load-balancer-api-external: resolved host name a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:41:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:03:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-108-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-108.ec2.internal uid: 739338dc-0240-4d25-9a27-4d3cc6dbf5c2 resourceVersion: "61028" uid: f116f6f1-f7ff-4fe4-9aa0-b0409fbb7346 spec: sourcePod: network-check-source-869dcfcdcd-kpxf9 targetEndpoint: a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T19:09:14Z" message: 'load-balancer-api-internal: tcp connection to a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.673915ms message: 'load-balancer-api-internal: tcp connection to a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:45:14Z" - latency: 8.62082ms message: 'load-balancer-api-internal: resolved host name a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:45:14Z" - latency: 3.169152ms message: 'load-balancer-api-internal: tcp connection to a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:14Z" - latency: 6.038531ms message: 'load-balancer-api-internal: resolved host name a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:44:14Z" - latency: 3.34452ms message: 'load-balancer-api-internal: tcp connection to a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:14Z" - latency: 8.192202ms message: 'load-balancer-api-internal: resolved host name a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:43:14Z" - latency: 4.848817ms message: 'load-balancer-api-internal: tcp connection to a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:14Z" - latency: 6.605215ms message: 'load-balancer-api-internal: resolved host name a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:42:14Z" - latency: 5.011802ms message: 'load-balancer-api-internal: tcp connection to a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:14Z" - latency: 7.926884ms message: 'load-balancer-api-internal: resolved host name a052cc670c6a34db69075a6ac5030747-d0e88c41885de98a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:41:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:03:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-108-to-network-check-target-ip-10-0-135-67 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-108.ec2.internal uid: 739338dc-0240-4d25-9a27-4d3cc6dbf5c2 resourceVersion: "61023" uid: 3e8d913e-f9b3-4411-ab08-5b45c22f29d5 spec: sourcePod: network-check-source-869dcfcdcd-kpxf9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:10:14Z" message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.086385ms message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:45:14Z" - latency: 2.323877ms message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:14Z" - latency: 2.240181ms message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:14Z" - latency: 1.855122ms message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:14Z" - latency: 2.13224ms message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:14Z" - latency: 1.913229ms message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:14Z" - latency: 2.54499ms message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:14Z" - latency: 1.926239ms message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:14Z" - latency: 2.205388ms message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:37:14Z" - latency: 2.149876ms message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:36:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:03:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-108-to-network-check-target-ip-10-0-138-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-108.ec2.internal uid: 739338dc-0240-4d25-9a27-4d3cc6dbf5c2 resourceVersion: "61022" uid: 5aceb590-80f3-4ab9-8327-f6516641ce15 spec: sourcePod: network-check-source-869dcfcdcd-kpxf9 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:10:14Z" message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.682365ms message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:45:14Z" - latency: 1.871603ms message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:14Z" - latency: 1.890272ms message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:14Z" - latency: 1.777595ms message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:14Z" - latency: 1.569869ms message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:14Z" - latency: 1.347808ms message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:14Z" - latency: 1.720238ms message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:14Z" - latency: 1.847401ms message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:14Z" - latency: 2.09798ms message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:37:14Z" - latency: 1.421676ms message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:36:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:03:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-108-to-network-check-target-ip-10-0-139-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-108.ec2.internal uid: 739338dc-0240-4d25-9a27-4d3cc6dbf5c2 resourceVersion: "61020" uid: bb56a871-acf1-4a1a-88a6-d2ead7f81c28 spec: sourcePod: network-check-source-869dcfcdcd-kpxf9 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:10:14Z" message: 'network-check-target-ip-10-0-139-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 775.904µs message: 'network-check-target-ip-10-0-139-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:45:14Z" - latency: 977.134µs message: 'network-check-target-ip-10-0-139-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:14Z" - latency: 844.686µs message: 'network-check-target-ip-10-0-139-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:14Z" - latency: 1.048806ms message: 'network-check-target-ip-10-0-139-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:14Z" - latency: 1.439444ms message: 'network-check-target-ip-10-0-139-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:14Z" - latency: 802.61µs message: 'network-check-target-ip-10-0-139-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:14Z" - latency: 997.184µs message: 'network-check-target-ip-10-0-139-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:14Z" - latency: 1.159596ms message: 'network-check-target-ip-10-0-139-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:14Z" - latency: 1.022482ms message: 'network-check-target-ip-10-0-139-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:37:14Z" - latency: 1.397797ms message: 'network-check-target-ip-10-0-139-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:36:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:03:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-108-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-108.ec2.internal uid: 739338dc-0240-4d25-9a27-4d3cc6dbf5c2 resourceVersion: "61024" uid: 1bfd7508-dbea-4f5e-a259-0e4325159419 spec: sourcePod: network-check-source-869dcfcdcd-kpxf9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T19:09:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 962.164µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:45:14Z" - latency: 2.012925ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:45:14Z" - latency: 873.209µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:14Z" - latency: 1.877155ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:44:14Z" - latency: 883.282µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:14Z" - latency: 1.488973ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:43:14Z" - latency: 906.926µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:14Z" - latency: 1.727596ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:42:14Z" - latency: 1.013199ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:14Z" - latency: 1.663651ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:41:14Z" kind: List metadata: resourceVersion: ""