apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T20:16:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-62-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-62.ec2.internal uid: e9a703f5-cdb7-4e66-a4d3-5d9ed096809e resourceVersion: "46157" uid: a61249ac-1454-4c37-aada-bcfea5ecc477 spec: sourcePod: network-check-source-6947749cfc-p6tgd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T20:23:50Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.229873ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:44:50Z" - latency: 1.498287ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:43:50Z" - latency: 983.258µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:42:50Z" - latency: 1.70459ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:41:50Z" - latency: 1.021189ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:40:50Z" - latency: 1.000995ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:39:50Z" - latency: 1.192673ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:38:50Z" - latency: 1.123274ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:37:50Z" - latency: 1.278542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:36:50Z" - latency: 1.301051ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:35:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T20:16:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-62-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-62.ec2.internal uid: e9a703f5-cdb7-4e66-a4d3-5d9ed096809e resourceVersion: "48361" uid: b5090621-1428-440c-9d7d-2a47f8649487 spec: sourcePod: network-check-source-6947749cfc-p6tgd targetEndpoint: aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T20:22:50Z" message: 'load-balancer-api-external: tcp connection to aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.749697ms message: 'load-balancer-api-external: tcp connection to aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:46:50Z" - latency: 9.352944ms message: 'load-balancer-api-external: resolved host name aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T20:46:50Z" - latency: 4.747982ms message: 'load-balancer-api-external: tcp connection to aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:45:50Z" - latency: 8.714358ms message: 'load-balancer-api-external: resolved host name aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T20:45:50Z" - latency: 3.698924ms message: 'load-balancer-api-external: tcp connection to aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:44:50Z" - latency: 11.128244ms message: 'load-balancer-api-external: resolved host name aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T20:44:50Z" - latency: 4.875877ms message: 'load-balancer-api-external: tcp connection to aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:43:50Z" - latency: 8.546966ms message: 'load-balancer-api-external: resolved host name aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T20:43:50Z" - latency: 5.003425ms message: 'load-balancer-api-external: tcp connection to aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:42:50Z" - latency: 8.560363ms message: 'load-balancer-api-external: resolved host name aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T20:42:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T20:16:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-62-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-62.ec2.internal uid: e9a703f5-cdb7-4e66-a4d3-5d9ed096809e resourceVersion: "48360" uid: b3f52164-4190-4fd2-8e96-4f37b9912fd1 spec: sourcePod: network-check-source-6947749cfc-p6tgd targetEndpoint: aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T20:22:50Z" message: 'load-balancer-api-internal: tcp connection to aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.850615ms message: 'load-balancer-api-internal: tcp connection to aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:46:50Z" - latency: 9.286098ms message: 'load-balancer-api-internal: resolved host name aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T20:46:50Z" - latency: 4.73346ms message: 'load-balancer-api-internal: tcp connection to aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:45:50Z" - latency: 8.768236ms message: 'load-balancer-api-internal: resolved host name aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T20:45:50Z" - latency: 3.691401ms message: 'load-balancer-api-internal: tcp connection to aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:44:50Z" - latency: 11.034491ms message: 'load-balancer-api-internal: resolved host name aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T20:44:50Z" - latency: 6.929552ms message: 'load-balancer-api-internal: tcp connection to aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:43:50Z" - latency: 8.581643ms message: 'load-balancer-api-internal: resolved host name aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T20:43:50Z" - latency: 5.015557ms message: 'load-balancer-api-internal: tcp connection to aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:42:50Z" - latency: 8.488774ms message: 'load-balancer-api-internal: resolved host name aee67b6bd2f084dd182704779d31075f-35033ec9b0ad589c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T20:42:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T20:16:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-62-to-network-check-target-ip-10-0-135-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-62.ec2.internal uid: e9a703f5-cdb7-4e66-a4d3-5d9ed096809e resourceVersion: "46156" uid: 8caaafe9-b3ae-4c03-9cba-63e3ab22a574 spec: sourcePod: network-check-source-6947749cfc-p6tgd targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T20:23:50Z" message: 'network-check-target-ip-10-0-135-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.152196ms message: 'network-check-target-ip-10-0-135-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:44:50Z" - latency: 2.710872ms message: 'network-check-target-ip-10-0-135-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:43:50Z" - latency: 2.251574ms message: 'network-check-target-ip-10-0-135-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:42:50Z" - latency: 2.138786ms message: 'network-check-target-ip-10-0-135-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:41:50Z" - latency: 2.446747ms message: 'network-check-target-ip-10-0-135-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:40:50Z" - latency: 2.431557ms message: 'network-check-target-ip-10-0-135-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:39:50Z" - latency: 2.426256ms message: 'network-check-target-ip-10-0-135-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:38:50Z" - latency: 2.140983ms message: 'network-check-target-ip-10-0-135-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:37:50Z" - latency: 1.644085ms message: 'network-check-target-ip-10-0-135-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:36:50Z" - latency: 3.086429ms message: 'network-check-target-ip-10-0-135-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:35:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T20:16:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-62-to-network-check-target-ip-10-0-136-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-62.ec2.internal uid: e9a703f5-cdb7-4e66-a4d3-5d9ed096809e resourceVersion: "46154" uid: a1369c4d-9529-44c7-acce-b156a02fb981 spec: sourcePod: network-check-source-6947749cfc-p6tgd targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T20:23:50Z" message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 927.819µs message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:44:50Z" - latency: 978.519µs message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:43:50Z" - latency: 917.99µs message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:42:50Z" - latency: 1.010527ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:41:50Z" - latency: 1.014933ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:40:50Z" - latency: 805.788µs message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:39:50Z" - latency: 1.066501ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:38:50Z" - latency: 1.866317ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:37:50Z" - latency: 902.47µs message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:36:50Z" - latency: 1.100135ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:35:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T20:16:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-62-to-network-check-target-ip-10-0-137-64 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-62.ec2.internal uid: e9a703f5-cdb7-4e66-a4d3-5d9ed096809e resourceVersion: "46155" uid: d1b7e3af-bd64-465b-b2f2-49d2a8d9afb1 spec: sourcePod: network-check-source-6947749cfc-p6tgd targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T20:23:50Z" message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.235457ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:44:50Z" - latency: 2.653939ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:43:50Z" - latency: 2.82286ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:42:50Z" - latency: 2.156376ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:41:50Z" - latency: 2.307081ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:40:50Z" - latency: 2.643411ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:39:50Z" - latency: 2.341683ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:38:50Z" - latency: 2.63735ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:37:50Z" - latency: 1.775257ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:36:50Z" - latency: 2.478647ms message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:35:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T20:16:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-62-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-62.ec2.internal uid: e9a703f5-cdb7-4e66-a4d3-5d9ed096809e resourceVersion: "48359" uid: 1d8fd6f2-b382-4517-888d-35682a29786a spec: sourcePod: network-check-source-6947749cfc-p6tgd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T20:22:50Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 928.87µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:46:50Z" - latency: 1.754418ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T20:46:50Z" - latency: 940.94µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:45:50Z" - latency: 1.7166ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T20:45:50Z" - latency: 872.115µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:44:50Z" - latency: 1.832188ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T20:44:50Z" - latency: 1.079407ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:43:50Z" - latency: 1.753141ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T20:43:50Z" - latency: 793.407µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T20:42:50Z" - latency: 1.779186ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T20:42:50Z" kind: List metadata: resourceVersion: ""