apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:28:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-158-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-158.ec2.internal uid: fa79e56a-d29f-4961-b326-04a6f7075ba1 resourceVersion: "32215" uid: 31342184-09ee-4095-9120-beda074ec7cb spec: sourcePod: network-check-source-7d88cb55d8-jxrbq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T01:35:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 905.499µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:10:37Z" - latency: 823.492µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:09:37Z" - latency: 754.256µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:08:37Z" - latency: 1.25144ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:07:37Z" - latency: 848.337µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:06:37Z" - latency: 873.831µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:05:37Z" - latency: 806.478µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:04:37Z" - latency: 1.324331ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:03:37Z" - latency: 1.335114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:02:37Z" - latency: 805.684µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:01:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:28:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-158-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-158.ec2.internal uid: fa79e56a-d29f-4961-b326-04a6f7075ba1 resourceVersion: "32216" uid: cfad12fb-17ef-423f-a752-81b42933deb5 spec: sourcePod: network-check-source-7d88cb55d8-jxrbq targetEndpoint: abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T01:34:37Z" message: 'load-balancer-api-external: tcp connection to abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.787063ms message: 'load-balancer-api-external: tcp connection to abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:10:37Z" - latency: 8.066796ms message: 'load-balancer-api-external: resolved host name abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T02:10:37Z" - latency: 5.252058ms message: 'load-balancer-api-external: tcp connection to abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:09:37Z" - latency: 8.389765ms message: 'load-balancer-api-external: resolved host name abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T02:09:37Z" - latency: 5.132007ms message: 'load-balancer-api-external: tcp connection to abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:08:37Z" - latency: 8.186034ms message: 'load-balancer-api-external: resolved host name abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T02:08:37Z" - latency: 4.466049ms message: 'load-balancer-api-external: tcp connection to abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:07:37Z" - latency: 7.721823ms message: 'load-balancer-api-external: resolved host name abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T02:07:37Z" - latency: 3.927977ms message: 'load-balancer-api-external: tcp connection to abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:06:37Z" - latency: 8.028437ms message: 'load-balancer-api-external: resolved host name abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T02:06:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:28:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-158-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-158.ec2.internal uid: fa79e56a-d29f-4961-b326-04a6f7075ba1 resourceVersion: "32217" uid: 563d9ba0-17a5-4e91-b4ca-749be219003c spec: sourcePod: network-check-source-7d88cb55d8-jxrbq targetEndpoint: abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T01:34:37Z" message: 'load-balancer-api-internal: tcp connection to abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.775339ms message: 'load-balancer-api-internal: tcp connection to abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:10:37Z" - latency: 8.151066ms message: 'load-balancer-api-internal: resolved host name abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T02:10:37Z" - latency: 5.288659ms message: 'load-balancer-api-internal: tcp connection to abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:09:37Z" - latency: 8.46114ms message: 'load-balancer-api-internal: resolved host name abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T02:09:37Z" - latency: 5.108563ms message: 'load-balancer-api-internal: tcp connection to abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:08:37Z" - latency: 8.213066ms message: 'load-balancer-api-internal: resolved host name abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T02:08:37Z" - latency: 4.433392ms message: 'load-balancer-api-internal: tcp connection to abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:07:37Z" - latency: 7.796325ms message: 'load-balancer-api-internal: resolved host name abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T02:07:37Z" - latency: 4.080094ms message: 'load-balancer-api-internal: tcp connection to abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:06:37Z" - latency: 8.087467ms message: 'load-balancer-api-internal: resolved host name abfdeaa54894c4872906323206178fb3-49b95d0ab406a7e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T02:06:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:28:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-158-to-network-check-target-ip-10-0-134-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-158.ec2.internal uid: fa79e56a-d29f-4961-b326-04a6f7075ba1 resourceVersion: "32214" uid: c2f6d416-d078-4f90-9497-d4874160e823 spec: sourcePod: network-check-source-7d88cb55d8-jxrbq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T01:35:37Z" message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.28083ms message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:10:37Z" - latency: 2.103415ms message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:09:37Z" - latency: 1.593086ms message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:08:37Z" - latency: 2.056113ms message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:07:37Z" - latency: 2.701475ms message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:06:37Z" - latency: 1.829162ms message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:05:37Z" - latency: 1.881221ms message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:04:37Z" - latency: 1.991025ms message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:03:37Z" - latency: 1.677585ms message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:02:37Z" - latency: 2.032136ms message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:01:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:28:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-158-to-network-check-target-ip-10-0-134-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-158.ec2.internal uid: fa79e56a-d29f-4961-b326-04a6f7075ba1 resourceVersion: "32211" uid: f325f1f6-3996-4538-b6f2-6e18bb5b2727 spec: sourcePod: network-check-source-7d88cb55d8-jxrbq targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T01:35:37Z" message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.299445ms message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:10:37Z" - latency: 771.902µs message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:09:37Z" - latency: 714.394µs message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:08:37Z" - latency: 729.122µs message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:07:37Z" - latency: 712.573µs message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:06:37Z" - latency: 746.049µs message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:05:37Z" - latency: 1.028991ms message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:04:37Z" - latency: 890.397µs message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:03:37Z" - latency: 868.338µs message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:02:37Z" - latency: 843.68µs message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:01:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:28:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-158-to-network-check-target-ip-10-0-142-30 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-158.ec2.internal uid: fa79e56a-d29f-4961-b326-04a6f7075ba1 resourceVersion: "32213" uid: 34112550-d76c-483d-be53-87b85cf54b27 spec: sourcePod: network-check-source-7d88cb55d8-jxrbq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T01:35:37Z" message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.459658ms message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:10:37Z" - latency: 1.823151ms message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:09:37Z" - latency: 1.641626ms message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:08:37Z" - latency: 1.776297ms message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:07:37Z" - latency: 2.081444ms message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:06:37Z" - latency: 1.82126ms message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:05:37Z" - latency: 1.857547ms message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:04:37Z" - latency: 1.867024ms message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:03:37Z" - latency: 1.697547ms message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:02:37Z" - latency: 1.733565ms message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:01:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:28:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-158-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-158.ec2.internal uid: fa79e56a-d29f-4961-b326-04a6f7075ba1 resourceVersion: "32212" uid: 5b23c657-a878-4b7b-8b3e-8bf1019d4c00 spec: sourcePod: network-check-source-7d88cb55d8-jxrbq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T01:34:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 880.742µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:10:37Z" - latency: 1.657576ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T02:10:37Z" - latency: 766.55µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:09:37Z" - latency: 1.900467ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T02:09:37Z" - latency: 907.865µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:08:37Z" - latency: 1.642673ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T02:08:37Z" - latency: 783.34µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:07:37Z" - latency: 1.866874ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T02:07:37Z" - latency: 1.054003ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T02:06:37Z" - latency: 1.58284ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T02:06:37Z" kind: List metadata: resourceVersion: ""