apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T18:05:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-201-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-201.ec2.internal uid: 29dc2444-f0a3-4d1d-9322-c2e5b272f658 resourceVersion: "71441" uid: 77a82ff5-fb2d-4b34-9cd1-e9d7dbf6dea5 spec: sourcePod: network-check-source-7d88cb55d8-7pnpp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T18:12:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.007132ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:54:16Z" - latency: 1.231164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:53:16Z" - latency: 1.630627ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:52:16Z" - latency: 1.253341ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:51:16Z" - latency: 1.141355ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:16Z" - latency: 1.414077ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:16Z" - latency: 1.294335ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:16Z" - latency: 1.410686ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:16Z" - latency: 1.270561ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:16Z" - latency: 1.205912ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:45:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T18:05:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-201-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-201.ec2.internal uid: 29dc2444-f0a3-4d1d-9322-c2e5b272f658 resourceVersion: "70272" uid: 76fe2f72-a408-48a7-bace-e0dfea73e2c8 spec: sourcePod: network-check-source-7d88cb55d8-7pnpp targetEndpoint: af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T18:11:16Z" message: 'load-balancer-api-external: tcp connection to af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.698074ms message: 'load-balancer-api-external: tcp connection to af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:53:16Z" - latency: 7.750543ms message: 'load-balancer-api-external: resolved host name af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:53:16Z" - latency: 3.674939ms message: 'load-balancer-api-external: tcp connection to af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:52:16Z" - latency: 8.482772ms message: 'load-balancer-api-external: resolved host name af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:52:16Z" - latency: 4.200875ms message: 'load-balancer-api-external: tcp connection to af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:51:16Z" - latency: 6.754873ms message: 'load-balancer-api-external: resolved host name af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:51:16Z" - latency: 5.266366ms message: 'load-balancer-api-external: tcp connection to af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:16Z" - latency: 7.410856ms message: 'load-balancer-api-external: resolved host name af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:50:16Z" - latency: 5.110235ms message: 'load-balancer-api-external: tcp connection to af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:16Z" - latency: 7.818591ms message: 'load-balancer-api-external: resolved host name af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:49:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T18:05:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-201-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-201.ec2.internal uid: 29dc2444-f0a3-4d1d-9322-c2e5b272f658 resourceVersion: "70273" uid: 1dbfbbf8-6159-4b83-ae1f-9452a5ad8cc2 spec: sourcePod: network-check-source-7d88cb55d8-7pnpp targetEndpoint: af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T18:11:16Z" message: 'load-balancer-api-internal: tcp connection to af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.41331ms message: 'load-balancer-api-internal: tcp connection to af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:53:16Z" - latency: 7.661387ms message: 'load-balancer-api-internal: resolved host name af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:53:16Z" - latency: 3.920625ms message: 'load-balancer-api-internal: tcp connection to af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:52:16Z" - latency: 8.45696ms message: 'load-balancer-api-internal: resolved host name af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:52:16Z" - latency: 4.908858ms message: 'load-balancer-api-internal: tcp connection to af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:51:16Z" - latency: 6.722716ms message: 'load-balancer-api-internal: resolved host name af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:51:16Z" - latency: 5.257881ms message: 'load-balancer-api-internal: tcp connection to af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:16Z" - latency: 7.388496ms message: 'load-balancer-api-internal: resolved host name af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:50:16Z" - latency: 5.111137ms message: 'load-balancer-api-internal: tcp connection to af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:16Z" - latency: 7.772246ms message: 'load-balancer-api-internal: resolved host name af89a2b0183e54cbc80aceff5bd1b3ef-90c74ba4fb011a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:49:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T18:05:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-201-to-network-check-target-ip-10-0-139-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-201.ec2.internal uid: 29dc2444-f0a3-4d1d-9322-c2e5b272f658 resourceVersion: "71438" uid: db55abbb-85ad-4e33-bdc9-feac1571a040 spec: sourcePod: network-check-source-7d88cb55d8-7pnpp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T18:12:16Z" message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.012454ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:54:16Z" - latency: 1.05706ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:53:16Z" - latency: 1.17232ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:52:16Z" - latency: 1.56193ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:51:16Z" - latency: 1.022569ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:16Z" - latency: 1.145006ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:16Z" - latency: 1.127383ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:16Z" - latency: 1.208829ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:16Z" - latency: 1.06661ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:16Z" - latency: 2.541014ms message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:45:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T18:05:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-201-to-network-check-target-ip-10-0-139-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-201.ec2.internal uid: 29dc2444-f0a3-4d1d-9322-c2e5b272f658 resourceVersion: "71439" uid: 6314a0f6-b28f-4d11-b616-560fe7e3e11c spec: sourcePod: network-check-source-7d88cb55d8-7pnpp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T18:12:16Z" message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.109871ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:54:16Z" - latency: 2.326599ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:53:16Z" - latency: 2.394816ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:52:16Z" - latency: 2.330088ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:51:16Z" - latency: 2.326342ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:16Z" - latency: 2.43084ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:16Z" - latency: 2.357344ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:16Z" - latency: 2.375966ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:16Z" - latency: 2.408967ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:16Z" - latency: 2.459708ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:45:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T18:05:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-201-to-network-check-target-ip-10-0-141-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-201.ec2.internal uid: 29dc2444-f0a3-4d1d-9322-c2e5b272f658 resourceVersion: "71440" uid: 55a6fadf-36ce-4759-822d-096b0511939d spec: sourcePod: network-check-source-7d88cb55d8-7pnpp targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T18:12:16Z" message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.207883ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:54:16Z" - latency: 2.730087ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:53:16Z" - latency: 2.44746ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:52:16Z" - latency: 2.231021ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:51:16Z" - latency: 2.379661ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:16Z" - latency: 2.357556ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:16Z" - latency: 1.979059ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:16Z" - latency: 2.666879ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:16Z" - latency: 2.199109ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:16Z" - latency: 2.954505ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:45:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T18:05:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-201-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-201.ec2.internal uid: 29dc2444-f0a3-4d1d-9322-c2e5b272f658 resourceVersion: "70271" uid: 9cd81a76-ca99-4b47-b4eb-c2728c84e679 spec: sourcePod: network-check-source-7d88cb55d8-7pnpp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T18:11:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.191652ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:53:16Z" - latency: 2.212286ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:53:16Z" - latency: 1.050329ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:52:16Z" - latency: 2.788692ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:52:16Z" - latency: 1.179545ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:51:16Z" - latency: 1.925306ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:51:16Z" - latency: 1.25753ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:16Z" - latency: 1.91768ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:50:16Z" - latency: 1.160082ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:16Z" - latency: 2.222491ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:49:16Z" kind: List metadata: resourceVersion: ""