apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T14:23:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-70-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-70.ec2.internal uid: d6e7772b-953b-4eac-b270-90e12ac29751 resourceVersion: "53451" uid: 02985a5f-9aa2-4667-87d6-f26bfa4d792a spec: sourcePod: network-check-source-6f8b768455-mgbbx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-11T14:30:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.019568ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:51:47Z" - latency: 1.015758ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:50:47Z" - latency: 1.013272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:49:47Z" - latency: 785.696µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:48:47Z" - latency: 1.032792ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:47:47Z" - latency: 1.042496ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:46:47Z" - latency: 862.185µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:45:47Z" - latency: 953.749µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:44:47Z" - latency: 938.444µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:43:47Z" - latency: 855.218µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:42:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T14:23:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-70-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-70.ec2.internal uid: d6e7772b-953b-4eac-b270-90e12ac29751 resourceVersion: "54753" uid: d857ba55-4956-4507-8b09-6e679b1aef4f spec: sourcePod: network-check-source-6f8b768455-mgbbx targetEndpoint: a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T14:29:47Z" message: 'load-balancer-api-external: tcp connection to a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.850359ms message: 'load-balancer-api-external: tcp connection to a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:53:47Z" - latency: 6.421177ms message: 'load-balancer-api-external: resolved host name a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:53:47Z" - latency: 6.452406ms message: 'load-balancer-api-external: tcp connection to a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:52:47Z" - latency: 8.579515ms message: 'load-balancer-api-external: resolved host name a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:52:47Z" - latency: 4.123529ms message: 'load-balancer-api-external: tcp connection to a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:51:47Z" - latency: 6.908743ms message: 'load-balancer-api-external: resolved host name a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:51:47Z" - latency: 4.843473ms message: 'load-balancer-api-external: tcp connection to a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:50:47Z" - latency: 8.621775ms message: 'load-balancer-api-external: resolved host name a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:50:47Z" - latency: 6.201624ms message: 'load-balancer-api-external: tcp connection to a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:49:47Z" - latency: 7.506958ms message: 'load-balancer-api-external: resolved host name a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:49:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T14:23:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-70-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-70.ec2.internal uid: d6e7772b-953b-4eac-b270-90e12ac29751 resourceVersion: "54754" uid: 30cfd99e-7bd8-4cef-9d99-21876971a4ab spec: sourcePod: network-check-source-6f8b768455-mgbbx targetEndpoint: a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T14:29:47Z" message: 'load-balancer-api-internal: tcp connection to a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.416176ms message: 'load-balancer-api-internal: tcp connection to a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:53:47Z" - latency: 2.588276ms message: 'load-balancer-api-internal: resolved host name a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:53:47Z" - latency: 2.712922ms message: 'load-balancer-api-internal: tcp connection to a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:52:47Z" - latency: 2.329834ms message: 'load-balancer-api-internal: resolved host name a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:52:47Z" - latency: 4.598021ms message: 'load-balancer-api-internal: tcp connection to a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:51:47Z" - latency: 3.187323ms message: 'load-balancer-api-internal: resolved host name a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:51:47Z" - latency: 3.985697ms message: 'load-balancer-api-internal: tcp connection to a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:50:47Z" - latency: 2.336872ms message: 'load-balancer-api-internal: resolved host name a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:50:47Z" - latency: 5.233871ms message: 'load-balancer-api-internal: tcp connection to a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:49:47Z" - latency: 2.036391ms message: 'load-balancer-api-internal: resolved host name a0af01956503e4cd69205ac2070be4bf-ca74b8b8485c5bf2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:49:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T14:23:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-70-to-network-check-target-ip-10-0-135-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-70.ec2.internal uid: d6e7772b-953b-4eac-b270-90e12ac29751 resourceVersion: "53455" uid: 43c49331-8859-4f4c-bfa0-a60c1c5f0be3 spec: sourcePod: network-check-source-6f8b768455-mgbbx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-11T14:30:48Z" message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.053707ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:51:48Z" - latency: 906.519µs message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:50:48Z" - latency: 838.794µs message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:49:48Z" - latency: 910.512µs message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:48:48Z" - latency: 2.072655ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:47:48Z" - latency: 2.105187ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:46:48Z" - latency: 1.838018ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:45:48Z" - latency: 2.215416ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:44:48Z" - latency: 867.195µs message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:43:48Z" - latency: 1.843028ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:42:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T14:23:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-70-to-network-check-target-ip-10-0-137-70 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-70.ec2.internal uid: d6e7772b-953b-4eac-b270-90e12ac29751 resourceVersion: "53458" uid: e04a0e43-a861-4c26-a146-cfd3da953df7 spec: sourcePod: network-check-source-6f8b768455-mgbbx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-11T14:30:48Z" message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 488.304µs message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:51:48Z" - latency: 655.901µs message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:50:48Z" - latency: 636.247µs message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:49:48Z" - latency: 842.563µs message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:48:48Z" - latency: 456.769µs message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:47:48Z" - latency: 478.576µs message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:46:48Z" - latency: 425.772µs message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:45:48Z" - latency: 879.56µs message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:44:48Z" - latency: 749.508µs message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:43:48Z" - latency: 481.237µs message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:42:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T14:23:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-70-to-network-check-target-ip-10-0-142-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-70.ec2.internal uid: d6e7772b-953b-4eac-b270-90e12ac29751 resourceVersion: "53457" uid: 0ebff7e2-ff97-4102-8fb0-dad8a68df5ce spec: sourcePod: network-check-source-6f8b768455-mgbbx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-11T14:30:48Z" message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.076405ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:51:48Z" - latency: 1.916459ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:50:48Z" - latency: 1.780329ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:49:48Z" - latency: 2.771564ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:48:48Z" - latency: 1.798062ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:47:48Z" - latency: 1.928472ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:46:48Z" - latency: 2.055201ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:45:48Z" - latency: 687.376µs message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:44:48Z" - latency: 2.140567ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:43:48Z" - latency: 2.031554ms message: 'network-check-target-ip-10-0-142-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:42:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T14:23:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-70-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-70.ec2.internal uid: d6e7772b-953b-4eac-b270-90e12ac29751 resourceVersion: "54755" uid: f04ebb79-f37d-43f4-9a7f-158809d0f626 spec: sourcePod: network-check-source-6f8b768455-mgbbx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-11T14:29:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.882016ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:53:47Z" - latency: 577.453µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T14:53:47Z" - latency: 2.234757ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:52:47Z" - latency: 545.859µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T14:52:47Z" - latency: 906.015µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:51:47Z" - latency: 575.057µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T14:51:47Z" - latency: 2.006683ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:50:47Z" - latency: 541.717µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T14:50:47Z" - latency: 1.808338ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:49:47Z" - latency: 516.478µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T14:49:47Z" kind: List metadata: resourceVersion: ""