apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T06:52:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-188-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-188.ec2.internal uid: 1ad5375c-3f35-46c7-b6a1-1517813dc842 resourceVersion: "20818" uid: e3217393-2ca1-4b64-b62e-fa1ac43524f9 spec: sourcePod: network-check-source-7d88cb55d8-kslnx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-30T06:59:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.09602ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:13:05Z" - latency: 870.963µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:12:05Z" - latency: 896.606µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:11:05Z" - latency: 1.090195ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:10:05Z" - latency: 1.587996ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:09:05Z" - latency: 1.143891ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:08:05Z" - latency: 955.924µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:07:05Z" - latency: 1.106119ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:06:05Z" - latency: 1.001358ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:05:05Z" - latency: 1.268597ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:04:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T06:52:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-188-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-188.ec2.internal uid: 1ad5375c-3f35-46c7-b6a1-1517813dc842 resourceVersion: "22286" uid: 22d55a8c-bc92-49f0-8977-9ba70f4ddc18 spec: sourcePod: network-check-source-7d88cb55d8-kslnx targetEndpoint: a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T06:58:05Z" message: 'load-balancer-api-external: tcp connection to a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.083637ms message: 'load-balancer-api-external: tcp connection to a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:16:05Z" - latency: 10.817671ms message: 'load-balancer-api-external: resolved host name a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T07:16:05Z" - latency: 5.109603ms message: 'load-balancer-api-external: tcp connection to a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:15:05Z" - latency: 8.251766ms message: 'load-balancer-api-external: resolved host name a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T07:15:05Z" - latency: 4.102531ms message: 'load-balancer-api-external: tcp connection to a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:14:05Z" - latency: 8.624902ms message: 'load-balancer-api-external: resolved host name a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T07:14:05Z" - latency: 4.147924ms message: 'load-balancer-api-external: tcp connection to a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:13:05Z" - latency: 8.212157ms message: 'load-balancer-api-external: resolved host name a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T07:13:05Z" - latency: 5.674962ms message: 'load-balancer-api-external: tcp connection to a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:12:05Z" - latency: 8.320425ms message: 'load-balancer-api-external: resolved host name a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T07:12:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T06:52:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-188-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-188.ec2.internal uid: 1ad5375c-3f35-46c7-b6a1-1517813dc842 resourceVersion: "22285" uid: ed815029-5f7d-4fc4-8049-10aabbcf0523 spec: sourcePod: network-check-source-7d88cb55d8-kslnx targetEndpoint: a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T06:58:05Z" message: 'load-balancer-api-internal: tcp connection to a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.75294ms message: 'load-balancer-api-internal: tcp connection to a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:16:05Z" - latency: 10.781971ms message: 'load-balancer-api-internal: resolved host name a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T07:16:05Z" - latency: 4.967921ms message: 'load-balancer-api-internal: tcp connection to a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:15:05Z" - latency: 8.217056ms message: 'load-balancer-api-internal: resolved host name a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T07:15:05Z" - latency: 4.409479ms message: 'load-balancer-api-internal: tcp connection to a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:14:05Z" - latency: 8.58625ms message: 'load-balancer-api-internal: resolved host name a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T07:14:05Z" - latency: 4.234082ms message: 'load-balancer-api-internal: tcp connection to a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:13:05Z" - latency: 8.195933ms message: 'load-balancer-api-internal: resolved host name a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T07:13:05Z" - latency: 4.764472ms message: 'load-balancer-api-internal: tcp connection to a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:12:05Z" - latency: 8.407535ms message: 'load-balancer-api-internal: resolved host name a1d939bac473b4708a529d4088f6ffa5-3e077247136404c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T07:12:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T06:52:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-188-to-network-check-target-ip-10-0-130-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-188.ec2.internal uid: 1ad5375c-3f35-46c7-b6a1-1517813dc842 resourceVersion: "20815" uid: 90aa697b-e165-45b4-8e35-afc5cb774717 spec: sourcePod: network-check-source-7d88cb55d8-kslnx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-30T06:59:05Z" message: 'network-check-target-ip-10-0-130-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 949.36µs message: 'network-check-target-ip-10-0-130-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:13:05Z" - latency: 817.267µs message: 'network-check-target-ip-10-0-130-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:12:05Z" - latency: 911.643µs message: 'network-check-target-ip-10-0-130-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:11:05Z" - latency: 886.56µs message: 'network-check-target-ip-10-0-130-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:10:05Z" - latency: 1.115092ms message: 'network-check-target-ip-10-0-130-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:09:05Z" - latency: 1.809744ms message: 'network-check-target-ip-10-0-130-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:08:05Z" - latency: 1.364682ms message: 'network-check-target-ip-10-0-130-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:07:05Z" - latency: 991.507µs message: 'network-check-target-ip-10-0-130-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:06:05Z" - latency: 1.302281ms message: 'network-check-target-ip-10-0-130-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:05:05Z" - latency: 922.751µs message: 'network-check-target-ip-10-0-130-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:04:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T06:52:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-188-to-network-check-target-ip-10-0-143-185 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-188.ec2.internal uid: 1ad5375c-3f35-46c7-b6a1-1517813dc842 resourceVersion: "20816" uid: 2a969c8c-f83a-4a3f-ac90-ff7e9c2496e3 spec: sourcePod: network-check-source-7d88cb55d8-kslnx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-30T06:59:05Z" message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.308216ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:13:05Z" - latency: 2.145047ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:12:05Z" - latency: 2.304968ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:11:05Z" - latency: 2.379835ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:10:05Z" - latency: 2.401546ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:09:05Z" - latency: 2.767982ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:08:05Z" - latency: 7.20051ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:07:05Z" - latency: 2.662656ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:06:05Z" - latency: 2.206288ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:05:05Z" - latency: 2.730298ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:04:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T06:52:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-188-to-network-check-target-ip-10-0-143-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-188.ec2.internal uid: 1ad5375c-3f35-46c7-b6a1-1517813dc842 resourceVersion: "20817" uid: 9459907f-356a-446a-8b52-3bc758923324 spec: sourcePod: network-check-source-7d88cb55d8-kslnx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-30T06:59:05Z" message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.199748ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:13:05Z" - latency: 2.272503ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:12:05Z" - latency: 2.418062ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:11:05Z" - latency: 2.461584ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:10:05Z" - latency: 2.194397ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:09:05Z" - latency: 2.253107ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:08:05Z" - latency: 2.588315ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:07:05Z" - latency: 2.091592ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:06:05Z" - latency: 2.286042ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:05:05Z" - latency: 2.172108ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:04:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T06:52:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-188-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-188.ec2.internal uid: 1ad5375c-3f35-46c7-b6a1-1517813dc842 resourceVersion: "22284" uid: 8b15d6de-b5a7-43d3-866f-c7daa9e61213 spec: sourcePod: network-check-source-7d88cb55d8-kslnx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-30T06:58:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 910.383µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:16:05Z" - latency: 1.754381ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T07:16:05Z" - latency: 907.237µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:15:05Z" - latency: 1.807487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T07:15:05Z" - latency: 755.096µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:14:05Z" - latency: 1.732803ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T07:14:05Z" - latency: 908.765µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:13:05Z" - latency: 1.724477ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T07:13:05Z" - latency: 966.654µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T07:12:05Z" - latency: 1.786915ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T07:12:05Z" kind: List metadata: resourceVersion: ""