apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T13:04:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-233-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-233.ec2.internal uid: 14f04be0-a711-4183-a618-d9bcc05e0117 resourceVersion: "30269" uid: d6cc39d2-d26c-4275-ba49-0b34baffc006 spec: sourcePod: network-check-source-dbd9cf844-c75mp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T13:11:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.887836ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:18:24Z" - latency: 1.032159ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:17:24Z" - latency: 1.077578ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:16:24Z" - latency: 1.07925ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:15:24Z" - latency: 1.45062ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:14:24Z" - latency: 1.04344ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:13:24Z" - latency: 716.722µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:12:24Z" - latency: 1.113453ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:11:24Z" - latency: 1.39549ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:10:24Z" - latency: 1.212012ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:09:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T13:04:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-233-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-233.ec2.internal uid: 14f04be0-a711-4183-a618-d9bcc05e0117 resourceVersion: "33933" uid: 5d9d0cca-7153-4d58-9dff-7929faa32b27 spec: sourcePod: network-check-source-dbd9cf844-c75mp targetEndpoint: a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T13:10:24Z" message: 'load-balancer-api-external: tcp connection to a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.802037ms message: 'load-balancer-api-external: tcp connection to a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:22:24Z" - latency: 8.846444ms message: 'load-balancer-api-external: resolved host name a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:22:24Z" - latency: 5.42674ms message: 'load-balancer-api-external: tcp connection to a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:21:24Z" - latency: 6.985321ms message: 'load-balancer-api-external: resolved host name a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:21:24Z" - latency: 6.510956ms message: 'load-balancer-api-external: tcp connection to a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:20:24Z" - latency: 6.862812ms message: 'load-balancer-api-external: resolved host name a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:20:24Z" - latency: 5.638953ms message: 'load-balancer-api-external: tcp connection to a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:19:24Z" - latency: 6.887131ms message: 'load-balancer-api-external: resolved host name a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:19:24Z" - latency: 3.789414ms message: 'load-balancer-api-external: tcp connection to a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:18:24Z" - latency: 12.812978ms message: 'load-balancer-api-external: resolved host name a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:18:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T13:04:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-233-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-233.ec2.internal uid: 14f04be0-a711-4183-a618-d9bcc05e0117 resourceVersion: "33932" uid: 2f67313b-4545-4bd8-ab4d-84eae2f31537 spec: sourcePod: network-check-source-dbd9cf844-c75mp targetEndpoint: a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T13:10:24Z" message: 'load-balancer-api-internal: tcp connection to a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.766376ms message: 'load-balancer-api-internal: tcp connection to a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:22:24Z" - latency: 8.775513ms message: 'load-balancer-api-internal: resolved host name a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:22:24Z" - latency: 5.414271ms message: 'load-balancer-api-internal: tcp connection to a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:21:24Z" - latency: 6.920138ms message: 'load-balancer-api-internal: resolved host name a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:21:24Z" - latency: 6.511047ms message: 'load-balancer-api-internal: tcp connection to a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:20:24Z" - latency: 6.746862ms message: 'load-balancer-api-internal: resolved host name a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:20:24Z" - latency: 3.650947ms message: 'load-balancer-api-internal: tcp connection to a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:19:24Z" - latency: 6.879333ms message: 'load-balancer-api-internal: resolved host name a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:19:24Z" - latency: 3.806658ms message: 'load-balancer-api-internal: tcp connection to a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:18:24Z" - latency: 12.625243ms message: 'load-balancer-api-internal: resolved host name a005a811a186b4724a3dc16b8f99699e-91fc455c26db9d0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:18:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T13:04:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-233-to-network-check-target-ip-10-0-128-233 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-233.ec2.internal uid: 14f04be0-a711-4183-a618-d9bcc05e0117 resourceVersion: "30266" uid: 3b646fab-d311-4f23-a689-05517c76492d spec: sourcePod: network-check-source-dbd9cf844-c75mp targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-10T13:11:24Z" message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 966.411µs message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:18:24Z" - latency: 864.555µs message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:17:24Z" - latency: 987.127µs message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:16:24Z" - latency: 958.159µs message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:15:24Z" - latency: 1.106917ms message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:14:24Z" - latency: 1.533603ms message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:13:24Z" - latency: 1.43657ms message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:12:24Z" - latency: 1.261355ms message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:11:24Z" - latency: 1.627871ms message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:10:24Z" - latency: 865.054µs message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:09:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T13:04:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-233-to-network-check-target-ip-10-0-128-45 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-233.ec2.internal uid: 14f04be0-a711-4183-a618-d9bcc05e0117 resourceVersion: "30267" uid: c5d6d65e-4940-4e6b-997e-24d4879e51b7 spec: sourcePod: network-check-source-dbd9cf844-c75mp targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T13:11:24Z" message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.209163ms message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:18:24Z" - latency: 2.01816ms message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:17:24Z" - latency: 1.944844ms message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:16:24Z" - latency: 1.828788ms message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:15:24Z" - latency: 1.844673ms message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:14:24Z" - latency: 2.425527ms message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:13:24Z" - latency: 2.033378ms message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:12:24Z" - latency: 1.792387ms message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:11:24Z" - latency: 2.557995ms message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:10:24Z" - latency: 1.707255ms message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:09:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T13:04:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-233-to-network-check-target-ip-10-0-143-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-233.ec2.internal uid: 14f04be0-a711-4183-a618-d9bcc05e0117 resourceVersion: "30268" uid: 4af56e3d-b4ab-4d55-8fe5-1a28310ce4f8 spec: sourcePod: network-check-source-dbd9cf844-c75mp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T13:11:24Z" message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.337913ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:18:24Z" - latency: 2.162845ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:17:24Z" - latency: 2.347547ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:16:24Z" - latency: 2.193036ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:15:24Z" - latency: 2.246712ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:14:24Z" - latency: 2.606631ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:13:24Z" - latency: 1.982246ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:12:24Z" - latency: 2.028403ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:11:24Z" - latency: 2.28373ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:10:24Z" - latency: 2.104271ms message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:09:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T13:04:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-233-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-233.ec2.internal uid: 14f04be0-a711-4183-a618-d9bcc05e0117 resourceVersion: "33931" uid: 255f24a4-49d7-4801-b59e-f23563c62364 spec: sourcePod: network-check-source-dbd9cf844-c75mp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T13:10:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 922.512µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:22:24Z" - latency: 2.394694ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:22:24Z" - latency: 924.557µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:21:24Z" - latency: 1.971471ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:21:24Z" - latency: 1.112497ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:20:24Z" - latency: 2.012174ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:20:24Z" - latency: 953.31µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:19:24Z" - latency: 1.710533ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:19:24Z" - latency: 996.589µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:18:24Z" - latency: 2.611374ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:18:24Z" kind: List metadata: resourceVersion: ""