apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T18:57:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-41-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-41.ec2.internal uid: 983d8456-5c51-4fb4-9113-9b8dcaf47fb8 resourceVersion: "22714" uid: 633f103e-2031-4d7f-b36a-f56a58f6b4b5 spec: sourcePod: network-check-source-65bdbbff45-zqkbv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-05T19:04:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.097744ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:04:39Z" - latency: 1.123965ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:03:39Z" - latency: 1.112723ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:02:39Z" - latency: 1.437579ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:01:39Z" - latency: 953.689µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:00:39Z" - latency: 1.098797ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:59:39Z" - latency: 1.088333ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:58:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T18:57:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-41-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-41.ec2.internal uid: 983d8456-5c51-4fb4-9113-9b8dcaf47fb8 resourceVersion: "21781" uid: e29d5adc-471c-44c3-948f-57bf6068c0ab spec: sourcePod: network-check-source-65bdbbff45-zqkbv targetEndpoint: ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T19:03:39Z" message: 'load-balancer-api-external: tcp connection to ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.33973ms message: 'load-balancer-api-external: tcp connection to ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:03:39Z" - latency: 6.804297ms message: 'load-balancer-api-external: resolved host name ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T19:03:39Z" - latency: 6.282312ms message: 'load-balancer-api-external: tcp connection to ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:02:39Z" - latency: 9.452356ms message: 'load-balancer-api-external: resolved host name ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T19:02:39Z" - latency: 5.407819ms message: 'load-balancer-api-external: tcp connection to ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:01:39Z" - latency: 9.319364ms message: 'load-balancer-api-external: resolved host name ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T19:01:39Z" - latency: 4.698642ms message: 'load-balancer-api-external: tcp connection to ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:00:39Z" - latency: 7.525657ms message: 'load-balancer-api-external: resolved host name ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T19:00:39Z" - latency: 5.171629ms message: 'load-balancer-api-external: tcp connection to ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:59:39Z" - latency: 8.53955ms message: 'load-balancer-api-external: resolved host name ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:59:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T18:57:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-41-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-41.ec2.internal uid: 983d8456-5c51-4fb4-9113-9b8dcaf47fb8 resourceVersion: "21780" uid: 364159f7-75e1-47ee-8a79-e9a5d42655a6 spec: sourcePod: network-check-source-65bdbbff45-zqkbv targetEndpoint: ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T19:03:39Z" message: 'load-balancer-api-internal: tcp connection to ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.359493ms message: 'load-balancer-api-internal: tcp connection to ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:03:39Z" - latency: 6.851395ms message: 'load-balancer-api-internal: resolved host name ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T19:03:39Z" - latency: 3.64689ms message: 'load-balancer-api-internal: tcp connection to ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:02:39Z" - latency: 9.331608ms message: 'load-balancer-api-internal: resolved host name ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T19:02:39Z" - latency: 5.553142ms message: 'load-balancer-api-internal: tcp connection to ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:01:39Z" - latency: 9.164239ms message: 'load-balancer-api-internal: resolved host name ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T19:01:39Z" - latency: 5.439075ms message: 'load-balancer-api-internal: tcp connection to ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:00:39Z" - latency: 7.431533ms message: 'load-balancer-api-internal: resolved host name ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T19:00:39Z" - latency: 5.277164ms message: 'load-balancer-api-internal: tcp connection to ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:59:39Z" - latency: 9.18611ms message: 'load-balancer-api-internal: resolved host name ae36f5acd19e649709cd6d10d4749069-ad3d4244e98dc9b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:59:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T18:57:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-41-to-network-check-target-ip-10-0-138-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-41.ec2.internal uid: 983d8456-5c51-4fb4-9113-9b8dcaf47fb8 resourceVersion: "22713" uid: e491fc79-7354-44be-a633-d64136b2193d spec: sourcePod: network-check-source-65bdbbff45-zqkbv targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-05T19:04:39Z" message: 'network-check-target-ip-10-0-138-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.423434ms message: 'network-check-target-ip-10-0-138-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:04:39Z" - latency: 2.145626ms message: 'network-check-target-ip-10-0-138-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:03:39Z" - latency: 2.30111ms message: 'network-check-target-ip-10-0-138-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:02:39Z" - latency: 2.960254ms message: 'network-check-target-ip-10-0-138-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:01:39Z" - latency: 2.102744ms message: 'network-check-target-ip-10-0-138-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:00:39Z" - latency: 2.345734ms message: 'network-check-target-ip-10-0-138-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:59:39Z" - latency: 2.55652ms message: 'network-check-target-ip-10-0-138-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:58:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T18:57:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-41-to-network-check-target-ip-10-0-139-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-41.ec2.internal uid: 983d8456-5c51-4fb4-9113-9b8dcaf47fb8 resourceVersion: "22712" uid: 495d9754-44da-4d9e-ba27-dece015880be spec: sourcePod: network-check-source-65bdbbff45-zqkbv targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-05T19:04:39Z" message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.514993ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:04:39Z" - latency: 2.151055ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:03:39Z" - latency: 2.838366ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:02:39Z" - latency: 2.367434ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:01:39Z" - latency: 2.631295ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:00:39Z" - latency: 2.483611ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:59:39Z" - latency: 2.315946ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:58:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T18:57:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-41-to-network-check-target-ip-10-0-141-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-41.ec2.internal uid: 983d8456-5c51-4fb4-9113-9b8dcaf47fb8 resourceVersion: "22711" uid: 5dda43ce-d63c-45bb-80be-a80d7b6cf1ef spec: sourcePod: network-check-source-65bdbbff45-zqkbv targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-05T19:04:39Z" message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 950.77µs message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:04:39Z" - latency: 921.536µs message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:03:39Z" - latency: 1.249047ms message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:02:39Z" - latency: 915.777µs message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:01:39Z" - latency: 793.293µs message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:00:39Z" - latency: 1.030036ms message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:59:39Z" - latency: 1.624433ms message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:58:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T18:57:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-41-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-41.ec2.internal uid: 983d8456-5c51-4fb4-9113-9b8dcaf47fb8 resourceVersion: "21779" uid: 68c5e1b3-a978-41ab-a706-ab0c9e592a85 spec: sourcePod: network-check-source-65bdbbff45-zqkbv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-05T19:03:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.006098ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:03:39Z" - latency: 1.902323ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T19:03:39Z" - latency: 1.104401ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:02:39Z" - latency: 1.850422ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T19:02:39Z" - latency: 933.419µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:01:39Z" - latency: 1.999063ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T19:01:39Z" - latency: 849.502µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T19:00:39Z" - latency: 1.807732ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T19:00:39Z" - latency: 790.028µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:59:39Z" - latency: 2.307097ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:59:39Z" kind: List metadata: resourceVersion: ""