apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T13:17:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-243-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-243.ec2.internal uid: 3cbbaeac-4a17-4b7d-974c-8f0b3662d3d4 resourceVersion: "79204" uid: ab59ea32-9d06-473d-bf8d-8eea860fe144 spec: sourcePod: network-check-source-56499946bc-s59jf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T13:24:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.182163ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:23Z" - latency: 931.403µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:23Z" - latency: 911.628µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:23Z" - latency: 960.767µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:23Z" - latency: 914.402µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:30:23Z" - latency: 827.91µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:29:23Z" - latency: 907.687µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:28:23Z" - latency: 1.305709ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:27:23Z" - latency: 836.389µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:26:23Z" - latency: 941.108µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:25:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T13:17:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-243-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-243.ec2.internal uid: 3cbbaeac-4a17-4b7d-974c-8f0b3662d3d4 resourceVersion: "79885" uid: 7c2ed65a-e995-4f02-8373-0831965bcf6f spec: sourcePod: network-check-source-56499946bc-s59jf targetEndpoint: a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T13:23:23Z" message: 'load-balancer-api-external: tcp connection to a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.097907ms message: 'load-balancer-api-external: tcp connection to a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:23Z" - latency: 7.455972ms message: 'load-balancer-api-external: resolved host name a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:35:23Z" - latency: 6.21001ms message: 'load-balancer-api-external: tcp connection to a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:23Z" - latency: 6.092691ms message: 'load-balancer-api-external: resolved host name a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:34:23Z" - latency: 4.275648ms message: 'load-balancer-api-external: tcp connection to a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:23Z" - latency: 6.62241ms message: 'load-balancer-api-external: resolved host name a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:33:23Z" - latency: 4.74391ms message: 'load-balancer-api-external: tcp connection to a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:23Z" - latency: 6.565042ms message: 'load-balancer-api-external: resolved host name a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:32:23Z" - latency: 3.50725ms message: 'load-balancer-api-external: tcp connection to a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:23Z" - latency: 7.249522ms message: 'load-balancer-api-external: resolved host name a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:31:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T13:17:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-243-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-243.ec2.internal uid: 3cbbaeac-4a17-4b7d-974c-8f0b3662d3d4 resourceVersion: "79886" uid: 9c72dbdf-1538-4029-a09e-8dc52589f47a spec: sourcePod: network-check-source-56499946bc-s59jf targetEndpoint: a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T13:23:23Z" message: 'load-balancer-api-internal: tcp connection to a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.108814ms message: 'load-balancer-api-internal: tcp connection to a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:23Z" - latency: 7.548571ms message: 'load-balancer-api-internal: resolved host name a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:35:23Z" - latency: 6.199681ms message: 'load-balancer-api-internal: tcp connection to a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:23Z" - latency: 6.143403ms message: 'load-balancer-api-internal: resolved host name a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:34:23Z" - latency: 4.845349ms message: 'load-balancer-api-internal: tcp connection to a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:23Z" - latency: 6.612659ms message: 'load-balancer-api-internal: resolved host name a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:33:23Z" - latency: 4.735333ms message: 'load-balancer-api-internal: tcp connection to a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:23Z" - latency: 6.576161ms message: 'load-balancer-api-internal: resolved host name a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:32:23Z" - latency: 5.786953ms message: 'load-balancer-api-internal: tcp connection to a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:23Z" - latency: 7.369729ms message: 'load-balancer-api-internal: resolved host name a757e4d2fdcfa44088eac934bada7ff4-8b372f7c9f23306f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:31:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T13:17:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-243-to-network-check-target-ip-10-0-131-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-243.ec2.internal uid: 3cbbaeac-4a17-4b7d-974c-8f0b3662d3d4 resourceVersion: "79201" uid: d7703ede-1e80-451f-82b8-8d9d4528000e spec: sourcePod: network-check-source-56499946bc-s59jf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T13:24:23Z" message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.407055ms message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:23Z" - latency: 990.393µs message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:23Z" - latency: 791.565µs message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:23Z" - latency: 858.414µs message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:23Z" - latency: 1.000927ms message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:30:23Z" - latency: 1.372377ms message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:29:23Z" - latency: 1.582638ms message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:28:23Z" - latency: 1.870997ms message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:27:23Z" - latency: 780.624µs message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:26:23Z" - latency: 1.399413ms message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:25:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T13:17:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-243-to-network-check-target-ip-10-0-135-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-243.ec2.internal uid: 3cbbaeac-4a17-4b7d-974c-8f0b3662d3d4 resourceVersion: "79202" uid: 50306cef-15ec-4920-bca7-3732c4e32cb6 spec: sourcePod: network-check-source-56499946bc-s59jf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T13:24:23Z" message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.050153ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:23Z" - latency: 2.136132ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:23Z" - latency: 1.754604ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:23Z" - latency: 1.860068ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:23Z" - latency: 2.101042ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:30:23Z" - latency: 2.148338ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:29:23Z" - latency: 1.977712ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:28:23Z" - latency: 2.364996ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:27:23Z" - latency: 1.794894ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:26:23Z" - latency: 2.062939ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:25:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T13:17:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-243-to-network-check-target-ip-10-0-138-135 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-243.ec2.internal uid: 3cbbaeac-4a17-4b7d-974c-8f0b3662d3d4 resourceVersion: "79203" uid: 802ab096-7f89-4d2e-8bef-b889e2a28575 spec: sourcePod: network-check-source-56499946bc-s59jf targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T13:24:23Z" message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.473561ms message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:23Z" - latency: 2.055526ms message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:23Z" - latency: 1.854221ms message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:23Z" - latency: 1.788561ms message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:23Z" - latency: 1.944452ms message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:30:23Z" - latency: 2.011749ms message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:29:23Z" - latency: 2.196145ms message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:28:23Z" - latency: 2.638711ms message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:27:23Z" - latency: 1.695557ms message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:26:23Z" - latency: 2.289365ms message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:25:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T13:17:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-243-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-243.ec2.internal uid: 3cbbaeac-4a17-4b7d-974c-8f0b3662d3d4 resourceVersion: "79883" uid: 75198e36-b2e5-44a8-906d-d80881fa41d2 spec: sourcePod: network-check-source-56499946bc-s59jf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T13:23:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 849.893µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:23Z" - latency: 1.852698ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:35:23Z" - latency: 986.498µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:23Z" - latency: 1.658587ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:34:23Z" - latency: 1.064165ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:23Z" - latency: 1.748068ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:33:23Z" - latency: 956.935µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:23Z" - latency: 1.811266ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:32:23Z" - latency: 853.75µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:23Z" - latency: 1.7278ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:31:23Z" kind: List metadata: resourceVersion: ""