apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T23:37:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.ec2.internal uid: deb55c33-4a9e-4d99-b6ec-44f4c29be3ed resourceVersion: "19258" uid: 0445bbd8-946a-4385-bba7-0d76f62220b9 spec: sourcePod: network-check-source-7f44b6dd87-fd8x5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-27T23:44:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.209822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:58:11Z" - latency: 896.996µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:57:11Z" - latency: 995.439µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:56:11Z" - latency: 713.904µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:55:11Z" - latency: 734.188µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:54:11Z" - latency: 949.836µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:53:11Z" - latency: 1.376691ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:52:11Z" - latency: 922.685µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:51:11Z" - latency: 1.503824ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:50:11Z" - latency: 894.122µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:49:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T23:37:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.ec2.internal uid: deb55c33-4a9e-4d99-b6ec-44f4c29be3ed resourceVersion: "20435" uid: c513af09-3141-4021-89cb-b2fc997dda66 spec: sourcePod: network-check-source-7f44b6dd87-fd8x5 targetEndpoint: ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T23:43:11Z" message: 'load-balancer-api-external: tcp connection to ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.608008ms message: 'load-balancer-api-external: tcp connection to ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:01:11Z" - latency: 8.403442ms message: 'load-balancer-api-external: resolved host name ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T00:01:11Z" - latency: 5.769614ms message: 'load-balancer-api-external: tcp connection to ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:00:11Z" - latency: 8.221975ms message: 'load-balancer-api-external: resolved host name ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T00:00:11Z" - latency: 5.027989ms message: 'load-balancer-api-external: tcp connection to ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:59:11Z" - latency: 8.516703ms message: 'load-balancer-api-external: resolved host name ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T23:59:11Z" - latency: 5.416133ms message: 'load-balancer-api-external: tcp connection to ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:58:11Z" - latency: 10.015046ms message: 'load-balancer-api-external: resolved host name ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T23:58:11Z" - latency: 5.958933ms message: 'load-balancer-api-external: tcp connection to ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:57:11Z" - latency: 8.234044ms message: 'load-balancer-api-external: resolved host name ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T23:57:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T23:37:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.ec2.internal uid: deb55c33-4a9e-4d99-b6ec-44f4c29be3ed resourceVersion: "20436" uid: 68194cde-05c8-418e-840e-9f20d9157345 spec: sourcePod: network-check-source-7f44b6dd87-fd8x5 targetEndpoint: ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T23:43:11Z" message: 'load-balancer-api-internal: tcp connection to ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.622065ms message: 'load-balancer-api-internal: tcp connection to ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:01:11Z" - latency: 8.457907ms message: 'load-balancer-api-internal: resolved host name ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T00:01:11Z" - latency: 6.607382ms message: 'load-balancer-api-internal: tcp connection to ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:00:11Z" - latency: 8.147538ms message: 'load-balancer-api-internal: resolved host name ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T00:00:11Z" - latency: 4.701268ms message: 'load-balancer-api-internal: tcp connection to ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:59:11Z" - latency: 8.608011ms message: 'load-balancer-api-internal: resolved host name ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T23:59:11Z" - latency: 5.399902ms message: 'load-balancer-api-internal: tcp connection to ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:58:11Z" - latency: 9.942048ms message: 'load-balancer-api-internal: resolved host name ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T23:58:11Z" - latency: 6.392196ms message: 'load-balancer-api-internal: tcp connection to ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:57:11Z" - latency: 8.268472ms message: 'load-balancer-api-internal: resolved host name ae87c8ade32cb4b9d8e254b69544f4da-1a2b3f2c0245ab19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T23:57:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T23:37:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-network-check-target-ip-10-0-130-189 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.ec2.internal uid: deb55c33-4a9e-4d99-b6ec-44f4c29be3ed resourceVersion: "19256" uid: 13458b16-2c80-493d-b1e9-ec70bcd333d1 spec: sourcePod: network-check-source-7f44b6dd87-fd8x5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-27T23:44:11Z" message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.266732ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:58:11Z" - latency: 771.175µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:57:11Z" - latency: 907.062µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:56:11Z" - latency: 796.671µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:55:11Z" - latency: 712.476µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:54:11Z" - latency: 831.176µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:53:11Z" - latency: 1.145496ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:52:11Z" - latency: 1.739169ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:51:11Z" - latency: 946.027µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:50:11Z" - latency: 781.2µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:49:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T23:37:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-network-check-target-ip-10-0-132-191 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.ec2.internal uid: deb55c33-4a9e-4d99-b6ec-44f4c29be3ed resourceVersion: "19255" uid: 796bd234-43c0-40ad-8e54-b845dc3642d1 spec: sourcePod: network-check-source-7f44b6dd87-fd8x5 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-27T23:44:11Z" message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.239114ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:58:11Z" - latency: 2.121444ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:57:11Z" - latency: 2.021776ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:56:11Z" - latency: 1.976258ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:55:11Z" - latency: 1.916122ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:54:11Z" - latency: 2.06589ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:53:11Z" - latency: 2.099597ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:52:11Z" - latency: 2.088612ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:51:11Z" - latency: 1.981143ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:50:11Z" - latency: 2.036838ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:49:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T23:37:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-network-check-target-ip-10-0-143-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.ec2.internal uid: deb55c33-4a9e-4d99-b6ec-44f4c29be3ed resourceVersion: "19257" uid: 41cfb240-23a9-4230-8a99-01ee0bb35bdf spec: sourcePod: network-check-source-7f44b6dd87-fd8x5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-27T23:44:11Z" message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.764241ms message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:58:11Z" - latency: 1.530233ms message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:57:11Z" - latency: 1.799804ms message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:56:11Z" - latency: 1.571482ms message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:55:11Z" - latency: 1.69498ms message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:54:11Z" - latency: 1.818543ms message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:53:11Z" - latency: 1.745188ms message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:52:11Z" - latency: 1.777964ms message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:51:11Z" - latency: 1.816347ms message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:50:11Z" - latency: 1.940865ms message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:49:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T23:37:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.ec2.internal uid: deb55c33-4a9e-4d99-b6ec-44f4c29be3ed resourceVersion: "20434" uid: dc18494c-738c-4d44-93b2-4c85830dadce spec: sourcePod: network-check-source-7f44b6dd87-fd8x5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-27T23:43:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 667.943µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:01:11Z" - latency: 1.824646ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T00:01:11Z" - latency: 1.012895ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:00:11Z" - latency: 1.607004ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T00:00:11Z" - latency: 777.095µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:59:11Z" - latency: 2.29676ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T23:59:11Z" - latency: 761.231µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:58:11Z" - latency: 1.753236ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T23:58:11Z" - latency: 882.732µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T23:57:11Z" - latency: 1.770563ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T23:57:11Z" kind: List metadata: resourceVersion: ""