apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T13:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-73-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-73.ec2.internal uid: a6695e3a-28d1-4fac-8c4c-e5251a92f36f resourceVersion: "26077" uid: db8c68aa-3cc9-4e4c-a9d5-193b826b6c9b spec: sourcePod: network-check-source-8894fc9bd-9jhgc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T13:32:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.082369ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:07:20Z" - latency: 728.564µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:06:20Z" - latency: 1.076464ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:05:20Z" - latency: 1.002804ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:04:20Z" - latency: 835.061µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:03:20Z" - latency: 885.165µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:02:20Z" - latency: 982.037µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:01:20Z" - latency: 727.525µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:00:20Z" - latency: 1.345562ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T13:59:20Z" - latency: 866.767µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T13:58:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T13:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-73-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-73.ec2.internal uid: a6695e3a-28d1-4fac-8c4c-e5251a92f36f resourceVersion: "26078" uid: 0d571370-c212-4242-989a-fc40fa9065e2 spec: sourcePod: network-check-source-8894fc9bd-9jhgc targetEndpoint: a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T13:31:20Z" message: 'load-balancer-api-external: tcp connection to a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.920771ms message: 'load-balancer-api-external: tcp connection to a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:07:20Z" - latency: 10.89661ms message: 'load-balancer-api-external: resolved host name a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:07:20Z" - latency: 4.713218ms message: 'load-balancer-api-external: tcp connection to a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:06:20Z" - latency: 8.121441ms message: 'load-balancer-api-external: resolved host name a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:06:20Z" - latency: 4.599402ms message: 'load-balancer-api-external: tcp connection to a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:05:20Z" - latency: 10.708101ms message: 'load-balancer-api-external: resolved host name a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:05:20Z" - latency: 4.907049ms message: 'load-balancer-api-external: tcp connection to a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:04:20Z" - latency: 7.895525ms message: 'load-balancer-api-external: resolved host name a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:04:20Z" - latency: 5.435902ms message: 'load-balancer-api-external: tcp connection to a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:03:20Z" - latency: 9.175918ms message: 'load-balancer-api-external: resolved host name a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:03:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T13:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-73-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-73.ec2.internal uid: a6695e3a-28d1-4fac-8c4c-e5251a92f36f resourceVersion: "26079" uid: 6e441462-7475-4116-9702-98f38544050e spec: sourcePod: network-check-source-8894fc9bd-9jhgc targetEndpoint: a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T13:31:20Z" message: 'load-balancer-api-internal: tcp connection to a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.626031ms message: 'load-balancer-api-internal: tcp connection to a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:07:20Z" - latency: 10.846904ms message: 'load-balancer-api-internal: resolved host name a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:07:20Z" - latency: 4.726446ms message: 'load-balancer-api-internal: tcp connection to a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:06:20Z" - latency: 8.077186ms message: 'load-balancer-api-internal: resolved host name a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:06:20Z" - latency: 4.598773ms message: 'load-balancer-api-internal: tcp connection to a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:05:20Z" - latency: 10.657826ms message: 'load-balancer-api-internal: resolved host name a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:05:20Z" - latency: 4.896705ms message: 'load-balancer-api-internal: tcp connection to a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:04:20Z" - latency: 7.842328ms message: 'load-balancer-api-internal: resolved host name a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:04:20Z" - latency: 5.370646ms message: 'load-balancer-api-internal: tcp connection to a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:03:20Z" - latency: 9.137432ms message: 'load-balancer-api-internal: resolved host name a4fdceb89f7ba46fb885d43a2000a723-e8fad4f9fd20d4a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:03:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T13:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-73-to-network-check-target-ip-10-0-128-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-73.ec2.internal uid: a6695e3a-28d1-4fac-8c4c-e5251a92f36f resourceVersion: "26074" uid: 2edbfe38-8929-4597-ad7a-a36d3006415a spec: sourcePod: network-check-source-8894fc9bd-9jhgc targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T13:32:20Z" message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.807891ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:07:20Z" - latency: 1.91152ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:06:20Z" - latency: 1.576166ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:05:20Z" - latency: 1.805861ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:04:20Z" - latency: 1.878554ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:03:20Z" - latency: 1.700048ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:02:20Z" - latency: 1.849342ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:01:20Z" - latency: 1.874879ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:00:20Z" - latency: 1.738724ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T13:59:20Z" - latency: 1.662004ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T13:58:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T13:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-73-to-network-check-target-ip-10-0-136-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-73.ec2.internal uid: a6695e3a-28d1-4fac-8c4c-e5251a92f36f resourceVersion: "26073" uid: 8e47a848-ebfb-4a7b-a54b-50e4eda1b400 spec: sourcePod: network-check-source-8894fc9bd-9jhgc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T13:32:20Z" message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 800.041µs message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:07:20Z" - latency: 856.332µs message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:06:20Z" - latency: 872.89µs message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:05:20Z" - latency: 1.033467ms message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:04:20Z" - latency: 755.43µs message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:03:20Z" - latency: 984.147µs message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:02:20Z" - latency: 793.027µs message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:01:20Z" - latency: 875.166µs message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:00:20Z" - latency: 748.445µs message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T13:59:20Z" - latency: 1.07321ms message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T13:58:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T13:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-73-to-network-check-target-ip-10-0-142-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-73.ec2.internal uid: a6695e3a-28d1-4fac-8c4c-e5251a92f36f resourceVersion: "26075" uid: 804ee52b-a9c7-4dc0-a879-6b0b56775737 spec: sourcePod: network-check-source-8894fc9bd-9jhgc targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T13:32:20Z" message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.205819ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:07:20Z" - latency: 2.103886ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:06:20Z" - latency: 2.141309ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:05:20Z" - latency: 2.024509ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:04:20Z" - latency: 2.038737ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:03:20Z" - latency: 1.927481ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:02:20Z" - latency: 1.905596ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:01:20Z" - latency: 2.162587ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:00:20Z" - latency: 1.951231ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T13:59:20Z" - latency: 2.14346ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T13:58:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T13:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-73-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-73.ec2.internal uid: a6695e3a-28d1-4fac-8c4c-e5251a92f36f resourceVersion: "26076" uid: bdba19a8-25ef-49dc-9d13-74d6767093f0 spec: sourcePod: network-check-source-8894fc9bd-9jhgc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T13:31:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 871.9µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:07:20Z" - latency: 1.704861ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:07:20Z" - latency: 956.163µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:06:20Z" - latency: 1.766376ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:06:20Z" - latency: 837.113µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:05:20Z" - latency: 1.655752ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:05:20Z" - latency: 804.385µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:04:20Z" - latency: 1.825875ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:04:20Z" - latency: 783.277µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:03:20Z" - latency: 2.219727ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:03:20Z" kind: List metadata: resourceVersion: ""