apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T15:34:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-63-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-63.ec2.internal uid: 50490d11-4668-42b1-a9d8-97e56dca8689 resourceVersion: "18149" uid: 189f9a88-9ba1-439c-9603-2a222acd2360 spec: sourcePod: network-check-source-7f44b6dd87-6jd8v targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-20T15:41:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.028234ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:48:55Z" - latency: 1.229798ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:47:55Z" - latency: 1.008888ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:46:55Z" - latency: 878.791µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:45:55Z" - latency: 949.326µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:44:55Z" - latency: 1.177635ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:43:55Z" - latency: 1.017039ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:42:55Z" - latency: 1.109984ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:41:55Z" - latency: 963.237µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:40:55Z" - latency: 916.768µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:39:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T15:34:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-63-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-63.ec2.internal uid: 50490d11-4668-42b1-a9d8-97e56dca8689 resourceVersion: "20192" uid: 6f5b5714-4700-4557-996c-3e526e2b5778 spec: sourcePod: network-check-source-7f44b6dd87-6jd8v targetEndpoint: a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T15:40:55Z" message: 'load-balancer-api-external: tcp connection to a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.281765ms message: 'load-balancer-api-external: tcp connection to a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:52:55Z" - latency: 8.629982ms message: 'load-balancer-api-external: resolved host name a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T15:52:55Z" - latency: 5.457255ms message: 'load-balancer-api-external: tcp connection to a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:51:55Z" - latency: 11.082932ms message: 'load-balancer-api-external: resolved host name a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T15:51:55Z" - latency: 4.995866ms message: 'load-balancer-api-external: tcp connection to a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:50:55Z" - latency: 9.978668ms message: 'load-balancer-api-external: resolved host name a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T15:50:55Z" - latency: 4.99198ms message: 'load-balancer-api-external: tcp connection to a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:49:55Z" - latency: 8.490058ms message: 'load-balancer-api-external: resolved host name a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T15:49:55Z" - latency: 5.16645ms message: 'load-balancer-api-external: tcp connection to a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:48:55Z" - latency: 8.403759ms message: 'load-balancer-api-external: resolved host name a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T15:48:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T15:34:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-63-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-63.ec2.internal uid: 50490d11-4668-42b1-a9d8-97e56dca8689 resourceVersion: "20193" uid: 40391ed3-3150-4805-9152-30f61ae0f805 spec: sourcePod: network-check-source-7f44b6dd87-6jd8v targetEndpoint: a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T15:40:55Z" message: 'load-balancer-api-internal: tcp connection to a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.294037ms message: 'load-balancer-api-internal: tcp connection to a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:52:55Z" - latency: 8.719729ms message: 'load-balancer-api-internal: resolved host name a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T15:52:55Z" - latency: 5.422514ms message: 'load-balancer-api-internal: tcp connection to a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:51:55Z" - latency: 11.140327ms message: 'load-balancer-api-internal: resolved host name a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T15:51:55Z" - latency: 5.971349ms message: 'load-balancer-api-internal: tcp connection to a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:50:55Z" - latency: 10.047439ms message: 'load-balancer-api-internal: resolved host name a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T15:50:55Z" - latency: 4.9662ms message: 'load-balancer-api-internal: tcp connection to a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:49:55Z" - latency: 8.55094ms message: 'load-balancer-api-internal: resolved host name a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T15:49:55Z" - latency: 5.16186ms message: 'load-balancer-api-internal: tcp connection to a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:48:55Z" - latency: 8.484525ms message: 'load-balancer-api-internal: resolved host name a703670aa4590473ba5beabb64e56bb5-a1c8df97e33a008f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T15:48:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T15:34:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-63-to-network-check-target-ip-10-0-137-255 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-63.ec2.internal uid: 50490d11-4668-42b1-a9d8-97e56dca8689 resourceVersion: "18148" uid: bee2e3de-8116-4709-9e78-e2693a657695 spec: sourcePod: network-check-source-7f44b6dd87-6jd8v targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-20T15:41:55Z" message: 'network-check-target-ip-10-0-137-255: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.14685ms message: 'network-check-target-ip-10-0-137-255: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:48:55Z" - latency: 2.099844ms message: 'network-check-target-ip-10-0-137-255: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:47:55Z" - latency: 2.200265ms message: 'network-check-target-ip-10-0-137-255: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:46:55Z" - latency: 2.403829ms message: 'network-check-target-ip-10-0-137-255: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:45:55Z" - latency: 2.086185ms message: 'network-check-target-ip-10-0-137-255: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:44:55Z" - latency: 2.160691ms message: 'network-check-target-ip-10-0-137-255: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:43:55Z" - latency: 2.116166ms message: 'network-check-target-ip-10-0-137-255: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:42:55Z" - latency: 2.132501ms message: 'network-check-target-ip-10-0-137-255: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:41:55Z" - latency: 1.990443ms message: 'network-check-target-ip-10-0-137-255: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:40:55Z" - latency: 2.008839ms message: 'network-check-target-ip-10-0-137-255: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:39:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T15:34:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-63-to-network-check-target-ip-10-0-137-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-63.ec2.internal uid: 50490d11-4668-42b1-a9d8-97e56dca8689 resourceVersion: "18146" uid: 67730abe-5fed-469e-a056-65144ad45077 spec: sourcePod: network-check-source-7f44b6dd87-6jd8v targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T15:41:55Z" message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 903.27µs message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:48:55Z" - latency: 1.428617ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:47:55Z" - latency: 788.112µs message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:46:55Z" - latency: 1.31329ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:45:55Z" - latency: 811.145µs message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:44:55Z" - latency: 806.47µs message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:43:55Z" - latency: 860.844µs message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:42:55Z" - latency: 871.641µs message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:41:55Z" - latency: 855.822µs message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:40:55Z" - latency: 860.345µs message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:39:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T15:34:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-63-to-network-check-target-ip-10-0-140-154 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-63.ec2.internal uid: 50490d11-4668-42b1-a9d8-97e56dca8689 resourceVersion: "18147" uid: e62ea705-fd94-4797-bd40-81e4848c7675 spec: sourcePod: network-check-source-7f44b6dd87-6jd8v targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T15:41:55Z" message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.766292ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:48:55Z" - latency: 2.030323ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:47:55Z" - latency: 1.916764ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:46:55Z" - latency: 1.995428ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:45:55Z" - latency: 1.906016ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:44:55Z" - latency: 2.079038ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:43:55Z" - latency: 2.07447ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:42:55Z" - latency: 2.052015ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:41:55Z" - latency: 1.914533ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:40:55Z" - latency: 1.616153ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:39:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T15:34:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-63-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-63.ec2.internal uid: 50490d11-4668-42b1-a9d8-97e56dca8689 resourceVersion: "20191" uid: 7b43ae49-7d74-4452-8719-68731e7de859 spec: sourcePod: network-check-source-7f44b6dd87-6jd8v targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-20T15:40:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 946.977µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:52:55Z" - latency: 1.918792ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T15:52:55Z" - latency: 983.79µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:51:55Z" - latency: 2.013933ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T15:51:55Z" - latency: 901.215µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:50:55Z" - latency: 1.965805ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T15:50:55Z" - latency: 1.127301ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:49:55Z" - latency: 1.797994ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T15:49:55Z" - latency: 833.596µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T15:48:55Z" - latency: 1.804499ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T15:48:55Z" kind: List metadata: resourceVersion: ""