apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T14:54:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-202-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-202.ec2.internal uid: 7243cd3d-23e0-4046-b28e-6adca722bd4c resourceVersion: "64523" uid: 956d033c-3239-400d-b165-c325f5f3913e spec: sourcePod: network-check-source-7bc5b6bf85-gzgw4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-19T15:01:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 861.134µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:36:45Z" - latency: 831.452µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:35:45Z" - latency: 847.469µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:34:45Z" - latency: 1.025764ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:33:45Z" - latency: 824.417µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:32:45Z" - latency: 928.409µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:31:45Z" - latency: 1.006271ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:30:45Z" - latency: 760.691µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:29:45Z" - latency: 1.164397ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:28:45Z" - latency: 873.672µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:27:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T14:54:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-202-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-202.ec2.internal uid: 7243cd3d-23e0-4046-b28e-6adca722bd4c resourceVersion: "64526" uid: c2c359ef-eb7f-4406-9626-bc94131b4a6c spec: sourcePod: network-check-source-7bc5b6bf85-gzgw4 targetEndpoint: a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-19T15:00:45Z" message: 'load-balancer-api-external: tcp connection to a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.425295ms message: 'load-balancer-api-external: tcp connection to a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:36:45Z" - latency: 8.662557ms message: 'load-balancer-api-external: resolved host name a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:36:45Z" - latency: 5.072475ms message: 'load-balancer-api-external: tcp connection to a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:35:45Z" - latency: 8.14222ms message: 'load-balancer-api-external: resolved host name a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:35:45Z" - latency: 4.818732ms message: 'load-balancer-api-external: tcp connection to a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:34:45Z" - latency: 13.635089ms message: 'load-balancer-api-external: resolved host name a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:34:45Z" - latency: 3.495306ms message: 'load-balancer-api-external: tcp connection to a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:33:45Z" - latency: 9.362015ms message: 'load-balancer-api-external: resolved host name a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:33:45Z" - latency: 5.032967ms message: 'load-balancer-api-external: tcp connection to a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:32:45Z" - latency: 8.399289ms message: 'load-balancer-api-external: resolved host name a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:32:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T14:54:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-202-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-202.ec2.internal uid: 7243cd3d-23e0-4046-b28e-6adca722bd4c resourceVersion: "64525" uid: c74e2ad3-181b-4dd1-84c7-9b73bef48f22 spec: sourcePod: network-check-source-7bc5b6bf85-gzgw4 targetEndpoint: a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-19T15:00:45Z" message: 'load-balancer-api-internal: tcp connection to a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.153272ms message: 'load-balancer-api-internal: tcp connection to a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:36:45Z" - latency: 8.715514ms message: 'load-balancer-api-internal: resolved host name a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:36:45Z" - latency: 5.53064ms message: 'load-balancer-api-internal: tcp connection to a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:35:45Z" - latency: 8.110593ms message: 'load-balancer-api-internal: resolved host name a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:35:45Z" - latency: 4.844807ms message: 'load-balancer-api-internal: tcp connection to a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:34:45Z" - latency: 13.686007ms message: 'load-balancer-api-internal: resolved host name a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:34:45Z" - latency: 3.483633ms message: 'load-balancer-api-internal: tcp connection to a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:33:45Z" - latency: 9.297731ms message: 'load-balancer-api-internal: resolved host name a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:33:45Z" - latency: 5.057035ms message: 'load-balancer-api-internal: tcp connection to a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:32:45Z" - latency: 8.469308ms message: 'load-balancer-api-internal: resolved host name a9bd89babad734f278de69cae1e74603-34fa0d3e704011f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T15:32:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T14:54:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-202-to-network-check-target-ip-10-0-135-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-202.ec2.internal uid: 7243cd3d-23e0-4046-b28e-6adca722bd4c resourceVersion: "64521" uid: fa3b5c5a-ab02-4e29-8f08-de0861456c88 spec: sourcePod: network-check-source-7bc5b6bf85-gzgw4 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-19T15:01:45Z" message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.124072ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:36:45Z" - latency: 2.300948ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:35:45Z" - latency: 2.280068ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:34:45Z" - latency: 2.547655ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:33:45Z" - latency: 2.286335ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:32:45Z" - latency: 2.386999ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:31:45Z" - latency: 2.556923ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:30:45Z" - latency: 2.147367ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:29:45Z" - latency: 2.50618ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:28:45Z" - latency: 2.443612ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:27:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T14:54:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-202-to-network-check-target-ip-10-0-139-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-202.ec2.internal uid: 7243cd3d-23e0-4046-b28e-6adca722bd4c resourceVersion: "64519" uid: 6f222814-d2ec-4e1c-8553-339a27427b76 spec: sourcePod: network-check-source-7bc5b6bf85-gzgw4 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-19T15:01:45Z" message: 'network-check-target-ip-10-0-139-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.229658ms message: 'network-check-target-ip-10-0-139-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:36:45Z" - latency: 765.254µs message: 'network-check-target-ip-10-0-139-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:35:45Z" - latency: 922.385µs message: 'network-check-target-ip-10-0-139-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:34:45Z" - latency: 702.175µs message: 'network-check-target-ip-10-0-139-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:33:45Z" - latency: 676.797µs message: 'network-check-target-ip-10-0-139-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:32:45Z" - latency: 859.634µs message: 'network-check-target-ip-10-0-139-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:31:45Z" - latency: 790.666µs message: 'network-check-target-ip-10-0-139-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:30:45Z" - latency: 795.566µs message: 'network-check-target-ip-10-0-139-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:29:45Z" - latency: 1.013034ms message: 'network-check-target-ip-10-0-139-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:28:45Z" - latency: 678.043µs message: 'network-check-target-ip-10-0-139-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:27:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T14:54:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-202-to-network-check-target-ip-10-0-142-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-202.ec2.internal uid: 7243cd3d-23e0-4046-b28e-6adca722bd4c resourceVersion: "64520" uid: 9145d46c-11f3-438a-bfcd-55fc1ca06ee4 spec: sourcePod: network-check-source-7bc5b6bf85-gzgw4 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-19T15:01:45Z" message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.977891ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:36:45Z" - latency: 2.001305ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:35:45Z" - latency: 2.194026ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:34:45Z" - latency: 2.363246ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:33:45Z" - latency: 2.235379ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:32:45Z" - latency: 2.477ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:31:45Z" - latency: 1.972831ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:30:45Z" - latency: 15.055043ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:29:45Z" - latency: 2.428678ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:28:45Z" - latency: 2.121056ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:27:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T14:54:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-202-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-202.ec2.internal uid: 7243cd3d-23e0-4046-b28e-6adca722bd4c resourceVersion: "64522" uid: 04ba086c-9f58-4538-a6b6-adabb8c32c0c spec: sourcePod: network-check-source-7bc5b6bf85-gzgw4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-19T15:00:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.405684ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:36:45Z" - latency: 1.63515ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T15:36:45Z" - latency: 845.042µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:35:45Z" - latency: 1.616471ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T15:35:45Z" - latency: 1.115565ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:34:45Z" - latency: 1.669481ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T15:34:45Z" - latency: 854.252µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:33:45Z" - latency: 1.64271ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T15:33:45Z" - latency: 880.062µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T15:32:45Z" - latency: 1.766871ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T15:32:45Z" kind: List metadata: resourceVersion: ""