apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:17:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-173-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-173.ec2.internal uid: 5bb6f6b1-012b-49f4-9d56-2a3a4ff58a90 resourceVersion: "51403" uid: 2ee5bd1e-5f88-49d2-b475-85e43a39ea98 spec: sourcePod: network-check-source-6947749cfc-jtzhp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T19:24:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.048074ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:52:18Z" - latency: 1.12141ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:51:18Z" - latency: 1.093768ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:50:18Z" - latency: 815.439µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:49:18Z" - latency: 826.425µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:48:18Z" - latency: 1.348496ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:47:18Z" - latency: 1.023968ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:18Z" - latency: 1.34147ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:18Z" - latency: 862.806µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:44:18Z" - latency: 1.119213ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:43:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:17:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-173-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-173.ec2.internal uid: 5bb6f6b1-012b-49f4-9d56-2a3a4ff58a90 resourceVersion: "45920" uid: 6fa1887a-837a-4bbf-8bda-7af6d0895985 spec: sourcePod: network-check-source-6947749cfc-jtzhp targetEndpoint: a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T19:23:18Z" message: 'load-balancer-api-external: tcp connection to a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.020795ms message: 'load-balancer-api-external: tcp connection to a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:47:18Z" - latency: 6.793395ms message: 'load-balancer-api-external: resolved host name a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:47:18Z" - latency: 5.328529ms message: 'load-balancer-api-external: tcp connection to a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:18Z" - latency: 6.574163ms message: 'load-balancer-api-external: resolved host name a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:46:18Z" - latency: 3.74397ms message: 'load-balancer-api-external: tcp connection to a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:18Z" - latency: 12.850724ms message: 'load-balancer-api-external: resolved host name a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:45:18Z" - latency: 3.306245ms message: 'load-balancer-api-external: tcp connection to a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:44:18Z" - latency: 6.187158ms message: 'load-balancer-api-external: resolved host name a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:44:18Z" - latency: 5.896863ms message: 'load-balancer-api-external: tcp connection to a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:43:18Z" - latency: 6.6582ms message: 'load-balancer-api-external: resolved host name a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:43:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:17:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-173-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-173.ec2.internal uid: 5bb6f6b1-012b-49f4-9d56-2a3a4ff58a90 resourceVersion: "45921" uid: e64d7156-6447-4513-b3ef-71910dd238cf spec: sourcePod: network-check-source-6947749cfc-jtzhp targetEndpoint: a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T19:23:18Z" message: 'load-balancer-api-internal: tcp connection to a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.147187ms message: 'load-balancer-api-internal: tcp connection to a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:47:18Z" - latency: 6.839492ms message: 'load-balancer-api-internal: resolved host name a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:47:18Z" - latency: 5.394675ms message: 'load-balancer-api-internal: tcp connection to a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:18Z" - latency: 6.543939ms message: 'load-balancer-api-internal: resolved host name a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:46:18Z" - latency: 5.200612ms message: 'load-balancer-api-internal: tcp connection to a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:18Z" - latency: 12.83889ms message: 'load-balancer-api-internal: resolved host name a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:45:18Z" - latency: 4.444346ms message: 'load-balancer-api-internal: tcp connection to a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:44:18Z" - latency: 6.296838ms message: 'load-balancer-api-internal: resolved host name a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:44:18Z" - latency: 5.926751ms message: 'load-balancer-api-internal: tcp connection to a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:43:18Z" - latency: 6.689ms message: 'load-balancer-api-internal: resolved host name a2f4984fcd9444ad7acb086d0dcfc54d-ef790ebf707fc95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:43:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:17:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-173-to-network-check-target-ip-10-0-140-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-173.ec2.internal uid: 5bb6f6b1-012b-49f4-9d56-2a3a4ff58a90 resourceVersion: "51402" uid: 5a2d8bcb-2e28-4206-8d25-3ecb3655a5ae spec: sourcePod: network-check-source-6947749cfc-jtzhp targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T19:24:18Z" message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.589606ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:52:18Z" - latency: 2.088764ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:51:18Z" - latency: 2.441692ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:50:18Z" - latency: 1.727561ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:49:18Z" - latency: 1.940993ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:48:18Z" - latency: 2.103962ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:47:18Z" - latency: 2.248658ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:18Z" - latency: 2.318739ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:18Z" - latency: 2.130352ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:44:18Z" - latency: 2.136128ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:43:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:17:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-173-to-network-check-target-ip-10-0-142-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-173.ec2.internal uid: 5bb6f6b1-012b-49f4-9d56-2a3a4ff58a90 resourceVersion: "51400" uid: d9abe316-13f0-406f-8139-c4becd5417aa spec: sourcePod: network-check-source-6947749cfc-jtzhp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T19:24:18Z" message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 757.925µs message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:52:18Z" - latency: 893.406µs message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:51:18Z" - latency: 855.89µs message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:50:18Z" - latency: 1.190314ms message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:49:18Z" - latency: 887.131µs message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:48:18Z" - latency: 1.091473ms message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:47:18Z" - latency: 817.303µs message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:18Z" - latency: 878.663µs message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:18Z" - latency: 843.894µs message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:44:18Z" - latency: 1.361936ms message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:43:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:17:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-173-to-network-check-target-ip-10-0-142-72 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-173.ec2.internal uid: 5bb6f6b1-012b-49f4-9d56-2a3a4ff58a90 resourceVersion: "51401" uid: 8aafe0f9-1ffe-43ac-b0a0-c8e5e285b779 spec: sourcePod: network-check-source-6947749cfc-jtzhp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T19:24:18Z" message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.296242ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:52:18Z" - latency: 2.262426ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:51:18Z" - latency: 2.12765ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:50:18Z" - latency: 2.014358ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:49:18Z" - latency: 2.235897ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:48:18Z" - latency: 2.604131ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:47:18Z" - latency: 2.100387ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:18Z" - latency: 2.146138ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:18Z" - latency: 2.12299ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:44:18Z" - latency: 2.426841ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:43:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:17:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-173-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-173.ec2.internal uid: 5bb6f6b1-012b-49f4-9d56-2a3a4ff58a90 resourceVersion: "45919" uid: 7310ce71-4e82-415d-b61b-add8ed8c6c2e spec: sourcePod: network-check-source-6947749cfc-jtzhp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T19:23:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 810.172µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:47:18Z" - latency: 1.764166ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:47:18Z" - latency: 1.028161ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:18Z" - latency: 2.04751ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:46:18Z" - latency: 1.444425ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:18Z" - latency: 1.86363ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:45:18Z" - latency: 1.24769ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:44:18Z" - latency: 1.743298ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:44:18Z" - latency: 882.028µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:43:18Z" - latency: 1.861331ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:43:18Z" kind: List metadata: resourceVersion: ""