apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 0db829c3-42f0-4002-b76d-4f29b0168e23 resourceVersion: "31853" uid: 4c4cf9f3-a834-4e5f-bd56-59611b69a257 spec: sourcePod: network-check-source-56d84b9f44-98rxb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T15:57:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 765.975µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:32:40Z" - latency: 905.44µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:31:40Z" - latency: 818.645µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:30:40Z" - latency: 895.316µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:29:40Z" - latency: 987.663µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:28:40Z" - latency: 1.192183ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:27:40Z" - latency: 866.672µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:26:40Z" - latency: 1.071955ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:25:40Z" - latency: 985.824µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:24:40Z" - latency: 1.569845ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:23:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 0db829c3-42f0-4002-b76d-4f29b0168e23 resourceVersion: "31854" uid: f3ebbbea-e6cc-4acf-bcd7-c170d757f394 spec: sourcePod: network-check-source-56d84b9f44-98rxb targetEndpoint: a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T15:56:40Z" message: 'load-balancer-api-external: tcp connection to a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.906229ms message: 'load-balancer-api-external: tcp connection to a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:32:40Z" - latency: 10.447219ms message: 'load-balancer-api-external: resolved host name a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:32:40Z" - latency: 5.532227ms message: 'load-balancer-api-external: tcp connection to a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:31:40Z" - latency: 6.829101ms message: 'load-balancer-api-external: resolved host name a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:31:40Z" - latency: 4.380402ms message: 'load-balancer-api-external: tcp connection to a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:30:40Z" - latency: 8.781751ms message: 'load-balancer-api-external: resolved host name a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:30:40Z" - latency: 5.361483ms message: 'load-balancer-api-external: tcp connection to a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:29:40Z" - latency: 8.542149ms message: 'load-balancer-api-external: resolved host name a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:29:40Z" - latency: 5.672809ms message: 'load-balancer-api-external: tcp connection to a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:28:40Z" - latency: 7.500739ms message: 'load-balancer-api-external: resolved host name a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:28:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 0db829c3-42f0-4002-b76d-4f29b0168e23 resourceVersion: "31855" uid: f94a3abc-773a-4fa1-8d73-3619feca4998 spec: sourcePod: network-check-source-56d84b9f44-98rxb targetEndpoint: a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T15:56:40Z" message: 'load-balancer-api-internal: tcp connection to a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.612931ms message: 'load-balancer-api-internal: tcp connection to a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:32:40Z" - latency: 10.477208ms message: 'load-balancer-api-internal: resolved host name a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:32:40Z" - latency: 6.102665ms message: 'load-balancer-api-internal: tcp connection to a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:31:40Z" - latency: 6.790683ms message: 'load-balancer-api-internal: resolved host name a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:31:40Z" - latency: 4.753165ms message: 'load-balancer-api-internal: tcp connection to a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:30:40Z" - latency: 8.867448ms message: 'load-balancer-api-internal: resolved host name a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:30:40Z" - latency: 5.343664ms message: 'load-balancer-api-internal: tcp connection to a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:29:40Z" - latency: 8.504046ms message: 'load-balancer-api-internal: resolved host name a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:29:40Z" - latency: 5.681083ms message: 'load-balancer-api-internal: tcp connection to a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:28:40Z" - latency: 7.434701ms message: 'load-balancer-api-internal: resolved host name a1e0fc198eecb44fca1a4c5ee615912b-6e9b1f0f78428d4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:28:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-network-check-target-ip-10-0-128-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 0db829c3-42f0-4002-b76d-4f29b0168e23 resourceVersion: "31851" uid: 490f602b-fd7e-4f0f-a973-9bccfcd57386 spec: sourcePod: network-check-source-56d84b9f44-98rxb targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-02T15:57:40Z" message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 854.256µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:32:40Z" - latency: 856.801µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:31:40Z" - latency: 831.304µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:30:40Z" - latency: 944.924µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:29:40Z" - latency: 918.236µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:28:40Z" - latency: 883.132µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:27:40Z" - latency: 875.771µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:26:40Z" - latency: 888.365µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:25:40Z" - latency: 1.013099ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:24:40Z" - latency: 727.417µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:23:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-network-check-target-ip-10-0-133-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 0db829c3-42f0-4002-b76d-4f29b0168e23 resourceVersion: "31850" uid: dcdd34de-1f34-4ccd-8ee4-10f2e8893ea5 spec: sourcePod: network-check-source-56d84b9f44-98rxb targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T15:57:40Z" message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.09039ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:32:40Z" - latency: 1.907967ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:31:40Z" - latency: 1.744561ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:30:40Z" - latency: 2.000186ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:29:40Z" - latency: 1.95206ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:28:40Z" - latency: 1.771271ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:27:40Z" - latency: 1.758746ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:26:40Z" - latency: 1.875114ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:25:40Z" - latency: 1.781867ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:24:40Z" - latency: 1.815497ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:23:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-network-check-target-ip-10-0-142-13 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 0db829c3-42f0-4002-b76d-4f29b0168e23 resourceVersion: "31849" uid: 336ac54b-a6a3-4b02-b0e4-866483ae3c54 spec: sourcePod: network-check-source-56d84b9f44-98rxb targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-02T15:57:40Z" message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.050779ms message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:32:40Z" - latency: 2.141775ms message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:31:40Z" - latency: 2.110372ms message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:30:40Z" - latency: 2.107258ms message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:29:40Z" - latency: 2.280348ms message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:28:40Z" - latency: 2.169603ms message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:27:40Z" - latency: 2.253064ms message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:26:40Z" - latency: 2.125056ms message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:25:40Z" - latency: 2.094073ms message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:24:40Z" - latency: 2.890724ms message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:23:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 0db829c3-42f0-4002-b76d-4f29b0168e23 resourceVersion: "31852" uid: eeb617f9-f99f-4f65-88b9-7b25a3b8e5f5 spec: sourcePod: network-check-source-56d84b9f44-98rxb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T15:56:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 860.148µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:32:40Z" - latency: 2.140772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:32:40Z" - latency: 798.851µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:31:40Z" - latency: 2.18794ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:31:40Z" - latency: 794.899µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:30:40Z" - latency: 2.09425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:30:40Z" - latency: 783.635µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:29:40Z" - latency: 2.523974ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:29:40Z" - latency: 1.104615ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:28:40Z" - latency: 1.71276ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:28:40Z" kind: List metadata: resourceVersion: ""