apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T03:22:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-231-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-231.ec2.internal uid: 2a66dac2-4e08-4ff8-96b2-94203d54c7d9 resourceVersion: "43881" uid: 7325fc98-a6b4-4ac7-b56c-7467030fd71b spec: sourcePod: network-check-source-7f44b6dd87-xn5b6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T03:29:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.154989ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:50:53Z" - latency: 1.086019ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:49:53Z" - latency: 998.988µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:48:53Z" - latency: 1.022742ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:47:53Z" - latency: 1.123302ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:46:53Z" - latency: 744.729µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:45:53Z" - latency: 1.191654ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:44:53Z" - latency: 827.402µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:43:53Z" - latency: 962.712µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:42:53Z" - latency: 977.556µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:41:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T03:22:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-231-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-231.ec2.internal uid: 2a66dac2-4e08-4ff8-96b2-94203d54c7d9 resourceVersion: "46094" uid: 9acd6a74-e791-442d-ba2d-8e42e6c73e91 spec: sourcePod: network-check-source-7f44b6dd87-xn5b6 targetEndpoint: a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T03:28:53Z" message: 'load-balancer-api-external: tcp connection to a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.509031ms message: 'load-balancer-api-external: tcp connection to a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:52:53Z" - latency: 6.685548ms message: 'load-balancer-api-external: resolved host name a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T03:52:53Z" - latency: 5.532572ms message: 'load-balancer-api-external: tcp connection to a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:51:53Z" - latency: 7.136027ms message: 'load-balancer-api-external: resolved host name a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T03:51:53Z" - latency: 3.559911ms message: 'load-balancer-api-external: tcp connection to a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:50:53Z" - latency: 6.801102ms message: 'load-balancer-api-external: resolved host name a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T03:50:53Z" - latency: 4.426199ms message: 'load-balancer-api-external: tcp connection to a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:49:53Z" - latency: 6.582182ms message: 'load-balancer-api-external: resolved host name a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T03:49:53Z" - latency: 5.374231ms message: 'load-balancer-api-external: tcp connection to a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:48:53Z" - latency: 6.237841ms message: 'load-balancer-api-external: resolved host name a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T03:48:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T03:22:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-231-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-231.ec2.internal uid: 2a66dac2-4e08-4ff8-96b2-94203d54c7d9 resourceVersion: "46093" uid: b74da78c-fb46-4a16-930e-1b3a3bbb9665 spec: sourcePod: network-check-source-7f44b6dd87-xn5b6 targetEndpoint: a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T03:28:53Z" message: 'load-balancer-api-internal: tcp connection to a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.440928ms message: 'load-balancer-api-internal: tcp connection to a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:52:53Z" - latency: 6.708523ms message: 'load-balancer-api-internal: resolved host name a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T03:52:53Z" - latency: 5.558626ms message: 'load-balancer-api-internal: tcp connection to a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:51:53Z" - latency: 6.947593ms message: 'load-balancer-api-internal: resolved host name a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T03:51:53Z" - latency: 3.457016ms message: 'load-balancer-api-internal: tcp connection to a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:50:53Z" - latency: 6.716424ms message: 'load-balancer-api-internal: resolved host name a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T03:50:53Z" - latency: 3.41654ms message: 'load-balancer-api-internal: tcp connection to a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:49:53Z" - latency: 6.514296ms message: 'load-balancer-api-internal: resolved host name a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T03:49:53Z" - latency: 5.413594ms message: 'load-balancer-api-internal: tcp connection to a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:48:53Z" - latency: 6.155285ms message: 'load-balancer-api-internal: resolved host name a664875465fa74abca4ad5d4e5a73e88-972ee68c2dba9e8b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T03:48:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T03:22:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-231-to-network-check-target-ip-10-0-135-231 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-231.ec2.internal uid: 2a66dac2-4e08-4ff8-96b2-94203d54c7d9 resourceVersion: "43878" uid: b49d9ad3-9417-49a9-87fc-6a0e2825de76 spec: sourcePod: network-check-source-7f44b6dd87-xn5b6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T03:29:53Z" message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 850.824µs message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:50:53Z" - latency: 1.145561ms message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:49:53Z" - latency: 732.885µs message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:48:53Z" - latency: 855.637µs message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:47:53Z" - latency: 988.442µs message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:46:53Z" - latency: 816.204µs message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:45:53Z" - latency: 762.974µs message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:44:53Z" - latency: 887.608µs message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:43:53Z" - latency: 854.15µs message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:42:53Z" - latency: 817.39µs message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:41:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T03:22:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-231-to-network-check-target-ip-10-0-141-29 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-231.ec2.internal uid: 2a66dac2-4e08-4ff8-96b2-94203d54c7d9 resourceVersion: "43879" uid: f267345b-5113-45c5-8d25-694ecb249bcb spec: sourcePod: network-check-source-7f44b6dd87-xn5b6 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T03:29:53Z" message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.95048ms message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:50:53Z" - latency: 1.933456ms message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:49:53Z" - latency: 1.594534ms message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:48:53Z" - latency: 1.754289ms message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:47:53Z" - latency: 1.758245ms message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:46:53Z" - latency: 1.844099ms message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:45:53Z" - latency: 1.893517ms message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:44:53Z" - latency: 1.95187ms message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:43:53Z" - latency: 1.700459ms message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:42:53Z" - latency: 2.132571ms message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:41:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T03:22:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-231-to-network-check-target-ip-10-0-141-36 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-231.ec2.internal uid: 2a66dac2-4e08-4ff8-96b2-94203d54c7d9 resourceVersion: "43880" uid: 95277a43-26b3-4b50-af7d-f18d61f59707 spec: sourcePod: network-check-source-7f44b6dd87-xn5b6 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-28T03:29:53Z" message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.208044ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:50:53Z" - latency: 2.088137ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:49:53Z" - latency: 1.90566ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:48:53Z" - latency: 2.154828ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:47:53Z" - latency: 2.068477ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:46:53Z" - latency: 1.744193ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:45:53Z" - latency: 1.903099ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:44:53Z" - latency: 2.350002ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:43:53Z" - latency: 2.168893ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:42:53Z" - latency: 2.01851ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:41:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T03:22:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-231-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-231.ec2.internal uid: 2a66dac2-4e08-4ff8-96b2-94203d54c7d9 resourceVersion: "46092" uid: f79ca93a-7320-4d42-a9a3-a344e51bf7e5 spec: sourcePod: network-check-source-7f44b6dd87-xn5b6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T03:28:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.009048ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:52:53Z" - latency: 1.756553ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T03:52:53Z" - latency: 822.199µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:51:53Z" - latency: 1.830314ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T03:51:53Z" - latency: 846.999µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:50:53Z" - latency: 2.304279ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T03:50:53Z" - latency: 791.325µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:49:53Z" - latency: 1.909068ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T03:49:53Z" - latency: 1.083008ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T03:48:53Z" - latency: 1.580495ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T03:48:53Z" kind: List metadata: resourceVersion: ""