apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T03:16:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 3af0a1a0-d0e9-40cc-94f2-f78b0ee94d05 resourceVersion: "76254" uid: 11d09f47-c2bb-4e74-8869-ffcd6a3ee37a spec: sourcePod: network-check-source-65bdbbff45-2v2qn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T03:23:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.021447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:12:02Z" - latency: 1.056323ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:11:02Z" - latency: 1.3066ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:10:02Z" - latency: 965.331µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:09:02Z" - latency: 1.216166ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:08:02Z" - latency: 1.329074ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:07:02Z" - latency: 1.554283ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:06:02Z" - latency: 1.229078ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:05:02Z" - latency: 1.273285ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:04:02Z" - latency: 1.238563ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:03:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T03:16:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 3af0a1a0-d0e9-40cc-94f2-f78b0ee94d05 resourceVersion: "80574" uid: e7d25c08-82a3-4241-8fb8-d4999c2654f5 spec: sourcePod: network-check-source-65bdbbff45-2v2qn targetEndpoint: a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T03:22:02Z" message: 'load-balancer-api-external: tcp connection to a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.364039ms message: 'load-balancer-api-external: tcp connection to a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:16:02Z" - latency: 8.28744ms message: 'load-balancer-api-external: resolved host name a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T04:16:02Z" - latency: 3.76991ms message: 'load-balancer-api-external: tcp connection to a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:15:02Z" - latency: 8.588406ms message: 'load-balancer-api-external: resolved host name a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T04:15:02Z" - latency: 5.203361ms message: 'load-balancer-api-external: tcp connection to a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:14:02Z" - latency: 8.356701ms message: 'load-balancer-api-external: resolved host name a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T04:14:02Z" - latency: 3.702983ms message: 'load-balancer-api-external: tcp connection to a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:13:02Z" - latency: 8.8692ms message: 'load-balancer-api-external: resolved host name a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T04:13:02Z" - latency: 4.89195ms message: 'load-balancer-api-external: tcp connection to a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:12:02Z" - latency: 9.044112ms message: 'load-balancer-api-external: resolved host name a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T04:12:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T03:16:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 3af0a1a0-d0e9-40cc-94f2-f78b0ee94d05 resourceVersion: "80575" uid: c1a1b215-73e4-48c2-9890-6a1d4315c359 spec: sourcePod: network-check-source-65bdbbff45-2v2qn targetEndpoint: a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T03:22:02Z" message: 'load-balancer-api-internal: tcp connection to a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.848104ms message: 'load-balancer-api-internal: tcp connection to a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:16:02Z" - latency: 8.232863ms message: 'load-balancer-api-internal: resolved host name a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T04:16:02Z" - latency: 3.803832ms message: 'load-balancer-api-internal: tcp connection to a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:15:02Z" - latency: 8.50512ms message: 'load-balancer-api-internal: resolved host name a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T04:15:02Z" - latency: 4.661057ms message: 'load-balancer-api-internal: tcp connection to a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:14:02Z" - latency: 8.236182ms message: 'load-balancer-api-internal: resolved host name a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T04:14:02Z" - latency: 4.924512ms message: 'load-balancer-api-internal: tcp connection to a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:13:02Z" - latency: 8.807295ms message: 'load-balancer-api-internal: resolved host name a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T04:13:02Z" - latency: 4.894282ms message: 'load-balancer-api-internal: tcp connection to a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:12:02Z" - latency: 8.927273ms message: 'load-balancer-api-internal: resolved host name a928a260e6f9e4df5aadd22960c00c99-9b5a0f80d5ec4073.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T04:12:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T03:16:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-network-check-target-ip-10-0-130-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 3af0a1a0-d0e9-40cc-94f2-f78b0ee94d05 resourceVersion: "76252" uid: 6f179447-ecc0-41bf-8edc-d6909706b4d3 spec: sourcePod: network-check-source-65bdbbff45-2v2qn targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T03:23:02Z" message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.092031ms message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:12:02Z" - latency: 2.433065ms message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:11:02Z" - latency: 2.2897ms message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:10:02Z" - latency: 2.140211ms message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:09:02Z" - latency: 2.58486ms message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:08:02Z" - latency: 2.597459ms message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:07:02Z" - latency: 2.33738ms message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:06:02Z" - latency: 2.369262ms message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:05:02Z" - latency: 2.730552ms message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:04:02Z" - latency: 2.388789ms message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:03:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T03:16:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-network-check-target-ip-10-0-134-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 3af0a1a0-d0e9-40cc-94f2-f78b0ee94d05 resourceVersion: "76253" uid: 1b9dc025-4cb9-4500-a3c9-bfedaf041ad9 spec: sourcePod: network-check-source-65bdbbff45-2v2qn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T03:23:02Z" message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.405891ms message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:12:02Z" - latency: 2.450728ms message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:11:02Z" - latency: 2.457216ms message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:10:02Z" - latency: 2.365151ms message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:09:02Z" - latency: 2.224097ms message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:08:02Z" - latency: 3.133002ms message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:07:02Z" - latency: 2.260811ms message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:06:02Z" - latency: 2.314494ms message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:05:02Z" - latency: 2.514478ms message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:04:02Z" - latency: 2.462004ms message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:03:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T03:16:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-network-check-target-ip-10-0-138-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 3af0a1a0-d0e9-40cc-94f2-f78b0ee94d05 resourceVersion: "76251" uid: 3987d54d-60f8-4361-b5ee-0059f20a1281 spec: sourcePod: network-check-source-65bdbbff45-2v2qn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T03:23:02Z" message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 811.278µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:12:02Z" - latency: 1.084656ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:11:02Z" - latency: 1.174651ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:10:02Z" - latency: 1.002023ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:09:02Z" - latency: 969.235µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:08:02Z" - latency: 1.295928ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:07:02Z" - latency: 1.089832ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:06:02Z" - latency: 992.462µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:05:02Z" - latency: 910.779µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:04:02Z" - latency: 915.962µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:03:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T03:16:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 3af0a1a0-d0e9-40cc-94f2-f78b0ee94d05 resourceVersion: "80573" uid: daabc80a-9917-44af-8e58-cf9fc0724b36 spec: sourcePod: network-check-source-65bdbbff45-2v2qn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T03:22:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.161478ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:16:02Z" - latency: 1.888961ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T04:16:02Z" - latency: 847.141µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:15:02Z" - latency: 1.756389ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T04:15:02Z" - latency: 865.221µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:14:02Z" - latency: 1.939735ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T04:14:02Z" - latency: 1.22561ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:13:02Z" - latency: 1.776539ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T04:13:02Z" - latency: 998.37µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T04:12:02Z" - latency: 1.632952ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T04:12:02Z" kind: List metadata: resourceVersion: ""