apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:49:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-58-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-58.ec2.internal uid: d681d62c-2033-4a1c-b3ae-b9c11fe90965 resourceVersion: "65387" uid: 0710cfa4-ed59-4812-af3e-2bf68c94201f spec: sourcePod: network-check-source-7d88cb55d8-xg7vg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T15:56:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.307953ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:31:43Z" - latency: 1.174213ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:30:43Z" - latency: 1.383004ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:29:43Z" - latency: 1.0093ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:28:43Z" - latency: 1.151186ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:27:43Z" - latency: 1.396528ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:26:43Z" - latency: 1.479674ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:25:43Z" - latency: 1.166239ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:24:43Z" - latency: 1.022048ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:23:43Z" - latency: 1.283911ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:22:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:49:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-58-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-58.ec2.internal uid: d681d62c-2033-4a1c-b3ae-b9c11fe90965 resourceVersion: "65390" uid: ddfdba44-1fe2-495c-a7ce-463e24d49c74 spec: sourcePod: network-check-source-7d88cb55d8-xg7vg targetEndpoint: ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T15:55:43Z" message: 'load-balancer-api-external: tcp connection to ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.214517ms message: 'load-balancer-api-external: tcp connection to ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:31:43Z" - latency: 8.188281ms message: 'load-balancer-api-external: resolved host name ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:31:43Z" - latency: 4.142072ms message: 'load-balancer-api-external: tcp connection to ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:30:43Z" - latency: 11.098979ms message: 'load-balancer-api-external: resolved host name ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:30:43Z" - latency: 6.502321ms message: 'load-balancer-api-external: tcp connection to ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:29:43Z" - latency: 10.401468ms message: 'load-balancer-api-external: resolved host name ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:29:43Z" - latency: 4.81522ms message: 'load-balancer-api-external: tcp connection to ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:28:43Z" - latency: 8.801901ms message: 'load-balancer-api-external: resolved host name ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:28:43Z" - latency: 4.783077ms message: 'load-balancer-api-external: tcp connection to ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:27:43Z" - latency: 8.94753ms message: 'load-balancer-api-external: resolved host name ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:27:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:49:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-58-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-58.ec2.internal uid: d681d62c-2033-4a1c-b3ae-b9c11fe90965 resourceVersion: "65389" uid: d6826748-51e2-4675-978b-b349449d7232 spec: sourcePod: network-check-source-7d88cb55d8-xg7vg targetEndpoint: ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T15:55:43Z" message: 'load-balancer-api-internal: tcp connection to ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.690562ms message: 'load-balancer-api-internal: tcp connection to ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:31:43Z" - latency: 8.086361ms message: 'load-balancer-api-internal: resolved host name ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:31:43Z" - latency: 4.150199ms message: 'load-balancer-api-internal: tcp connection to ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:30:43Z" - latency: 10.990987ms message: 'load-balancer-api-internal: resolved host name ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:30:43Z" - latency: 6.493116ms message: 'load-balancer-api-internal: tcp connection to ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:29:43Z" - latency: 10.348689ms message: 'load-balancer-api-internal: resolved host name ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:29:43Z" - latency: 4.826284ms message: 'load-balancer-api-internal: tcp connection to ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:28:43Z" - latency: 8.729691ms message: 'load-balancer-api-internal: resolved host name ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:28:43Z" - latency: 4.816823ms message: 'load-balancer-api-internal: tcp connection to ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:27:43Z" - latency: 8.875336ms message: 'load-balancer-api-internal: resolved host name ad265b96dcc204b30b59776a4414620e-69079ac7e1b7a4a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:27:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:49:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-58-to-network-check-target-ip-10-0-133-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-58.ec2.internal uid: d681d62c-2033-4a1c-b3ae-b9c11fe90965 resourceVersion: "65385" uid: 7c31bbd1-ca84-4b55-8182-5dd5b769ee16 spec: sourcePod: network-check-source-7d88cb55d8-xg7vg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T15:56:43Z" message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.505446ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:31:43Z" - latency: 2.331408ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:30:43Z" - latency: 2.2501ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:29:43Z" - latency: 2.1667ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:28:43Z" - latency: 2.467155ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:27:43Z" - latency: 2.352343ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:26:43Z" - latency: 1.975444ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:25:43Z" - latency: 2.563409ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:24:43Z" - latency: 2.37276ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:23:43Z" - latency: 2.386871ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:22:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:49:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-58-to-network-check-target-ip-10-0-134-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-58.ec2.internal uid: d681d62c-2033-4a1c-b3ae-b9c11fe90965 resourceVersion: "65386" uid: c69b9aa7-3916-4548-ac69-b3ba2820c03c spec: sourcePod: network-check-source-7d88cb55d8-xg7vg targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T15:56:43Z" message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.518902ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:31:43Z" - latency: 2.437593ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:30:43Z" - latency: 2.76891ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:29:43Z" - latency: 2.647729ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:28:43Z" - latency: 2.103391ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:27:43Z" - latency: 2.237294ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:26:43Z" - latency: 2.335368ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:25:43Z" - latency: 2.186809ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:24:43Z" - latency: 2.352331ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:23:43Z" - latency: 2.440378ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:22:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:49:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-58-to-network-check-target-ip-10-0-141-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-58.ec2.internal uid: d681d62c-2033-4a1c-b3ae-b9c11fe90965 resourceVersion: "65383" uid: fb751f90-a0dd-4ca9-a727-6aea6b825af9 spec: sourcePod: network-check-source-7d88cb55d8-xg7vg targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T15:56:43Z" message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.255042ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:31:43Z" - latency: 1.356612ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:30:43Z" - latency: 1.280267ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:29:43Z" - latency: 1.005169ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:28:43Z" - latency: 1.356179ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:27:43Z" - latency: 893.027µs message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:26:43Z" - latency: 1.317394ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:25:43Z" - latency: 999.022µs message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:24:43Z" - latency: 1.341056ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:23:43Z" - latency: 1.682808ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:22:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:49:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-58-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-58.ec2.internal uid: d681d62c-2033-4a1c-b3ae-b9c11fe90965 resourceVersion: "65384" uid: 073ecf50-0a1d-455c-a394-fa46f6a2682d spec: sourcePod: network-check-source-7d88cb55d8-xg7vg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T15:55:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.081847ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:31:43Z" - latency: 1.56367ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:31:43Z" - latency: 986.719µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:30:43Z" - latency: 1.907565ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:30:43Z" - latency: 946.613µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:29:43Z" - latency: 1.898326ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:29:43Z" - latency: 1.083298ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:28:43Z" - latency: 1.79528ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:28:43Z" - latency: 887.258µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:27:43Z" - latency: 1.745938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:27:43Z" kind: List metadata: resourceVersion: ""