apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:37:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-22-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-22.ec2.internal uid: 8eda3219-0597-49a2-8713-0c3a9d603d6d resourceVersion: "46343" uid: 91b3ccaf-4646-425e-8748-f86e1447b508 spec: sourcePod: network-check-source-8894fc9bd-2qtfd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T17:44:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.155923ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:19Z" - latency: 1.005497ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:19Z" - latency: 916.774µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:59:19Z" - latency: 1.096056ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:58:19Z" - latency: 800.36µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:57:19Z" - latency: 1.418732ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:56:19Z" - latency: 1.069576ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:55:19Z" - latency: 1.03663ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:54:19Z" - latency: 1.093537ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:53:19Z" - latency: 1.037235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:52:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:37:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-22-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-22.ec2.internal uid: 8eda3219-0597-49a2-8713-0c3a9d603d6d resourceVersion: "46344" uid: e26c53ac-2103-43e8-8b30-e7e2ca6e7bc7 spec: sourcePod: network-check-source-8894fc9bd-2qtfd targetEndpoint: a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T17:43:19Z" message: 'load-balancer-api-external: tcp connection to a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.746108ms message: 'load-balancer-api-external: tcp connection to a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:19Z" - latency: 12.649452ms message: 'load-balancer-api-external: resolved host name a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:01:19Z" - latency: 4.651648ms message: 'load-balancer-api-external: tcp connection to a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:19Z" - latency: 7.601566ms message: 'load-balancer-api-external: resolved host name a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:00:19Z" - latency: 5.617621ms message: 'load-balancer-api-external: tcp connection to a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:59:19Z" - latency: 8.626065ms message: 'load-balancer-api-external: resolved host name a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:59:19Z" - latency: 5.519619ms message: 'load-balancer-api-external: tcp connection to a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:58:19Z" - latency: 8.662554ms message: 'load-balancer-api-external: resolved host name a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:58:19Z" - latency: 5.661623ms message: 'load-balancer-api-external: tcp connection to a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:57:19Z" - latency: 7.877581ms message: 'load-balancer-api-external: resolved host name a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:57:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:37:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-22-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-22.ec2.internal uid: 8eda3219-0597-49a2-8713-0c3a9d603d6d resourceVersion: "46345" uid: 92913c3c-3e6b-4b8e-baaa-bd63dd294229 spec: sourcePod: network-check-source-8894fc9bd-2qtfd targetEndpoint: a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T17:43:19Z" message: 'load-balancer-api-internal: tcp connection to a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.537974ms message: 'load-balancer-api-internal: tcp connection to a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:19Z" - latency: 12.599259ms message: 'load-balancer-api-internal: resolved host name a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:01:19Z" - latency: 4.660864ms message: 'load-balancer-api-internal: tcp connection to a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:19Z" - latency: 7.543439ms message: 'load-balancer-api-internal: resolved host name a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:00:19Z" - latency: 5.606343ms message: 'load-balancer-api-internal: tcp connection to a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:59:19Z" - latency: 8.647477ms message: 'load-balancer-api-internal: resolved host name a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:59:19Z" - latency: 5.202356ms message: 'load-balancer-api-internal: tcp connection to a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:58:19Z" - latency: 8.698324ms message: 'load-balancer-api-internal: resolved host name a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:58:19Z" - latency: 5.589477ms message: 'load-balancer-api-internal: tcp connection to a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:57:19Z" - latency: 7.931578ms message: 'load-balancer-api-internal: resolved host name a8a7314060efa4e129d40fa26fef232c-8648ce91b86e4eef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:57:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:37:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-22-to-network-check-target-ip-10-0-130-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-22.ec2.internal uid: 8eda3219-0597-49a2-8713-0c3a9d603d6d resourceVersion: "46342" uid: 956b3180-0461-4a81-a9a8-698584459551 spec: sourcePod: network-check-source-8894fc9bd-2qtfd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T17:44:19Z" message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.120885ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:19Z" - latency: 2.049668ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:19Z" - latency: 2.108285ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:59:19Z" - latency: 2.055902ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:58:19Z" - latency: 2.045955ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:57:19Z" - latency: 2.112344ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:56:19Z" - latency: 2.047921ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:55:19Z" - latency: 1.959156ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:54:19Z" - latency: 1.896346ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:53:19Z" - latency: 2.162335ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:52:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:37:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-22-to-network-check-target-ip-10-0-131-22 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-22.ec2.internal uid: 8eda3219-0597-49a2-8713-0c3a9d603d6d resourceVersion: "46339" uid: d85f5700-05c4-4045-a828-1a07bd2a9798 spec: sourcePod: network-check-source-8894fc9bd-2qtfd targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T17:44:19Z" message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.332947ms message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:19Z" - latency: 743.786µs message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:19Z" - latency: 784.689µs message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:59:19Z" - latency: 794.42µs message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:58:19Z" - latency: 769.371µs message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:57:19Z" - latency: 801.711µs message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:56:19Z" - latency: 789.123µs message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:55:19Z" - latency: 1.444678ms message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:54:19Z" - latency: 1.272459ms message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:53:19Z" - latency: 1.307026ms message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:52:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:37:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-22-to-network-check-target-ip-10-0-138-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-22.ec2.internal uid: 8eda3219-0597-49a2-8713-0c3a9d603d6d resourceVersion: "46340" uid: 905b0b9a-6b74-4bf6-ac56-7fdf57786855 spec: sourcePod: network-check-source-8894fc9bd-2qtfd targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T17:44:19Z" message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.010421ms message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:19Z" - latency: 1.916516ms message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:19Z" - latency: 1.986606ms message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:59:19Z" - latency: 1.988382ms message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:58:19Z" - latency: 1.695951ms message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:57:19Z" - latency: 1.740422ms message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:56:19Z" - latency: 1.924913ms message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:55:19Z" - latency: 1.91438ms message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:54:19Z" - latency: 1.787959ms message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:53:19Z" - latency: 1.985662ms message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:52:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:37:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-22-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-22.ec2.internal uid: 8eda3219-0597-49a2-8713-0c3a9d603d6d resourceVersion: "46341" uid: 2707315c-57aa-4303-ac44-9655acd1f9c6 spec: sourcePod: network-check-source-8894fc9bd-2qtfd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T17:43:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 827.405µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:19Z" - latency: 1.49902ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:01:19Z" - latency: 949.394µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:19Z" - latency: 1.664704ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:00:19Z" - latency: 805.888µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:59:19Z" - latency: 1.661208ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:59:19Z" - latency: 937.247µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:58:19Z" - latency: 1.667516ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:58:19Z" - latency: 891.075µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:57:19Z" - latency: 1.623966ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:57:19Z" kind: List metadata: resourceVersion: ""