apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T19:33:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-228-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-228.ec2.internal uid: 031ba9bf-490c-4f4b-bf03-12c3ddd90e26 resourceVersion: "30999" uid: 07df19c7-7aa9-4725-882c-4bf4beacf787 spec: sourcePod: network-check-source-6947749cfc-ksr47 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T19:40:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.025722ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:47:01Z" - latency: 1.344622ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:46:01Z" - latency: 885.882µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:45:01Z" - latency: 1.042557ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:44:01Z" - latency: 1.099793ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:43:01Z" - latency: 1.363066ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:42:01Z" - latency: 1.268243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:41:01Z" - latency: 1.815105ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:40:01Z" - latency: 1.629572ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:39:01Z" - latency: 985.367µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:38:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T19:33:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-228-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-228.ec2.internal uid: 031ba9bf-490c-4f4b-bf03-12c3ddd90e26 resourceVersion: "29697" uid: 3ed77125-290d-4e48-a292-ed69f01a48d9 spec: sourcePod: network-check-source-6947749cfc-ksr47 targetEndpoint: a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T19:39:01Z" message: 'load-balancer-api-external: tcp connection to a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.578138ms message: 'load-balancer-api-external: tcp connection to a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:45:01Z" - latency: 8.938118ms message: 'load-balancer-api-external: resolved host name a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:45:01Z" - latency: 5.419322ms message: 'load-balancer-api-external: tcp connection to a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:44:01Z" - latency: 8.173267ms message: 'load-balancer-api-external: resolved host name a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:44:01Z" - latency: 5.495264ms message: 'load-balancer-api-external: tcp connection to a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:43:01Z" - latency: 11.698979ms message: 'load-balancer-api-external: resolved host name a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:43:01Z" - latency: 4.627158ms message: 'load-balancer-api-external: tcp connection to a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:42:01Z" - latency: 8.858712ms message: 'load-balancer-api-external: resolved host name a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:42:01Z" - latency: 4.705186ms message: 'load-balancer-api-external: tcp connection to a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:41:01Z" - latency: 8.763947ms message: 'load-balancer-api-external: resolved host name a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:41:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T19:33:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-228-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-228.ec2.internal uid: 031ba9bf-490c-4f4b-bf03-12c3ddd90e26 resourceVersion: "29698" uid: a519814e-efcf-40f7-8f7c-e8d842096bb8 spec: sourcePod: network-check-source-6947749cfc-ksr47 targetEndpoint: a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T19:39:01Z" message: 'load-balancer-api-internal: tcp connection to a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.544591ms message: 'load-balancer-api-internal: tcp connection to a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:45:01Z" - latency: 8.89972ms message: 'load-balancer-api-internal: resolved host name a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:45:01Z" - latency: 5.518687ms message: 'load-balancer-api-internal: tcp connection to a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:44:01Z" - latency: 8.218117ms message: 'load-balancer-api-internal: resolved host name a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:44:01Z" - latency: 5.11079ms message: 'load-balancer-api-internal: tcp connection to a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:43:01Z" - latency: 11.75888ms message: 'load-balancer-api-internal: resolved host name a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:43:01Z" - latency: 4.482064ms message: 'load-balancer-api-internal: tcp connection to a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:42:01Z" - latency: 9.040871ms message: 'load-balancer-api-internal: resolved host name a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:42:01Z" - latency: 4.393982ms message: 'load-balancer-api-internal: tcp connection to a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:41:01Z" - latency: 8.633649ms message: 'load-balancer-api-internal: resolved host name a32068cf5820444f0bbe6bbaf7f44907-86db000c9dc05bc2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:41:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T19:33:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-228-to-network-check-target-ip-10-0-130-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-228.ec2.internal uid: 031ba9bf-490c-4f4b-bf03-12c3ddd90e26 resourceVersion: "30996" uid: 8f07e59d-e9ab-47e9-b48a-47b661c398ac spec: sourcePod: network-check-source-6947749cfc-ksr47 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T19:40:01Z" message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 923.48µs message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:47:01Z" - latency: 1.019747ms message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:46:01Z" - latency: 907.968µs message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:45:01Z" - latency: 1.049973ms message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:44:01Z" - latency: 1.362407ms message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:43:01Z" - latency: 1.465384ms message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:42:01Z" - latency: 843.638µs message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:41:01Z" - latency: 856.589µs message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:40:01Z" - latency: 2.165823ms message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:39:01Z" - latency: 987.492µs message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:38:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T19:33:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-228-to-network-check-target-ip-10-0-140-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-228.ec2.internal uid: 031ba9bf-490c-4f4b-bf03-12c3ddd90e26 resourceVersion: "30997" uid: f8fdc044-19c3-4036-9c98-0567a88c7a3c spec: sourcePod: network-check-source-6947749cfc-ksr47 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T19:40:01Z" message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.132298ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:47:01Z" - latency: 2.389711ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:46:01Z" - latency: 2.202378ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:45:01Z" - latency: 2.138563ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:44:01Z" - latency: 2.435762ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:43:01Z" - latency: 2.482109ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:42:01Z" - latency: 2.481714ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:41:01Z" - latency: 2.196976ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:40:01Z" - latency: 1.961608ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:39:01Z" - latency: 2.230987ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:38:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T19:33:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-228-to-network-check-target-ip-10-0-140-61 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-228.ec2.internal uid: 031ba9bf-490c-4f4b-bf03-12c3ddd90e26 resourceVersion: "30998" uid: e2db1a24-d3a5-4d44-b1e2-58adf8b27aa8 spec: sourcePod: network-check-source-6947749cfc-ksr47 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T19:40:01Z" message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.909399ms message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:47:01Z" - latency: 1.685729ms message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:46:01Z" - latency: 1.992437ms message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:45:01Z" - latency: 1.675957ms message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:44:01Z" - latency: 1.803966ms message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:43:01Z" - latency: 1.784191ms message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:42:01Z" - latency: 2.029015ms message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:41:01Z" - latency: 2.092714ms message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:40:01Z" - latency: 5.027821ms message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:39:01Z" - latency: 2.003733ms message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:38:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T19:33:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-228-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-228.ec2.internal uid: 031ba9bf-490c-4f4b-bf03-12c3ddd90e26 resourceVersion: "29696" uid: a86ff9dd-9888-4a54-afc6-85721a370e9d spec: sourcePod: network-check-source-6947749cfc-ksr47 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T19:39:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.006558ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:45:01Z" - latency: 1.901278ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:45:01Z" - latency: 883.864µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:44:01Z" - latency: 1.873468ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:44:01Z" - latency: 986.019µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:43:01Z" - latency: 1.652646ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:43:01Z" - latency: 923.715µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:42:01Z" - latency: 1.955546ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:42:01Z" - latency: 927.589µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:41:01Z" - latency: 1.899366ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:41:01Z" kind: List metadata: resourceVersion: ""