apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:01:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-155-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-155.ec2.internal uid: dc16715f-2914-4940-8858-7b2560c7c356 resourceVersion: "31993" uid: 7a8ee355-1bbf-4e73-8fd0-08e56ba08146 spec: sourcePod: network-check-source-7bc5b6bf85-wkvxw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T10:08:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 979.511µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:43:01Z" - latency: 803.828µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:42:01Z" - latency: 1.072218ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:41:01Z" - latency: 1.406479ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:40:01Z" - latency: 1.180312ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:39:01Z" - latency: 1.32405ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:38:01Z" - latency: 980.602µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:37:01Z" - latency: 812.605µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:36:01Z" - latency: 866.683µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:35:01Z" - latency: 856.264µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:34:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:01:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-155-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-155.ec2.internal uid: dc16715f-2914-4940-8858-7b2560c7c356 resourceVersion: "34551" uid: b1057b53-dc31-4b79-aed5-f5f373e356a2 spec: sourcePod: network-check-source-7bc5b6bf85-wkvxw targetEndpoint: add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T10:07:01Z" message: 'load-balancer-api-external: tcp connection to add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.591465ms message: 'load-balancer-api-external: tcp connection to add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:49:01Z" - latency: 7.400116ms message: 'load-balancer-api-external: resolved host name add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:49:01Z" - latency: 3.111048ms message: 'load-balancer-api-external: tcp connection to add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:48:01Z" - latency: 8.341413ms message: 'load-balancer-api-external: resolved host name add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:48:01Z" - latency: 4.039029ms message: 'load-balancer-api-external: tcp connection to add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:47:01Z" - latency: 8.207402ms message: 'load-balancer-api-external: resolved host name add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:47:01Z" - latency: 3.948999ms message: 'load-balancer-api-external: tcp connection to add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:46:01Z" - latency: 6.469058ms message: 'load-balancer-api-external: resolved host name add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:46:01Z" - latency: 4.762876ms message: 'load-balancer-api-external: tcp connection to add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:45:01Z" - latency: 7.752291ms message: 'load-balancer-api-external: resolved host name add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:45:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:01:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-155-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-155.ec2.internal uid: dc16715f-2914-4940-8858-7b2560c7c356 resourceVersion: "34552" uid: 39f33dad-b8f8-4c18-8525-cc43f45d32a0 spec: sourcePod: network-check-source-7bc5b6bf85-wkvxw targetEndpoint: add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T10:07:01Z" message: 'load-balancer-api-internal: tcp connection to add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.611874ms message: 'load-balancer-api-internal: tcp connection to add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:49:01Z" - latency: 7.448764ms message: 'load-balancer-api-internal: resolved host name add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:49:01Z" - latency: 3.736867ms message: 'load-balancer-api-internal: tcp connection to add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:48:01Z" - latency: 8.322328ms message: 'load-balancer-api-internal: resolved host name add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:48:01Z" - latency: 4.003233ms message: 'load-balancer-api-internal: tcp connection to add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:47:01Z" - latency: 8.126976ms message: 'load-balancer-api-internal: resolved host name add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:47:01Z" - latency: 3.950215ms message: 'load-balancer-api-internal: tcp connection to add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:46:01Z" - latency: 6.5134ms message: 'load-balancer-api-internal: resolved host name add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:46:01Z" - latency: 4.777316ms message: 'load-balancer-api-internal: tcp connection to add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:45:01Z" - latency: 7.771656ms message: 'load-balancer-api-internal: resolved host name add686f0b5485403b8bac5c8808e6c4d-430cae64acc66b35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:45:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:01:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-155-to-network-check-target-ip-10-0-133-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-155.ec2.internal uid: dc16715f-2914-4940-8858-7b2560c7c356 resourceVersion: "31990" uid: 507a2e9c-9b9e-42fc-b806-f62bc1defcdd spec: sourcePod: network-check-source-7bc5b6bf85-wkvxw targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T10:08:01Z" message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.707328ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:43:01Z" - latency: 1.813516ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:42:01Z" - latency: 1.916492ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:41:01Z" - latency: 1.667899ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:40:01Z" - latency: 1.907079ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:39:01Z" - latency: 1.913083ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:38:01Z" - latency: 1.743027ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:37:01Z" - latency: 1.929346ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:36:01Z" - latency: 2.041027ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:35:01Z" - latency: 1.732922ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:34:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:01:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-155-to-network-check-target-ip-10-0-138-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-155.ec2.internal uid: dc16715f-2914-4940-8858-7b2560c7c356 resourceVersion: "31992" uid: 87b21c57-9564-4b8c-b92f-80c1e0b88103 spec: sourcePod: network-check-source-7bc5b6bf85-wkvxw targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-20T10:08:01Z" message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.240865ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:43:01Z" - latency: 2.14685ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:42:01Z" - latency: 2.204717ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:41:01Z" - latency: 2.049563ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:40:01Z" - latency: 2.244833ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:39:01Z" - latency: 2.280404ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:38:01Z" - latency: 2.12376ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:37:01Z" - latency: 2.287898ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:36:01Z" - latency: 2.037503ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:35:01Z" - latency: 1.625203ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:34:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:01:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-155-to-network-check-target-ip-10-0-143-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-155.ec2.internal uid: dc16715f-2914-4940-8858-7b2560c7c356 resourceVersion: "31989" uid: a68ec3e5-3d83-4538-8b5d-69f2ec4b6f21 spec: sourcePod: network-check-source-7bc5b6bf85-wkvxw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T10:08:01Z" message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 749.863µs message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:43:01Z" - latency: 1.423899ms message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:42:01Z" - latency: 1.138255ms message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:41:01Z" - latency: 718.364µs message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:40:01Z" - latency: 823.92µs message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:39:01Z" - latency: 906.625µs message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:38:01Z" - latency: 1.470401ms message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:37:01Z" - latency: 829.98µs message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:36:01Z" - latency: 1.306494ms message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:35:01Z" - latency: 707.145µs message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:34:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:01:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-155-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-155.ec2.internal uid: dc16715f-2914-4940-8858-7b2560c7c356 resourceVersion: "34548" uid: 1af05379-5175-42ea-9fe2-62bbab487964 spec: sourcePod: network-check-source-7bc5b6bf85-wkvxw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T10:07:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 779.792µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:49:01Z" - latency: 1.905105ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T10:49:01Z" - latency: 766.306µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:48:01Z" - latency: 2.231941ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T10:48:01Z" - latency: 953.985µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:47:01Z" - latency: 2.0789ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T10:47:01Z" - latency: 880.053µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:46:01Z" - latency: 1.729932ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T10:46:01Z" - latency: 1.13808ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:45:01Z" - latency: 1.610291ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T10:45:01Z" kind: List metadata: resourceVersion: ""