apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:14:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-77-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-77.ec2.internal uid: 883b636c-9b50-4a87-b6e9-1b6384ff0841 resourceVersion: "30205" uid: 85133ef0-0093-4848-9fe4-b53d0bee5f98 spec: sourcePod: network-check-source-6947749cfc-jd5f4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T23:21:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.433868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:28:38Z" - latency: 926.032µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:27:38Z" - latency: 853.193µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:26:38Z" - latency: 1.133103ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:25:38Z" - latency: 958.86µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:24:38Z" - latency: 1.06367ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:23:38Z" - latency: 1.196698ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:22:38Z" - latency: 1.114462ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:21:38Z" - latency: 1.105648ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:20:38Z" - latency: 1.629725ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:19:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:14:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-77-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-77.ec2.internal uid: 883b636c-9b50-4a87-b6e9-1b6384ff0841 resourceVersion: "32827" uid: 83a091ad-1bad-4258-8025-ad918d806ba2 spec: sourcePod: network-check-source-6947749cfc-jd5f4 targetEndpoint: a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T23:20:38Z" message: 'load-balancer-api-external: tcp connection to a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.21963ms message: 'load-balancer-api-external: tcp connection to a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:32:38Z" - latency: 7.514721ms message: 'load-balancer-api-external: resolved host name a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:32:38Z" - latency: 5.475696ms message: 'load-balancer-api-external: tcp connection to a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:31:38Z" - latency: 8.414948ms message: 'load-balancer-api-external: resolved host name a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:31:38Z" - latency: 3.574161ms message: 'load-balancer-api-external: tcp connection to a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:30:38Z" - latency: 9.536476ms message: 'load-balancer-api-external: resolved host name a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:30:38Z" - latency: 5.328311ms message: 'load-balancer-api-external: tcp connection to a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:29:38Z" - latency: 12.826326ms message: 'load-balancer-api-external: resolved host name a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:29:38Z" - latency: 4.364486ms message: 'load-balancer-api-external: tcp connection to a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:28:38Z" - latency: 8.725099ms message: 'load-balancer-api-external: resolved host name a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:28:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:14:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-77-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-77.ec2.internal uid: 883b636c-9b50-4a87-b6e9-1b6384ff0841 resourceVersion: "32828" uid: b93e22e6-a0ed-4ab6-a739-cbe11d2043f8 spec: sourcePod: network-check-source-6947749cfc-jd5f4 targetEndpoint: a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T23:20:38Z" message: 'load-balancer-api-internal: tcp connection to a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.812266ms message: 'load-balancer-api-internal: tcp connection to a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:32:38Z" - latency: 7.495925ms message: 'load-balancer-api-internal: resolved host name a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:32:38Z" - latency: 5.516077ms message: 'load-balancer-api-internal: tcp connection to a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:31:38Z" - latency: 8.352777ms message: 'load-balancer-api-internal: resolved host name a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:31:38Z" - latency: 3.571097ms message: 'load-balancer-api-internal: tcp connection to a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:30:38Z" - latency: 9.468484ms message: 'load-balancer-api-internal: resolved host name a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:30:38Z" - latency: 5.488788ms message: 'load-balancer-api-internal: tcp connection to a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:29:38Z" - latency: 12.771255ms message: 'load-balancer-api-internal: resolved host name a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:29:38Z" - latency: 4.418561ms message: 'load-balancer-api-internal: tcp connection to a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:28:38Z" - latency: 8.691922ms message: 'load-balancer-api-internal: resolved host name a8a95c8b4644041beb74e8ac70ba8aef-026e242bd61bd220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:28:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:14:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-77-to-network-check-target-ip-10-0-130-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-77.ec2.internal uid: 883b636c-9b50-4a87-b6e9-1b6384ff0841 resourceVersion: "30204" uid: 685b59e6-ffcd-488d-ba54-df4f63a425de spec: sourcePod: network-check-source-6947749cfc-jd5f4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T23:21:38Z" message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.93023ms message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:28:38Z" - latency: 1.919081ms message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:27:38Z" - latency: 1.769524ms message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:26:38Z" - latency: 1.935798ms message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:25:38Z" - latency: 1.739002ms message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:24:38Z" - latency: 2.132619ms message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:23:38Z" - latency: 1.997815ms message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:22:38Z" - latency: 2.231235ms message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:21:38Z" - latency: 1.938882ms message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:20:38Z" - latency: 1.953106ms message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:19:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:14:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-77-to-network-check-target-ip-10-0-134-77 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-77.ec2.internal uid: 883b636c-9b50-4a87-b6e9-1b6384ff0841 resourceVersion: "30202" uid: d499e3ae-e7cd-4656-acbf-ddf2a4d20575 spec: sourcePod: network-check-source-6947749cfc-jd5f4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T23:21:38Z" message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.650221ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:28:38Z" - latency: 1.112785ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:27:38Z" - latency: 834.279µs message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:26:38Z" - latency: 917.463µs message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:25:38Z" - latency: 1.210483ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:24:38Z" - latency: 1.140856ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:23:38Z" - latency: 1.006405ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:22:38Z" - latency: 851.309µs message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:21:38Z" - latency: 917.543µs message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:20:38Z" - latency: 992.858µs message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:19:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:14:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-77-to-network-check-target-ip-10-0-135-254 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-77.ec2.internal uid: 883b636c-9b50-4a87-b6e9-1b6384ff0841 resourceVersion: "30203" uid: 4d9a24c1-1aa5-4219-805e-76f155c8b68c spec: sourcePod: network-check-source-6947749cfc-jd5f4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T23:21:38Z" message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.34894ms message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:28:38Z" - latency: 2.642507ms message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:27:38Z" - latency: 1.99827ms message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:26:38Z" - latency: 2.287173ms message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:25:38Z" - latency: 2.241334ms message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:24:38Z" - latency: 2.249983ms message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:23:38Z" - latency: 2.392253ms message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:22:38Z" - latency: 2.782426ms message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:21:38Z" - latency: 2.826485ms message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:20:38Z" - latency: 2.396584ms message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:19:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:14:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-77-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-77.ec2.internal uid: 883b636c-9b50-4a87-b6e9-1b6384ff0841 resourceVersion: "32826" uid: f1f37cd0-08b6-419a-82c5-f83c8c5a477f spec: sourcePod: network-check-source-6947749cfc-jd5f4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T23:20:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.070694ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:32:38Z" - latency: 1.747855ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T23:32:38Z" - latency: 815.176µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:31:38Z" - latency: 2.596349ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T23:31:38Z" - latency: 1.47482ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:30:38Z" - latency: 1.770007ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T23:30:38Z" - latency: 943.31µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:29:38Z" - latency: 1.745381ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T23:29:38Z" - latency: 1.086361ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:28:38Z" - latency: 1.678004ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T23:28:38Z" kind: List metadata: resourceVersion: ""