apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:03:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-239-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-239.ec2.internal uid: 684d1638-924d-41e3-a234-198cdb6bd6a5 resourceVersion: "32269" uid: 78674ad4-ad41-4d52-87ea-1f1dcd1568e0 spec: sourcePod: network-check-source-65bdbbff45-mrq5b targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T18:10:46Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.474918ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:46Z" - latency: 1.548618ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:46Z" - latency: 1.001874ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:46Z" - latency: 1.075292ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:46Z" - latency: 843.232µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:46Z" - latency: 1.215594ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:40:46Z" - latency: 1.104067ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:39:46Z" - latency: 844.588µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:38:46Z" - latency: 1.241189ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:37:46Z" - latency: 1.047337ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:36:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:03:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-239-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-239.ec2.internal uid: 684d1638-924d-41e3-a234-198cdb6bd6a5 resourceVersion: "32271" uid: e6996373-cc75-4778-a1a0-f55dc63b00cd spec: sourcePod: network-check-source-65bdbbff45-mrq5b targetEndpoint: a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T18:09:46Z" message: 'load-balancer-api-external: tcp connection to a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.557598ms message: 'load-balancer-api-external: tcp connection to a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:46Z" - latency: 6.428231ms message: 'load-balancer-api-external: resolved host name a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:45:46Z" - latency: 5.090428ms message: 'load-balancer-api-external: tcp connection to a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:46Z" - latency: 7.091215ms message: 'load-balancer-api-external: resolved host name a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:44:46Z" - latency: 5.260769ms message: 'load-balancer-api-external: tcp connection to a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:46Z" - latency: 6.590304ms message: 'load-balancer-api-external: resolved host name a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:43:46Z" - latency: 5.960783ms message: 'load-balancer-api-external: tcp connection to a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:46Z" - latency: 7.067577ms message: 'load-balancer-api-external: resolved host name a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:42:46Z" - latency: 5.705344ms message: 'load-balancer-api-external: tcp connection to a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:46Z" - latency: 7.059226ms message: 'load-balancer-api-external: resolved host name a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:41:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:03:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-239-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-239.ec2.internal uid: 684d1638-924d-41e3-a234-198cdb6bd6a5 resourceVersion: "32270" uid: 3d8439aa-6b74-4aa1-a74c-92c886d71551 spec: sourcePod: network-check-source-65bdbbff45-mrq5b targetEndpoint: a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T18:09:46Z" message: 'load-balancer-api-internal: tcp connection to a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.330826ms message: 'load-balancer-api-internal: tcp connection to a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:46Z" - latency: 6.385061ms message: 'load-balancer-api-internal: resolved host name a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:45:46Z" - latency: 5.353859ms message: 'load-balancer-api-internal: tcp connection to a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:46Z" - latency: 7.102129ms message: 'load-balancer-api-internal: resolved host name a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:44:46Z" - latency: 5.280124ms message: 'load-balancer-api-internal: tcp connection to a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:46Z" - latency: 6.624375ms message: 'load-balancer-api-internal: resolved host name a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:43:46Z" - latency: 6.003262ms message: 'load-balancer-api-internal: tcp connection to a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:46Z" - latency: 7.026881ms message: 'load-balancer-api-internal: resolved host name a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:42:46Z" - latency: 5.683376ms message: 'load-balancer-api-internal: tcp connection to a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:46Z" - latency: 7.03048ms message: 'load-balancer-api-internal: resolved host name a0572de9682204ec6bb24bd472a45258-e9a9885e38ad745f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:41:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:03:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-239-to-network-check-target-ip-10-0-128-114 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-239.ec2.internal uid: 684d1638-924d-41e3-a234-198cdb6bd6a5 resourceVersion: "32267" uid: 215583cb-6e6b-49c0-a18c-8ac6438eff36 spec: sourcePod: network-check-source-65bdbbff45-mrq5b targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:10:46Z" message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.879278ms message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:46Z" - latency: 1.852353ms message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:46Z" - latency: 1.625275ms message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:46Z" - latency: 1.835599ms message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:46Z" - latency: 1.475701ms message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:46Z" - latency: 1.772815ms message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:40:46Z" - latency: 1.662268ms message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:39:46Z" - latency: 1.808256ms message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:38:46Z" - latency: 2.12137ms message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:37:46Z" - latency: 1.82206ms message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:36:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:03:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-239-to-network-check-target-ip-10-0-133-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-239.ec2.internal uid: 684d1638-924d-41e3-a234-198cdb6bd6a5 resourceVersion: "32266" uid: b46acce3-d612-4453-b40d-0723a734e7bc spec: sourcePod: network-check-source-65bdbbff45-mrq5b targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:10:46Z" message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.941958ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:46Z" - latency: 2.268881ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:46Z" - latency: 1.851687ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:46Z" - latency: 2.379726ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:46Z" - latency: 2.131995ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:46Z" - latency: 1.923164ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:40:46Z" - latency: 2.228939ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:39:46Z" - latency: 2.123521ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:38:46Z" - latency: 2.199835ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:37:46Z" - latency: 2.390784ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:36:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:03:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-239-to-network-check-target-ip-10-0-136-239 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-239.ec2.internal uid: 684d1638-924d-41e3-a234-198cdb6bd6a5 resourceVersion: "32264" uid: c5329be1-3756-4488-805d-f8db32a2ec6c spec: sourcePod: network-check-source-65bdbbff45-mrq5b targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:10:46Z" message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.01197ms message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:46Z" - latency: 1.297434ms message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:46Z" - latency: 808.054µs message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:46Z" - latency: 918.956µs message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:46Z" - latency: 1.131373ms message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:46Z" - latency: 830.968µs message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:40:46Z" - latency: 766.068µs message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:39:46Z" - latency: 847.061µs message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:38:46Z" - latency: 814.198µs message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:37:46Z" - latency: 1.167928ms message: 'network-check-target-ip-10-0-136-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:36:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:03:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-239-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-239.ec2.internal uid: 684d1638-924d-41e3-a234-198cdb6bd6a5 resourceVersion: "32265" uid: 30116dd5-781d-4536-b96f-21040863d281 spec: sourcePod: network-check-source-65bdbbff45-mrq5b targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T18:09:46Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 866.414µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:46Z" - latency: 1.589646ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:45:46Z" - latency: 980.629µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:46Z" - latency: 2.181729ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:44:46Z" - latency: 873.019µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:46Z" - latency: 1.908735ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:43:46Z" - latency: 799.975µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:46Z" - latency: 2.091122ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:42:46Z" - latency: 1.097273ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:46Z" - latency: 1.761975ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:41:46Z" kind: List metadata: resourceVersion: ""