apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T15:58:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-57-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-57.ec2.internal uid: 965d1e0d-2ed5-4e01-81fc-e1e482c57849 resourceVersion: "54558" uid: 3fde74fd-208c-4349-839c-39c9d683e5fa spec: sourcePod: network-check-source-685456655f-gt8ms targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T16:05:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.06955ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:26:31Z" - latency: 999.673µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:25:31Z" - latency: 1.155972ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:24:31Z" - latency: 1.349019ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:23:31Z" - latency: 1.432446ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:22:31Z" - latency: 951.503µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:21:31Z" - latency: 1.208521ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:20:31Z" - latency: 1.179317ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:19:31Z" - latency: 928.085µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:18:31Z" - latency: 1.1961ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:17:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T15:58:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-57-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-57.ec2.internal uid: 965d1e0d-2ed5-4e01-81fc-e1e482c57849 resourceVersion: "55950" uid: 878d0e34-5f2b-4d0e-a175-fe71743c5691 spec: sourcePod: network-check-source-685456655f-gt8ms targetEndpoint: a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T16:04:31Z" message: 'load-balancer-api-external: tcp connection to a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.713173ms message: 'load-balancer-api-external: tcp connection to a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:28:31Z" - latency: 6.582363ms message: 'load-balancer-api-external: resolved host name a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T16:28:31Z" - latency: 5.48181ms message: 'load-balancer-api-external: tcp connection to a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:27:31Z" - latency: 10.035078ms message: 'load-balancer-api-external: resolved host name a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T16:27:31Z" - latency: 5.384082ms message: 'load-balancer-api-external: tcp connection to a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:26:31Z" - latency: 8.635261ms message: 'load-balancer-api-external: resolved host name a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T16:26:31Z" - latency: 4.288096ms message: 'load-balancer-api-external: tcp connection to a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:25:31Z" - latency: 6.92023ms message: 'load-balancer-api-external: resolved host name a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T16:25:31Z" - latency: 4.898324ms message: 'load-balancer-api-external: tcp connection to a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:24:31Z" - latency: 7.050567ms message: 'load-balancer-api-external: resolved host name a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T16:24:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T15:58:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-57-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-57.ec2.internal uid: 965d1e0d-2ed5-4e01-81fc-e1e482c57849 resourceVersion: "55951" uid: 36e3b8ad-754e-4058-9336-9576d9587295 spec: sourcePod: network-check-source-685456655f-gt8ms targetEndpoint: a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T16:04:31Z" message: 'load-balancer-api-internal: tcp connection to a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.691227ms message: 'load-balancer-api-internal: tcp connection to a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:28:31Z" - latency: 6.531312ms message: 'load-balancer-api-internal: resolved host name a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T16:28:31Z" - latency: 4.589585ms message: 'load-balancer-api-internal: tcp connection to a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:27:31Z" - latency: 10.09321ms message: 'load-balancer-api-internal: resolved host name a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T16:27:31Z" - latency: 5.397078ms message: 'load-balancer-api-internal: tcp connection to a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:26:31Z" - latency: 8.530745ms message: 'load-balancer-api-internal: resolved host name a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T16:26:31Z" - latency: 4.909688ms message: 'load-balancer-api-internal: tcp connection to a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:25:31Z" - latency: 6.872573ms message: 'load-balancer-api-internal: resolved host name a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T16:25:31Z" - latency: 3.785564ms message: 'load-balancer-api-internal: tcp connection to a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:24:31Z" - latency: 7.106288ms message: 'load-balancer-api-internal: resolved host name a2ab68896f83f4442b0f3380475d31b9-6c782b91cec408a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T16:24:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T15:58:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-57-to-network-check-target-ip-10-0-130-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-57.ec2.internal uid: 965d1e0d-2ed5-4e01-81fc-e1e482c57849 resourceVersion: "54555" uid: f1cc2911-fc64-4359-ab92-ae03ecb708fa spec: sourcePod: network-check-source-685456655f-gt8ms targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T16:05:31Z" message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.184738ms message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:26:31Z" - latency: 884.259µs message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:25:31Z" - latency: 1.239369ms message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:24:31Z" - latency: 1.004633ms message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:23:31Z" - latency: 1.323406ms message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:22:31Z" - latency: 1.020546ms message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:21:31Z" - latency: 1.021ms message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:20:31Z" - latency: 876.742µs message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:19:31Z" - latency: 959.447µs message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:18:31Z" - latency: 886.252µs message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:17:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T15:58:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-57-to-network-check-target-ip-10-0-133-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-57.ec2.internal uid: 965d1e0d-2ed5-4e01-81fc-e1e482c57849 resourceVersion: "54556" uid: 616dc835-2ad0-44ef-8991-b871c9165ad5 spec: sourcePod: network-check-source-685456655f-gt8ms targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T16:05:31Z" message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.761725ms message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:26:31Z" - latency: 2.278714ms message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:25:31Z" - latency: 2.388607ms message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:24:31Z" - latency: 2.226363ms message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:23:31Z" - latency: 2.415246ms message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:22:31Z" - latency: 2.544133ms message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:21:31Z" - latency: 2.503846ms message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:20:31Z" - latency: 2.435193ms message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:19:31Z" - latency: 2.27183ms message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:18:31Z" - latency: 2.199168ms message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:17:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T15:58:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-57-to-network-check-target-ip-10-0-135-66 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-57.ec2.internal uid: 965d1e0d-2ed5-4e01-81fc-e1e482c57849 resourceVersion: "54557" uid: a6778a8e-3bee-47c9-b53b-9cfa9facaec3 spec: sourcePod: network-check-source-685456655f-gt8ms targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T16:05:31Z" message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.426934ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:26:31Z" - latency: 2.471472ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:25:31Z" - latency: 2.084551ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:24:31Z" - latency: 2.310885ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:23:31Z" - latency: 2.698747ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:22:31Z" - latency: 2.503926ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:21:31Z" - latency: 1.959ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:20:31Z" - latency: 2.392769ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:19:31Z" - latency: 2.464705ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:18:31Z" - latency: 2.096102ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:17:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T15:58:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-57-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-57.ec2.internal uid: 965d1e0d-2ed5-4e01-81fc-e1e482c57849 resourceVersion: "55949" uid: 94300690-7eae-4c1d-a925-bf0185dbb3de spec: sourcePod: network-check-source-685456655f-gt8ms targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T16:04:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 845.07µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:28:31Z" - latency: 1.937419ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T16:28:31Z" - latency: 902.696µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:27:31Z" - latency: 1.973175ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T16:27:31Z" - latency: 1.073303ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:26:31Z" - latency: 2.438494ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T16:26:31Z" - latency: 950.554µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:25:31Z" - latency: 1.621733ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T16:25:31Z" - latency: 887.531µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T16:24:31Z" - latency: 1.994959ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T16:24:31Z" kind: List metadata: resourceVersion: ""