apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T14:00:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-99-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-99.ec2.internal uid: fc63f465-c162-4aee-bba2-59627f629d83 resourceVersion: "135087" uid: 741af130-ddf5-429c-a6f8-c1ec734e7460 spec: sourcePod: network-check-source-6f78d59f99-ljkcn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T14:07:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.006399ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:10:17Z" - latency: 1.129717ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:09:17Z" - latency: 1.525729ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:08:17Z" - latency: 1.31398ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:07:17Z" - latency: 1.219509ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:06:17Z" - latency: 953.324µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:05:17Z" - latency: 1.318872ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:04:17Z" - latency: 2.988025ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:03:17Z" - latency: 894.642µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:02:17Z" - latency: 908.473µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:01:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T14:00:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-99-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-99.ec2.internal uid: fc63f465-c162-4aee-bba2-59627f629d83 resourceVersion: "131428" uid: 4c62e24d-c412-4418-aa11-a0e866cf0642 spec: sourcePod: network-check-source-6f78d59f99-ljkcn targetEndpoint: ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T14:06:17Z" message: 'load-balancer-api-external: tcp connection to ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 19.253319ms message: 'load-balancer-api-external: tcp connection to ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:06:17Z" - latency: 6.494541ms message: 'load-balancer-api-external: resolved host name ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T15:06:17Z" - latency: 18.708968ms message: 'load-balancer-api-external: tcp connection to ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:05:17Z" - latency: 6.695558ms message: 'load-balancer-api-external: resolved host name ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T15:05:17Z" - latency: 14.297512ms message: 'load-balancer-api-external: tcp connection to ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:04:17Z" - latency: 7.051696ms message: 'load-balancer-api-external: resolved host name ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T15:04:17Z" - latency: 16.226983ms message: 'load-balancer-api-external: tcp connection to ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:03:17Z" - latency: 15.742352ms message: 'load-balancer-api-external: resolved host name ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T15:03:17Z" - latency: 17.184372ms message: 'load-balancer-api-external: tcp connection to ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:02:17Z" - latency: 6.714446ms message: 'load-balancer-api-external: resolved host name ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T15:02:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T14:00:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-99-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-99.ec2.internal uid: fc63f465-c162-4aee-bba2-59627f629d83 resourceVersion: "131427" uid: 4cd97789-9791-4e49-b056-792b3f4fc35f spec: sourcePod: network-check-source-6f78d59f99-ljkcn targetEndpoint: ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T14:06:17Z" message: 'load-balancer-api-internal: tcp connection to ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.096655ms message: 'load-balancer-api-internal: tcp connection to ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:06:17Z" - latency: 6.547942ms message: 'load-balancer-api-internal: resolved host name ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T15:06:17Z" - latency: 18.232368ms message: 'load-balancer-api-internal: tcp connection to ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:05:17Z" - latency: 6.785012ms message: 'load-balancer-api-internal: resolved host name ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T15:05:17Z" - latency: 14.439591ms message: 'load-balancer-api-internal: tcp connection to ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:04:17Z" - latency: 6.972438ms message: 'load-balancer-api-internal: resolved host name ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T15:04:17Z" - latency: 14.773333ms message: 'load-balancer-api-internal: tcp connection to ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:03:17Z" - latency: 15.488944ms message: 'load-balancer-api-internal: resolved host name ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T15:03:17Z" - latency: 17.772259ms message: 'load-balancer-api-internal: tcp connection to ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:02:17Z" - latency: 6.704693ms message: 'load-balancer-api-internal: resolved host name ade32da817fe24ed5a6feb9e5c614c1f-e2ff0f386bcff078.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T15:02:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T14:00:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-99-to-network-check-target-ip-10-0-129-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-99.ec2.internal uid: fc63f465-c162-4aee-bba2-59627f629d83 resourceVersion: "135086" uid: c2ecf332-9c7e-4aac-88ab-93f8628be222 spec: sourcePod: network-check-source-6f78d59f99-ljkcn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T14:07:17Z" message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.741884ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:10:17Z" - latency: 2.903904ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:09:17Z" - latency: 2.440219ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:08:17Z" - latency: 2.57326ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:07:17Z" - latency: 2.401525ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:06:17Z" - latency: 2.547342ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:05:17Z" - latency: 2.54587ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:04:17Z" - latency: 4.071364ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:03:17Z" - latency: 2.379382ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:02:17Z" - latency: 2.352178ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:01:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T14:00:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-99-to-network-check-target-ip-10-0-134-9 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-99.ec2.internal uid: fc63f465-c162-4aee-bba2-59627f629d83 resourceVersion: "135085" uid: 2160dabc-27f5-4730-8888-dab34f475b99 spec: sourcePod: network-check-source-6f78d59f99-ljkcn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T14:07:17Z" message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.359686ms message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:10:17Z" - latency: 2.366603ms message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:09:17Z" - latency: 2.291836ms message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:08:17Z" - latency: 2.511667ms message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:07:17Z" - latency: 2.287801ms message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:06:17Z" - latency: 2.779031ms message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:05:17Z" - latency: 2.617007ms message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:04:17Z" - latency: 7.529791ms message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:03:17Z" - latency: 2.018591ms message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:02:17Z" - latency: 2.38144ms message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:01:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T14:00:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-99-to-network-check-target-ip-10-0-134-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-99.ec2.internal uid: fc63f465-c162-4aee-bba2-59627f629d83 resourceVersion: "135084" uid: d83d9f27-28b0-4271-9468-f5c35c71868a spec: sourcePod: network-check-source-6f78d59f99-ljkcn targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T14:07:17Z" message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 991.081µs message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:10:17Z" - latency: 1.045978ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:09:17Z" - latency: 1.645397ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:08:17Z" - latency: 1.28673ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:07:17Z" - latency: 965.497µs message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:06:17Z" - latency: 986.916µs message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:05:17Z" - latency: 1.099845ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:04:17Z" - latency: 2.729745ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:03:17Z" - latency: 849.625µs message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:02:17Z" - latency: 982.08µs message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:01:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T14:00:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-99-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-99.ec2.internal uid: fc63f465-c162-4aee-bba2-59627f629d83 resourceVersion: "131425" uid: 48ed0917-41a8-4e43-a0c3-5e418ebdb4dd spec: sourcePod: network-check-source-6f78d59f99-ljkcn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T14:06:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 982.941µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:06:17Z" - latency: 1.626226ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T15:06:17Z" - latency: 967.76µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:05:17Z" - latency: 1.759851ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T15:05:17Z" - latency: 1.363021ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:04:17Z" - latency: 1.94389ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T15:04:17Z" - latency: 1.756315ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:03:17Z" - latency: 10.02898ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T15:03:17Z" - latency: 904.829µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:02:17Z" - latency: 1.845192ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T15:02:17Z" kind: List metadata: resourceVersion: ""