apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:19:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-241-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-241.ec2.internal uid: b4d973d0-93bc-474e-906c-8666c1ff8dc8 resourceVersion: "44076" uid: a79f53d8-6d3f-4e09-9705-c886c1066fbb spec: sourcePod: network-check-source-7f44b6dd87-zt57r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T15:26:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 929.287µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:47:03Z" - latency: 934.436µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:46:03Z" - latency: 1.112037ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:45:03Z" - latency: 893.032µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:44:03Z" - latency: 931.284µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:43:03Z" - latency: 1.096478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:42:03Z" - latency: 765.398µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:41:03Z" - latency: 894.181µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:40:03Z" - latency: 990.614µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:39:03Z" - latency: 827.121µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:38:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:19:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-241-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-241.ec2.internal uid: b4d973d0-93bc-474e-906c-8666c1ff8dc8 resourceVersion: "46110" uid: 039799a7-e56b-44db-af1a-ae82b12bd873 spec: sourcePod: network-check-source-7f44b6dd87-zt57r targetEndpoint: a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T15:25:03Z" message: 'load-balancer-api-external: tcp connection to a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 9.599948ms message: 'load-balancer-api-external: tcp connection to a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:49:03Z" - latency: 6.652655ms message: 'load-balancer-api-external: resolved host name a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:49:03Z" - latency: 4.312463ms message: 'load-balancer-api-external: tcp connection to a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:48:03Z" - latency: 6.583536ms message: 'load-balancer-api-external: resolved host name a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:48:03Z" - latency: 3.669818ms message: 'load-balancer-api-external: tcp connection to a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:47:03Z" - latency: 6.338149ms message: 'load-balancer-api-external: resolved host name a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:47:03Z" - latency: 7.91725ms message: 'load-balancer-api-external: tcp connection to a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:46:03Z" - latency: 6.656504ms message: 'load-balancer-api-external: resolved host name a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:46:03Z" - latency: 6.827046ms message: 'load-balancer-api-external: tcp connection to a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:45:03Z" - latency: 6.855129ms message: 'load-balancer-api-external: resolved host name a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:45:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:19:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-241-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-241.ec2.internal uid: b4d973d0-93bc-474e-906c-8666c1ff8dc8 resourceVersion: "46109" uid: 3d302629-83fe-4bec-9e3c-20055fa295aa spec: sourcePod: network-check-source-7f44b6dd87-zt57r targetEndpoint: a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T15:25:03Z" message: 'load-balancer-api-internal: tcp connection to a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.95302ms message: 'load-balancer-api-internal: tcp connection to a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:49:03Z" - latency: 6.717028ms message: 'load-balancer-api-internal: resolved host name a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:49:03Z" - latency: 5.765427ms message: 'load-balancer-api-internal: tcp connection to a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:48:03Z" - latency: 6.655705ms message: 'load-balancer-api-internal: resolved host name a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:48:03Z" - latency: 3.662082ms message: 'load-balancer-api-internal: tcp connection to a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:47:03Z" - latency: 6.24069ms message: 'load-balancer-api-internal: resolved host name a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:47:03Z" - latency: 3.945387ms message: 'load-balancer-api-internal: tcp connection to a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:46:03Z" - latency: 6.685423ms message: 'load-balancer-api-internal: resolved host name a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:46:03Z" - latency: 5.848529ms message: 'load-balancer-api-internal: tcp connection to a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:45:03Z" - latency: 6.901743ms message: 'load-balancer-api-internal: resolved host name a97ce3b9fc97e4a0f91646d6e7ac2f57-d8981479ec78b5db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:45:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:19:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-241-to-network-check-target-ip-10-0-134-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-241.ec2.internal uid: b4d973d0-93bc-474e-906c-8666c1ff8dc8 resourceVersion: "44074" uid: 94e009d1-7a35-439b-b629-e9943214ca7f spec: sourcePod: network-check-source-7f44b6dd87-zt57r targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T15:26:03Z" message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.235313ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:47:03Z" - latency: 2.575577ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:46:03Z" - latency: 2.44379ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:45:03Z" - latency: 2.677831ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:44:03Z" - latency: 2.681168ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:43:03Z" - latency: 2.00577ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:42:03Z" - latency: 1.588499ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:41:03Z" - latency: 2.272101ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:40:03Z" - latency: 2.05446ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:39:03Z" - latency: 2.293603ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:38:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:19:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-241-to-network-check-target-ip-10-0-137-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-241.ec2.internal uid: b4d973d0-93bc-474e-906c-8666c1ff8dc8 resourceVersion: "44073" uid: 47e99642-0c55-49ee-a93a-3ae3b36c3615 spec: sourcePod: network-check-source-7f44b6dd87-zt57r targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-21T15:26:03Z" message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 858.718µs message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:47:03Z" - latency: 863.221µs message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:46:03Z" - latency: 929.321µs message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:45:03Z" - latency: 900.023µs message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:44:03Z" - latency: 897.365µs message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:43:03Z" - latency: 855.424µs message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:42:03Z" - latency: 1.087091ms message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:41:03Z" - latency: 1.263441ms message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:40:03Z" - latency: 890.574µs message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:39:03Z" - latency: 994.877µs message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:38:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:19:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-241-to-network-check-target-ip-10-0-142-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-241.ec2.internal uid: b4d973d0-93bc-474e-906c-8666c1ff8dc8 resourceVersion: "44075" uid: 94c316b8-406c-4208-90e7-7f15ce4a3136 spec: sourcePod: network-check-source-7f44b6dd87-zt57r targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T15:26:03Z" message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.089812ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:47:03Z" - latency: 2.185495ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:46:03Z" - latency: 2.401849ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:45:03Z" - latency: 2.23255ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:44:03Z" - latency: 2.382799ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:43:03Z" - latency: 2.103352ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:42:03Z" - latency: 2.085415ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:41:03Z" - latency: 2.330923ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:40:03Z" - latency: 2.158379ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:39:03Z" - latency: 2.252963ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:38:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:19:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-241-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-241.ec2.internal uid: b4d973d0-93bc-474e-906c-8666c1ff8dc8 resourceVersion: "46108" uid: 2bdad363-8e5e-4066-a0bb-24abb9d2cd55 spec: sourcePod: network-check-source-7f44b6dd87-zt57r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T15:25:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 836.107µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:49:03Z" - latency: 2.408996ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:49:03Z" - latency: 977.288µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:48:03Z" - latency: 1.746103ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:48:03Z" - latency: 1.163429ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:47:03Z" - latency: 1.828166ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:47:03Z" - latency: 1.148897ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:46:03Z" - latency: 1.669865ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:46:03Z" - latency: 844.703µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:45:03Z" - latency: 1.8269ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:45:03Z" kind: List metadata: resourceVersion: ""