apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T15:05:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-244-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-244.ec2.internal uid: ace800ae-8dd9-4239-9dde-30da409662cb resourceVersion: "45461" uid: fb9fd45c-9bd7-4ced-824e-6eabb5275447 spec: sourcePod: network-check-source-7bc5b6bf85-hpk7v targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T15:12:09Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 928.476µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:33:09Z" - latency: 971.374µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:32:09Z" - latency: 911.228µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:31:09Z" - latency: 1.94934ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:30:09Z" - latency: 940.751µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:29:09Z" - latency: 1.468189ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:28:09Z" - latency: 1.57647ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:27:09Z" - latency: 895.147µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:26:09Z" - latency: 923.192µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:25:09Z" - latency: 1.143651ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:24:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T15:05:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-244-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-244.ec2.internal uid: ace800ae-8dd9-4239-9dde-30da409662cb resourceVersion: "48117" uid: 652259e3-9d12-4747-a46a-d9f266586568 spec: sourcePod: network-check-source-7bc5b6bf85-hpk7v targetEndpoint: a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T15:11:09Z" message: 'load-balancer-api-external: tcp connection to a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.498912ms message: 'load-balancer-api-external: tcp connection to a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:35:09Z" - latency: 7.209146ms message: 'load-balancer-api-external: resolved host name a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T15:35:09Z" - latency: 6.268909ms message: 'load-balancer-api-external: tcp connection to a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:34:09Z" - latency: 6.621481ms message: 'load-balancer-api-external: resolved host name a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T15:34:09Z" - latency: 5.351038ms message: 'load-balancer-api-external: tcp connection to a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:33:09Z" - latency: 15.862093ms message: 'load-balancer-api-external: resolved host name a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T15:33:09Z" - latency: 3.867644ms message: 'load-balancer-api-external: tcp connection to a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:32:09Z" - latency: 8.932402ms message: 'load-balancer-api-external: resolved host name a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T15:32:09Z" - latency: 4.949265ms message: 'load-balancer-api-external: tcp connection to a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:31:09Z" - latency: 7.149555ms message: 'load-balancer-api-external: resolved host name a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T15:31:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T15:05:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-244-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-244.ec2.internal uid: ace800ae-8dd9-4239-9dde-30da409662cb resourceVersion: "48116" uid: 514b184c-c6cc-405e-ad69-230b9b9ceb94 spec: sourcePod: network-check-source-7bc5b6bf85-hpk7v targetEndpoint: a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T15:11:09Z" message: 'load-balancer-api-internal: tcp connection to a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.961047ms message: 'load-balancer-api-internal: tcp connection to a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:35:09Z" - latency: 7.239075ms message: 'load-balancer-api-internal: resolved host name a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T15:35:09Z" - latency: 4.364376ms message: 'load-balancer-api-internal: tcp connection to a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:34:09Z" - latency: 6.6844ms message: 'load-balancer-api-internal: resolved host name a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T15:34:09Z" - latency: 5.861083ms message: 'load-balancer-api-internal: tcp connection to a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:33:09Z" - latency: 15.756418ms message: 'load-balancer-api-internal: resolved host name a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T15:33:09Z" - latency: 3.859497ms message: 'load-balancer-api-internal: tcp connection to a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:32:09Z" - latency: 8.951175ms message: 'load-balancer-api-internal: resolved host name a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T15:32:09Z" - latency: 3.992121ms message: 'load-balancer-api-internal: tcp connection to a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:31:09Z" - latency: 7.043806ms message: 'load-balancer-api-internal: resolved host name a7f77711d9677424e9f43a3fb0bb7179-43cb87939368c80c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T15:31:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T15:05:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-244-to-network-check-target-ip-10-0-128-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-244.ec2.internal uid: ace800ae-8dd9-4239-9dde-30da409662cb resourceVersion: "45457" uid: def063a1-cbd1-478c-81b0-70738841945a spec: sourcePod: network-check-source-7bc5b6bf85-hpk7v targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T15:12:09Z" message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.126218ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:33:09Z" - latency: 1.545784ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:32:09Z" - latency: 944.322µs message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:31:09Z" - latency: 977.135µs message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:30:09Z" - latency: 1.551971ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:29:09Z" - latency: 1.160172ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:28:09Z" - latency: 1.087884ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:27:09Z" - latency: 1.023384ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:26:09Z" - latency: 1.473911ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:25:09Z" - latency: 1.02306ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:24:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T15:05:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-244-to-network-check-target-ip-10-0-133-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-244.ec2.internal uid: ace800ae-8dd9-4239-9dde-30da409662cb resourceVersion: "45460" uid: 561dd091-0a08-499b-9338-1eedb000617e spec: sourcePod: network-check-source-7bc5b6bf85-hpk7v targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-21T15:12:09Z" message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.535871ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:33:09Z" - latency: 2.675553ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:32:09Z" - latency: 2.092224ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:31:09Z" - latency: 2.403541ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:30:09Z" - latency: 2.286742ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:29:09Z" - latency: 2.202932ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:28:09Z" - latency: 2.256405ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:27:09Z" - latency: 2.069973ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:26:09Z" - latency: 2.281463ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:25:09Z" - latency: 2.394341ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:24:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T15:05:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-244-to-network-check-target-ip-10-0-135-119 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-244.ec2.internal uid: ace800ae-8dd9-4239-9dde-30da409662cb resourceVersion: "45459" uid: 7a608b7f-57b2-4212-bd0d-e4cac6ed960b spec: sourcePod: network-check-source-7bc5b6bf85-hpk7v targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T15:12:09Z" message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.519451ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:33:09Z" - latency: 2.350487ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:32:09Z" - latency: 2.270147ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:31:09Z" - latency: 2.422551ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:30:09Z" - latency: 2.978814ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:29:09Z" - latency: 2.483212ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:28:09Z" - latency: 3.258471ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:27:09Z" - latency: 2.281897ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:26:09Z" - latency: 2.488612ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:25:09Z" - latency: 2.459717ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:24:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T15:05:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-244-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-244.ec2.internal uid: ace800ae-8dd9-4239-9dde-30da409662cb resourceVersion: "48115" uid: 373a8538-f99b-4f27-a5b7-237041f49b02 spec: sourcePod: network-check-source-7bc5b6bf85-hpk7v targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T15:11:09Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.193261ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:35:09Z" - latency: 1.746843ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T15:35:09Z" - latency: 1.419966ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:34:09Z" - latency: 1.828508ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T15:34:09Z" - latency: 1.668567ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:33:09Z" - latency: 2.054765ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T15:33:09Z" - latency: 911.795µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:32:09Z" - latency: 1.90847ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T15:32:09Z" - latency: 1.008426ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T15:31:09Z" - latency: 1.633481ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T15:31:09Z" kind: List metadata: resourceVersion: ""