apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T05:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-124-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-124.ec2.internal uid: f0f8a0ce-75bf-4411-a531-c00325258601 resourceVersion: "20661" uid: 51eb19e8-547e-467c-b115-d93ddbc48fb2 spec: sourcePod: network-check-source-7d88cb55d8-s5bjn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T05:37:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 882.963µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:51:17Z" - latency: 852.316µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:50:17Z" - latency: 789.78µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:49:17Z" - latency: 819.273µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:48:17Z" - latency: 1.069291ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:47:17Z" - latency: 852.314µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:46:17Z" - latency: 870.07µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:45:17Z" - latency: 1.146663ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:44:17Z" - latency: 828.802µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:43:17Z" - latency: 821.707µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:42:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T05:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-124-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-124.ec2.internal uid: f0f8a0ce-75bf-4411-a531-c00325258601 resourceVersion: "22196" uid: ecad9e76-431c-42d5-84bc-47c74badbe24 spec: sourcePod: network-check-source-7d88cb55d8-s5bjn targetEndpoint: a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T05:36:17Z" message: 'load-balancer-api-external: tcp connection to a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.889457ms message: 'load-balancer-api-external: tcp connection to a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:54:17Z" - latency: 6.749197ms message: 'load-balancer-api-external: resolved host name a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T05:54:17Z" - latency: 5.347249ms message: 'load-balancer-api-external: tcp connection to a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:53:17Z" - latency: 7.671518ms message: 'load-balancer-api-external: resolved host name a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T05:53:17Z" - latency: 3.507706ms message: 'load-balancer-api-external: tcp connection to a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:52:17Z" - latency: 9.095055ms message: 'load-balancer-api-external: resolved host name a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T05:52:17Z" - latency: 4.915918ms message: 'load-balancer-api-external: tcp connection to a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:51:17Z" - latency: 7.526209ms message: 'load-balancer-api-external: resolved host name a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T05:51:17Z" - latency: 3.259853ms message: 'load-balancer-api-external: tcp connection to a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:50:17Z" - latency: 8.345962ms message: 'load-balancer-api-external: resolved host name a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T05:50:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T05:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-124-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-124.ec2.internal uid: f0f8a0ce-75bf-4411-a531-c00325258601 resourceVersion: "22197" uid: 889cd3fe-5de1-4f8b-9bcc-07ed6bd9f4b1 spec: sourcePod: network-check-source-7d88cb55d8-s5bjn targetEndpoint: a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T05:36:17Z" message: 'load-balancer-api-internal: tcp connection to a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.853006ms message: 'load-balancer-api-internal: tcp connection to a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:54:17Z" - latency: 6.701926ms message: 'load-balancer-api-internal: resolved host name a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T05:54:17Z" - latency: 5.384204ms message: 'load-balancer-api-internal: tcp connection to a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:53:17Z" - latency: 7.633815ms message: 'load-balancer-api-internal: resolved host name a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T05:53:17Z" - latency: 3.457374ms message: 'load-balancer-api-internal: tcp connection to a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:52:17Z" - latency: 9.162912ms message: 'load-balancer-api-internal: resolved host name a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T05:52:17Z" - latency: 4.316223ms message: 'load-balancer-api-internal: tcp connection to a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:51:17Z" - latency: 7.618209ms message: 'load-balancer-api-internal: resolved host name a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T05:51:17Z" - latency: 4.95686ms message: 'load-balancer-api-internal: tcp connection to a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:50:17Z" - latency: 8.429174ms message: 'load-balancer-api-internal: resolved host name a971b1e2c8283445f9cc7a6868fbf1d4-5dadd3b42b6b84d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T05:50:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T05:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-124-to-network-check-target-ip-10-0-137-238 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-124.ec2.internal uid: f0f8a0ce-75bf-4411-a531-c00325258601 resourceVersion: "20658" uid: c2b27bbc-d8da-42bd-9a80-345f413d67e7 spec: sourcePod: network-check-source-7d88cb55d8-s5bjn targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T05:37:17Z" message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.117729ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:51:17Z" - latency: 2.315602ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:50:17Z" - latency: 2.35851ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:49:17Z" - latency: 2.234169ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:48:17Z" - latency: 5.685361ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:47:17Z" - latency: 2.379393ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:46:17Z" - latency: 2.430156ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:45:17Z" - latency: 2.052433ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:44:17Z" - latency: 2.106674ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:43:17Z" - latency: 1.989191ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:42:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T05:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-124-to-network-check-target-ip-10-0-141-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-124.ec2.internal uid: f0f8a0ce-75bf-4411-a531-c00325258601 resourceVersion: "20660" uid: f00fab95-b20b-43f8-89e5-b342813c2f4b spec: sourcePod: network-check-source-7d88cb55d8-s5bjn targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T05:37:17Z" message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.270874ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:51:17Z" - latency: 753.653µs message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:50:17Z" - latency: 1.480115ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:49:17Z" - latency: 1.536802ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:48:17Z" - latency: 909.639µs message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:47:17Z" - latency: 1.296953ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:46:17Z" - latency: 1.495736ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:45:17Z" - latency: 967.339µs message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:44:17Z" - latency: 989.437µs message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:43:17Z" - latency: 790.417µs message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:42:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T05:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-124-to-network-check-target-ip-10-0-142-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-124.ec2.internal uid: f0f8a0ce-75bf-4411-a531-c00325258601 resourceVersion: "20659" uid: 6bdc2385-c116-43a1-b11b-3ce1fe6de9a3 spec: sourcePod: network-check-source-7d88cb55d8-s5bjn targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T05:37:17Z" message: 'network-check-target-ip-10-0-142-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.120843ms message: 'network-check-target-ip-10-0-142-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:51:17Z" - latency: 2.069973ms message: 'network-check-target-ip-10-0-142-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:50:17Z" - latency: 2.135122ms message: 'network-check-target-ip-10-0-142-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:49:17Z" - latency: 1.975802ms message: 'network-check-target-ip-10-0-142-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:48:17Z" - latency: 1.98087ms message: 'network-check-target-ip-10-0-142-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:47:17Z" - latency: 2.008085ms message: 'network-check-target-ip-10-0-142-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:46:17Z" - latency: 2.101726ms message: 'network-check-target-ip-10-0-142-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:45:17Z" - latency: 1.98585ms message: 'network-check-target-ip-10-0-142-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:44:17Z" - latency: 2.226336ms message: 'network-check-target-ip-10-0-142-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:43:17Z" - latency: 2.081324ms message: 'network-check-target-ip-10-0-142-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:42:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T05:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-124-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-124.ec2.internal uid: f0f8a0ce-75bf-4411-a531-c00325258601 resourceVersion: "22195" uid: 124146c7-d6e0-4d66-8873-9ecc090b9239 spec: sourcePod: network-check-source-7d88cb55d8-s5bjn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T05:36:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 965.057µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:54:17Z" - latency: 1.60947ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T05:54:17Z" - latency: 1.072772ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:53:17Z" - latency: 1.740487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T05:53:17Z" - latency: 796.349µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:52:17Z" - latency: 1.555168ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T05:52:17Z" - latency: 1.161295ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:51:17Z" - latency: 1.634085ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T05:51:17Z" - latency: 886.493µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T05:50:17Z" - latency: 1.723728ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T05:50:17Z" kind: List metadata: resourceVersion: ""