apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T16:42:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-35-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-35.ec2.internal uid: 7fba6726-bb45-44d1-b7d1-2dbfe3a4ffeb resourceVersion: "78380" uid: 139a343e-817f-4dc6-922e-17c48d9a6600 spec: sourcePod: network-check-source-65bdbbff45-g9g9z targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-05T16:49: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.065427ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:38:31Z" - latency: 1.052227ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:37:31Z" - latency: 833.444µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:36:31Z" - latency: 1.04069ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:35:31Z" - latency: 1.112653ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:34:31Z" - latency: 1.16823ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:33:31Z" - latency: 1.329995ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:32:31Z" - latency: 882.214µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:31:31Z" - latency: 968.841µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:30:31Z" - latency: 1.509082ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:29:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T16:42:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-35-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-35.ec2.internal uid: 7fba6726-bb45-44d1-b7d1-2dbfe3a4ffeb resourceVersion: "76407" uid: 8726677f-d30d-4259-a590-59b9ff226438 spec: sourcePod: network-check-source-65bdbbff45-g9g9z targetEndpoint: a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T16:48:31Z" message: 'load-balancer-api-external: tcp connection to a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.33621ms message: 'load-balancer-api-external: tcp connection to a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:36:31Z" - latency: 7.272138ms message: 'load-balancer-api-external: resolved host name a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:36:31Z" - latency: 3.479269ms message: 'load-balancer-api-external: tcp connection to a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:35:31Z" - latency: 7.11574ms message: 'load-balancer-api-external: resolved host name a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:35:31Z" - latency: 3.948317ms message: 'load-balancer-api-external: tcp connection to a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:34:31Z" - latency: 7.442983ms message: 'load-balancer-api-external: resolved host name a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:34:31Z" - latency: 4.365136ms message: 'load-balancer-api-external: tcp connection to a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:33:31Z" - latency: 7.154555ms message: 'load-balancer-api-external: resolved host name a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:33:31Z" - latency: 4.461655ms message: 'load-balancer-api-external: tcp connection to a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:32:31Z" - latency: 6.738502ms message: 'load-balancer-api-external: resolved host name a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:32:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T16:42:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-35-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-35.ec2.internal uid: 7fba6726-bb45-44d1-b7d1-2dbfe3a4ffeb resourceVersion: "76408" uid: c7b8e63b-56ee-400e-8c1b-fd3afdbb0f2b spec: sourcePod: network-check-source-65bdbbff45-g9g9z targetEndpoint: a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T16:48:31Z" message: 'load-balancer-api-internal: tcp connection to a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.368202ms message: 'load-balancer-api-internal: tcp connection to a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:36:31Z" - latency: 7.167854ms message: 'load-balancer-api-internal: resolved host name a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:36:31Z" - latency: 3.49485ms message: 'load-balancer-api-internal: tcp connection to a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:35:31Z" - latency: 7.169261ms message: 'load-balancer-api-internal: resolved host name a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:35:31Z" - latency: 3.931862ms message: 'load-balancer-api-internal: tcp connection to a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:34:31Z" - latency: 7.493279ms message: 'load-balancer-api-internal: resolved host name a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:34:31Z" - latency: 4.30838ms message: 'load-balancer-api-internal: tcp connection to a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:33:31Z" - latency: 7.204174ms message: 'load-balancer-api-internal: resolved host name a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:33:31Z" - latency: 4.452786ms message: 'load-balancer-api-internal: tcp connection to a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:32:31Z" - latency: 6.758958ms message: 'load-balancer-api-internal: resolved host name a52e101754a424248940b1d2464fcbfd-36ca29e8a8725d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:32:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T16:42:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-35-to-network-check-target-ip-10-0-130-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-35.ec2.internal uid: 7fba6726-bb45-44d1-b7d1-2dbfe3a4ffeb resourceVersion: "78378" uid: a7c51b4f-6539-45c4-9e58-b3e8f7524ff1 spec: sourcePod: network-check-source-65bdbbff45-g9g9z targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-05T16:49:31Z" message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 993.41µs message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:38:31Z" - latency: 1.014599ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:37:31Z" - latency: 1.420529ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:36:31Z" - latency: 1.203274ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:35:31Z" - latency: 1.062386ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:34:31Z" - latency: 884.954µs message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:33:31Z" - latency: 1.093227ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:32:31Z" - latency: 1.68633ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:31:31Z" - latency: 947.03µs message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:30:31Z" - latency: 1.905707ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:29:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T16:42:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-35-to-network-check-target-ip-10-0-132-4 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-35.ec2.internal uid: 7fba6726-bb45-44d1-b7d1-2dbfe3a4ffeb resourceVersion: "78379" uid: 98a31d06-434b-4467-b25a-f0b4b4ff2b01 spec: sourcePod: network-check-source-65bdbbff45-g9g9z targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-05T16:49:31Z" message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.892832ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:38:31Z" - latency: 2.723104ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:37:31Z" - latency: 2.321613ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:36:31Z" - latency: 2.365398ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:35:31Z" - latency: 2.519281ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:34:31Z" - latency: 2.256586ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:33:31Z" - latency: 2.367762ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:32:31Z" - latency: 2.316927ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:31:31Z" - latency: 1.987239ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:30:31Z" - latency: 2.311921ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:29:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T16:42:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-35-to-network-check-target-ip-10-0-138-233 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-35.ec2.internal uid: 7fba6726-bb45-44d1-b7d1-2dbfe3a4ffeb resourceVersion: "78381" uid: a04db90f-a053-4f72-8e72-3c8a1b423786 spec: sourcePod: network-check-source-65bdbbff45-g9g9z targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-05T16:49:31Z" message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.349347ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:38:31Z" - latency: 2.289482ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:37:31Z" - latency: 2.226464ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:36:31Z" - latency: 2.407314ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:35:31Z" - latency: 2.437002ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:34:31Z" - latency: 2.50707ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:33:31Z" - latency: 2.31874ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:32:31Z" - latency: 2.198254ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:31:31Z" - latency: 2.359227ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:30:31Z" - latency: 2.545593ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:29:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T16:42:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-35-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-35.ec2.internal uid: 7fba6726-bb45-44d1-b7d1-2dbfe3a4ffeb resourceVersion: "76406" uid: 78b6647e-30a5-4bc6-a7d3-3bc862602818 spec: sourcePod: network-check-source-65bdbbff45-g9g9z targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-05T16:48:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 904.744µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:36:31Z" - latency: 2.050617ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:36:31Z" - latency: 1.336226ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:35:31Z" - latency: 2.026316ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:35:31Z" - latency: 1.216183ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:34:31Z" - latency: 2.285588ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:34:31Z" - latency: 902.265µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:33:31Z" - latency: 1.805424ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:33:31Z" - latency: 1.355678ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:32:31Z" - latency: 1.722083ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:32:31Z" kind: List metadata: resourceVersion: ""