apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T00:37:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-51-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-51.ec2.internal uid: 847a1ae7-ba48-4475-ba1f-d4fa180c6d85 resourceVersion: "68576" uid: 3a1fcda4-8ae3-4f73-96ea-5357755753e5 spec: sourcePod: network-check-source-6f8b768455-59g6x targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T00:44:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 837.22µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:12:35Z" - latency: 1.205895ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:11:35Z" - latency: 1.264755ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:10:35Z" - latency: 973.338µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:09:35Z" - latency: 1.164211ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:08:35Z" - latency: 917.301µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:07:35Z" - latency: 952.573µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:06:35Z" - latency: 991.922µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:05:35Z" - latency: 1.046784ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:04:35Z" - latency: 978.141µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:03:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T00:37:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-51-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-51.ec2.internal uid: 847a1ae7-ba48-4475-ba1f-d4fa180c6d85 resourceVersion: "64364" uid: a644b909-8f8d-41a3-b50d-85741a51a004 spec: sourcePod: network-check-source-6f8b768455-59g6x targetEndpoint: a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T00:43:35Z" message: 'load-balancer-api-external: tcp connection to a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.042199ms message: 'load-balancer-api-external: tcp connection to a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:07:35Z" - latency: 9.526457ms message: 'load-balancer-api-external: resolved host name a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T01:07:35Z" - latency: 4.247427ms message: 'load-balancer-api-external: tcp connection to a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:06:35Z" - latency: 11.41241ms message: 'load-balancer-api-external: resolved host name a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T01:06:35Z" - latency: 4.98473ms message: 'load-balancer-api-external: tcp connection to a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:05:35Z" - latency: 9.149995ms message: 'load-balancer-api-external: resolved host name a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T01:05:35Z" - latency: 5.127267ms message: 'load-balancer-api-external: tcp connection to a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:04:35Z" - latency: 9.286194ms message: 'load-balancer-api-external: resolved host name a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T01:04:35Z" - latency: 5.598836ms message: 'load-balancer-api-external: tcp connection to a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:03:35Z" - latency: 9.076518ms message: 'load-balancer-api-external: resolved host name a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T01:03:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T00:37:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-51-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-51.ec2.internal uid: 847a1ae7-ba48-4475-ba1f-d4fa180c6d85 resourceVersion: "64365" uid: b7035cab-d2fc-4aff-b00b-8288de0dddc0 spec: sourcePod: network-check-source-6f8b768455-59g6x targetEndpoint: a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T00:43:35Z" message: 'load-balancer-api-internal: tcp connection to a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.039578ms message: 'load-balancer-api-internal: tcp connection to a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:07:35Z" - latency: 9.465898ms message: 'load-balancer-api-internal: resolved host name a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T01:07:35Z" - latency: 4.229851ms message: 'load-balancer-api-internal: tcp connection to a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:06:35Z" - latency: 11.469781ms message: 'load-balancer-api-internal: resolved host name a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T01:06:35Z" - latency: 5.003134ms message: 'load-balancer-api-internal: tcp connection to a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:05:35Z" - latency: 9.019617ms message: 'load-balancer-api-internal: resolved host name a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T01:05:35Z" - latency: 5.132955ms message: 'load-balancer-api-internal: tcp connection to a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:04:35Z" - latency: 9.372442ms message: 'load-balancer-api-internal: resolved host name a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T01:04:35Z" - latency: 5.231659ms message: 'load-balancer-api-internal: tcp connection to a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:03:35Z" - latency: 8.990467ms message: 'load-balancer-api-internal: resolved host name a1788fd3a612f4b6f92ebf91d99b89b5-99b35303a09c6053.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T01:03:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T00:37:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-51-to-network-check-target-ip-10-0-128-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-51.ec2.internal uid: 847a1ae7-ba48-4475-ba1f-d4fa180c6d85 resourceVersion: "68575" uid: 44734f65-2a26-4238-907a-d98f4e778615 spec: sourcePod: network-check-source-6f8b768455-59g6x targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T00:44:35Z" message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.156967ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:12:35Z" - latency: 2.410492ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:11:35Z" - latency: 2.37978ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:10:35Z" - latency: 2.527868ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:09:35Z" - latency: 2.906616ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:08:35Z" - latency: 2.323174ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:07:35Z" - latency: 2.132995ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:06:35Z" - latency: 2.411067ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:05:35Z" - latency: 2.627177ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:04:35Z" - latency: 2.408733ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:03:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T00:37:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-51-to-network-check-target-ip-10-0-134-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-51.ec2.internal uid: 847a1ae7-ba48-4475-ba1f-d4fa180c6d85 resourceVersion: "68573" uid: f2170fee-b53f-4d4f-88da-48309c660581 spec: sourcePod: network-check-source-6f8b768455-59g6x targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T00:44:35Z" message: 'network-check-target-ip-10-0-134-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.099641ms message: 'network-check-target-ip-10-0-134-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:12:35Z" - latency: 2.279483ms message: 'network-check-target-ip-10-0-134-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:11:35Z" - latency: 2.049311ms message: 'network-check-target-ip-10-0-134-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:10:35Z" - latency: 2.59082ms message: 'network-check-target-ip-10-0-134-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:09:35Z" - latency: 2.310386ms message: 'network-check-target-ip-10-0-134-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:08:35Z" - latency: 2.218622ms message: 'network-check-target-ip-10-0-134-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:07:35Z" - latency: 2.371928ms message: 'network-check-target-ip-10-0-134-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:06:35Z" - latency: 1.800552ms message: 'network-check-target-ip-10-0-134-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:05:35Z" - latency: 2.14933ms message: 'network-check-target-ip-10-0-134-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:04:35Z" - latency: 2.387282ms message: 'network-check-target-ip-10-0-134-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:03:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T00:37:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-51-to-network-check-target-ip-10-0-143-51 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-51.ec2.internal uid: 847a1ae7-ba48-4475-ba1f-d4fa180c6d85 resourceVersion: "68574" uid: 31107364-4abc-4572-be14-48a849011078 spec: sourcePod: network-check-source-6f8b768455-59g6x targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T00:44:35Z" message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 885.34µs message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:12:35Z" - latency: 1.529036ms message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:11:35Z" - latency: 854.661µs message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:10:35Z" - latency: 949.343µs message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:09:35Z" - latency: 1.041314ms message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:08:35Z" - latency: 915.174µs message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:07:35Z" - latency: 796.008µs message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:06:35Z" - latency: 968.309µs message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:05:35Z" - latency: 999.776µs message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:04:35Z" - latency: 1.414462ms message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:03:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T00:37:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-51-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-51.ec2.internal uid: 847a1ae7-ba48-4475-ba1f-d4fa180c6d85 resourceVersion: "64363" uid: d00ee0e1-6856-4be7-a17e-3ad346bc9a3d spec: sourcePod: network-check-source-6f8b768455-59g6x targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T00:43:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.977µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:07:35Z" - latency: 2.132954ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T01:07:35Z" - latency: 881.053µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:06:35Z" - latency: 2.045233ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T01:06:35Z" - latency: 1.05657ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:05:35Z" - latency: 2.31224ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T01:05:35Z" - latency: 981.311µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:04:35Z" - latency: 2.099274ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T01:04:35Z" - latency: 1.125646ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T01:03:35Z" - latency: 1.901137ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T01:03:35Z" kind: List metadata: resourceVersion: ""