apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T01:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-204-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-204.ec2.internal uid: 0d33f8e9-583f-4a8b-8805-ac01434b0a29 resourceVersion: "71821" uid: 98b5d661-3bf8-4f96-a510-4bc7e71b9b95 spec: sourcePod: network-check-source-7d88cb55d8-94cj6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T01:25:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 983.35µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:07:18Z" - latency: 980.628µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:06:18Z" - latency: 1.305145ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:05:18Z" - latency: 967.168µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:04:18Z" - latency: 1.091966ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:03:18Z" - latency: 1.016819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:02:18Z" - latency: 1.052199ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:01:18Z" - latency: 975.416µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:00:18Z" - latency: 905.348µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:59:18Z" - latency: 1.050649ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:58:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T01:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-204-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-204.ec2.internal uid: 0d33f8e9-583f-4a8b-8805-ac01434b0a29 resourceVersion: "70920" uid: 3567058b-cfd8-4728-8915-749d05cee13c spec: sourcePod: network-check-source-7d88cb55d8-94cj6 targetEndpoint: af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T01:24:18Z" message: 'load-balancer-api-external: tcp connection to af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.379495ms message: 'load-balancer-api-external: tcp connection to af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:06:18Z" - latency: 9.920352ms message: 'load-balancer-api-external: resolved host name af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T02:06:18Z" - latency: 4.630751ms message: 'load-balancer-api-external: tcp connection to af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:05:18Z" - latency: 7.233719ms message: 'load-balancer-api-external: resolved host name af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T02:05:18Z" - latency: 3.88945ms message: 'load-balancer-api-external: tcp connection to af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:04:18Z" - latency: 11.986767ms message: 'load-balancer-api-external: resolved host name af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T02:04:18Z" - latency: 4.881892ms message: 'load-balancer-api-external: tcp connection to af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:03:18Z" - latency: 7.906922ms message: 'load-balancer-api-external: resolved host name af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T02:03:18Z" - latency: 4.895452ms message: 'load-balancer-api-external: tcp connection to af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:02:18Z" - latency: 7.358371ms message: 'load-balancer-api-external: resolved host name af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T02:02:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T01:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-204-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-204.ec2.internal uid: 0d33f8e9-583f-4a8b-8805-ac01434b0a29 resourceVersion: "70919" uid: d400663f-5a6e-4d91-9da7-2565c4da20f3 spec: sourcePod: network-check-source-7d88cb55d8-94cj6 targetEndpoint: af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T01:24:18Z" message: 'load-balancer-api-internal: tcp connection to af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.850511ms message: 'load-balancer-api-internal: tcp connection to af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:06:18Z" - latency: 9.945131ms message: 'load-balancer-api-internal: resolved host name af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T02:06:18Z" - latency: 5.010742ms message: 'load-balancer-api-internal: tcp connection to af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:05:18Z" - latency: 7.283796ms message: 'load-balancer-api-internal: resolved host name af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T02:05:18Z" - latency: 3.907287ms message: 'load-balancer-api-internal: tcp connection to af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:04:18Z" - latency: 12.018255ms message: 'load-balancer-api-internal: resolved host name af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T02:04:18Z" - latency: 4.963313ms message: 'load-balancer-api-internal: tcp connection to af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:03:18Z" - latency: 7.962281ms message: 'load-balancer-api-internal: resolved host name af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T02:03:18Z" - latency: 4.231159ms message: 'load-balancer-api-internal: tcp connection to af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:02:18Z" - latency: 7.38862ms message: 'load-balancer-api-internal: resolved host name af0fa804f0dde4570928948c18675e8a-65f6c99a7d6921e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T02:02:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T01:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-204-to-network-check-target-ip-10-0-133-32 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-204.ec2.internal uid: 0d33f8e9-583f-4a8b-8805-ac01434b0a29 resourceVersion: "71819" uid: e8cbea31-f7ba-4d9a-979c-44a6a8c64e1d spec: sourcePod: network-check-source-7d88cb55d8-94cj6 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T01:25:18Z" message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.385243ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:07:18Z" - latency: 2.053862ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:06:18Z" - latency: 2.558131ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:05:18Z" - latency: 2.125465ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:04:18Z" - latency: 2.413858ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:03:18Z" - latency: 2.483452ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:02:18Z" - latency: 2.535917ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:01:18Z" - latency: 2.464616ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:00:18Z" - latency: 2.452111ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:59:18Z" - latency: 2.163915ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:58:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T01:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-204-to-network-check-target-ip-10-0-136-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-204.ec2.internal uid: 0d33f8e9-583f-4a8b-8805-ac01434b0a29 resourceVersion: "71820" uid: 2ebfc052-185f-45ea-aa3d-fcca634f65b0 spec: sourcePod: network-check-source-7d88cb55d8-94cj6 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T01:25:18Z" message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.220465ms message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:07:18Z" - latency: 1.980011ms message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:06:18Z" - latency: 2.296226ms message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:05:18Z" - latency: 2.082313ms message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:04:18Z" - latency: 2.590666ms message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:03:18Z" - latency: 2.282228ms message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:02:18Z" - latency: 2.409899ms message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:01:18Z" - latency: 2.145378ms message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:00:18Z" - latency: 2.257383ms message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:59:18Z" - latency: 2.045718ms message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:58:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T01:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-204-to-network-check-target-ip-10-0-139-204 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-204.ec2.internal uid: 0d33f8e9-583f-4a8b-8805-ac01434b0a29 resourceVersion: "71818" uid: f12d8c71-a6ff-40e4-828f-b9d0ad8bffb4 spec: sourcePod: network-check-source-7d88cb55d8-94cj6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T01:25:18Z" message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.263771ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:07:18Z" - latency: 1.23417ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:06:18Z" - latency: 1.448748ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:05:18Z" - latency: 884.226µs message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:04:18Z" - latency: 970.889µs message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:03:18Z" - latency: 961.651µs message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:02:18Z" - latency: 1.369503ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:01:18Z" - latency: 865.517µs message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:00:18Z" - latency: 1.073884ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:59:18Z" - latency: 951.965µs message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:58:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T01:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-204-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-204.ec2.internal uid: 0d33f8e9-583f-4a8b-8805-ac01434b0a29 resourceVersion: "70918" uid: 751adcfb-9a86-444f-b1ca-3a85a096ea9e spec: sourcePod: network-check-source-7d88cb55d8-94cj6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T01:24:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 880.335µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:06:18Z" - latency: 2.019225ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T02:06:18Z" - latency: 920.691µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:05:18Z" - latency: 1.753261ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T02:05:18Z" - latency: 999.893µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:04:18Z" - latency: 1.658708ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T02:04:18Z" - latency: 1.355299ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:03:18Z" - latency: 1.964523ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T02:03:18Z" - latency: 787.991µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T02:02:18Z" - latency: 1.807152ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T02:02:18Z" kind: List metadata: resourceVersion: ""