apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T16:31:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-98-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-98.ec2.internal uid: 452a8069-9c81-4880-bd5d-c57eef9eea33 resourceVersion: "62328" uid: 3c835615-0bef-4f23-901f-7f4fdeaf57d9 spec: sourcePod: network-check-source-7bc5b6bf85-lxfsf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T16:38:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.141246ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:13:08Z" - latency: 1.142192ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:12:08Z" - latency: 1.048806ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:11:08Z" - latency: 1.063114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:10:08Z" - latency: 966.975µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:09:08Z" - latency: 1.2673ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:08:08Z" - latency: 1.119697ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:07:08Z" - latency: 1.251479ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:06:08Z" - latency: 1.232806ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:05:08Z" - latency: 841.109µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:04:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T16:31:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-98-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-98.ec2.internal uid: 452a8069-9c81-4880-bd5d-c57eef9eea33 resourceVersion: "62330" uid: 8ec1d134-ec3a-46d9-8380-1e663d8b39b4 spec: sourcePod: network-check-source-7bc5b6bf85-lxfsf targetEndpoint: a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T16:37:08Z" message: 'load-balancer-api-external: tcp connection to a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.473221ms message: 'load-balancer-api-external: tcp connection to a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:13:08Z" - latency: 15.04456ms message: 'load-balancer-api-external: resolved host name a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:13:08Z" - latency: 6.962124ms message: 'load-balancer-api-external: tcp connection to a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:12:08Z" - latency: 6.851069ms message: 'load-balancer-api-external: resolved host name a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:12:08Z" - latency: 5.50223ms message: 'load-balancer-api-external: tcp connection to a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:11:08Z" - latency: 7.147771ms message: 'load-balancer-api-external: resolved host name a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:11:08Z" - latency: 5.986854ms message: 'load-balancer-api-external: tcp connection to a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:10:08Z" - latency: 6.984789ms message: 'load-balancer-api-external: resolved host name a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:10:08Z" - latency: 3.892956ms message: 'load-balancer-api-external: tcp connection to a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:09:08Z" - latency: 10.089181ms message: 'load-balancer-api-external: resolved host name a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:09:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T16:31:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-98-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-98.ec2.internal uid: 452a8069-9c81-4880-bd5d-c57eef9eea33 resourceVersion: "62329" uid: e7a2ee25-cf85-452b-b437-79e0b2a7c00d spec: sourcePod: network-check-source-7bc5b6bf85-lxfsf targetEndpoint: a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T16:37:08Z" message: 'load-balancer-api-internal: tcp connection to a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.519788ms message: 'load-balancer-api-internal: tcp connection to a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:13:08Z" - latency: 15.097504ms message: 'load-balancer-api-internal: resolved host name a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:13:08Z" - latency: 4.039584ms message: 'load-balancer-api-internal: tcp connection to a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:12:08Z" - latency: 6.900657ms message: 'load-balancer-api-internal: resolved host name a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:12:08Z" - latency: 5.492933ms message: 'load-balancer-api-internal: tcp connection to a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:11:08Z" - latency: 7.223971ms message: 'load-balancer-api-internal: resolved host name a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:11:08Z" - latency: 4.622529ms message: 'load-balancer-api-internal: tcp connection to a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:10:08Z" - latency: 7.039075ms message: 'load-balancer-api-internal: resolved host name a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:10:08Z" - latency: 4.358362ms message: 'load-balancer-api-internal: tcp connection to a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:09:08Z" - latency: 10.204944ms message: 'load-balancer-api-internal: resolved host name a6b18fb07c5bf4cb3b39f7b07632c1b9-7b0e83d4e3fe954d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:09:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T16:31:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-98-to-network-check-target-ip-10-0-129-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-98.ec2.internal uid: 452a8069-9c81-4880-bd5d-c57eef9eea33 resourceVersion: "62324" uid: 591be423-d955-45e1-806c-270afeaf471e spec: sourcePod: network-check-source-7bc5b6bf85-lxfsf targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T16:38:08Z" message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 953.738µs message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:13:08Z" - latency: 771.058µs message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:12:08Z" - latency: 1.395542ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:11:08Z" - latency: 1.214513ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:10:08Z" - latency: 1.035946ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:09:08Z" - latency: 1.565867ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:08:08Z" - latency: 1.695064ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:07:08Z" - latency: 1.608206ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:06:08Z" - latency: 956.857µs message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:05:08Z" - latency: 898.097µs message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:04:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T16:31:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-98-to-network-check-target-ip-10-0-135-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-98.ec2.internal uid: 452a8069-9c81-4880-bd5d-c57eef9eea33 resourceVersion: "62327" uid: 964fea1d-9134-4aab-b2da-df718212d031 spec: sourcePod: network-check-source-7bc5b6bf85-lxfsf targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-21T16:38:08Z" message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.247288ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:13:08Z" - latency: 2.292035ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:12:08Z" - latency: 1.925567ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:11:08Z" - latency: 2.450771ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:10:08Z" - latency: 2.446633ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:09:08Z" - latency: 1.896401ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:08:08Z" - latency: 2.3205ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:07:08Z" - latency: 2.429854ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:06:08Z" - latency: 2.117044ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:05:08Z" - latency: 2.199571ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:04:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T16:31:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-98-to-network-check-target-ip-10-0-141-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-98.ec2.internal uid: 452a8069-9c81-4880-bd5d-c57eef9eea33 resourceVersion: "62325" uid: b2205aaa-8c12-43b9-8088-63c5ec2b19a7 spec: sourcePod: network-check-source-7bc5b6bf85-lxfsf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T16:38:08Z" message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.961482ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:13:08Z" - latency: 1.797791ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:12:08Z" - latency: 1.879155ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:11:08Z" - latency: 1.957195ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:10:08Z" - latency: 1.821441ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:09:08Z" - latency: 2.144358ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:08:08Z" - latency: 3.604782ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:07:08Z" - latency: 1.986552ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:06:08Z" - latency: 1.876948ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:05:08Z" - latency: 1.8079ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:04:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T16:31:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-98-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-98.ec2.internal uid: 452a8069-9c81-4880-bd5d-c57eef9eea33 resourceVersion: "62326" uid: 26fee5e0-aa3f-4e61-bfdc-5fdce6c92f68 spec: sourcePod: network-check-source-7bc5b6bf85-lxfsf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T16:37:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 825.684µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:13:08Z" - latency: 2.077429ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:13:08Z" - latency: 941.711µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:12:08Z" - latency: 2.007543ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:12:08Z" - latency: 878.926µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:11:08Z" - latency: 1.811462ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:11:08Z" - latency: 1.000247ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:10:08Z" - latency: 1.791451ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:10:08Z" - latency: 971.04µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:09:08Z" - latency: 1.874241ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:09:08Z" kind: List metadata: resourceVersion: ""