apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T20:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-74-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-74.ec2.internal uid: a094f0c2-988c-42e1-afbc-41b198c68f77 resourceVersion: "42693" uid: fcfeca1c-b9da-4995-b2f8-1bae03f264d7 spec: sourcePod: network-check-source-7f44b6dd87-vr75d targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T20:32:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.667841ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:53:06Z" - latency: 1.272554ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:52:06Z" - latency: 1.040726ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:51:06Z" - latency: 934.779µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:50:06Z" - latency: 1.035847ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:49:06Z" - latency: 995.874µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:48:06Z" - latency: 1.155475ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:47:06Z" - latency: 1.068677ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:46:06Z" - latency: 1.064855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:45:06Z" - latency: 1.129001ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:44:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T20:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-74-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-74.ec2.internal uid: a094f0c2-988c-42e1-afbc-41b198c68f77 resourceVersion: "45227" uid: 4f1fd487-6223-4975-8bc9-25700eec0647 spec: sourcePod: network-check-source-7f44b6dd87-vr75d targetEndpoint: ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T20:31:06Z" message: 'load-balancer-api-external: tcp connection to ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.966626ms message: 'load-balancer-api-external: tcp connection to ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:55:06Z" - latency: 8.929127ms message: 'load-balancer-api-external: resolved host name ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T20:55:06Z" - latency: 5.470829ms message: 'load-balancer-api-external: tcp connection to ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:54:06Z" - latency: 7.830586ms message: 'load-balancer-api-external: resolved host name ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T20:54:06Z" - latency: 5.125245ms message: 'load-balancer-api-external: tcp connection to ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:53:06Z" - latency: 8.507376ms message: 'load-balancer-api-external: resolved host name ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T20:53:06Z" - latency: 3.510059ms message: 'load-balancer-api-external: tcp connection to ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:52:06Z" - latency: 8.295188ms message: 'load-balancer-api-external: resolved host name ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T20:52:06Z" - latency: 4.071468ms message: 'load-balancer-api-external: tcp connection to ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:51:06Z" - latency: 7.795156ms message: 'load-balancer-api-external: resolved host name ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T20:51:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T20:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-74-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-74.ec2.internal uid: a094f0c2-988c-42e1-afbc-41b198c68f77 resourceVersion: "45226" uid: 88f51071-19d3-43a5-8385-8468bf153a69 spec: sourcePod: network-check-source-7f44b6dd87-vr75d targetEndpoint: ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T20:31:06Z" message: 'load-balancer-api-internal: tcp connection to ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.322579ms message: 'load-balancer-api-internal: tcp connection to ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:55:06Z" - latency: 8.836822ms message: 'load-balancer-api-internal: resolved host name ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T20:55:06Z" - latency: 5.509089ms message: 'load-balancer-api-internal: tcp connection to ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:54:06Z" - latency: 7.717164ms message: 'load-balancer-api-internal: resolved host name ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T20:54:06Z" - latency: 5.146664ms message: 'load-balancer-api-internal: tcp connection to ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:53:06Z" - latency: 8.42098ms message: 'load-balancer-api-internal: resolved host name ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T20:53:06Z" - latency: 3.448165ms message: 'load-balancer-api-internal: tcp connection to ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:52:06Z" - latency: 8.341087ms message: 'load-balancer-api-internal: resolved host name ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T20:52:06Z" - latency: 3.63887ms message: 'load-balancer-api-internal: tcp connection to ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:51:06Z" - latency: 7.668379ms message: 'load-balancer-api-internal: resolved host name ae3642468c3e24d36990187c83bd083c-628b1c7255412805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T20:51:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T20:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-74-to-network-check-target-ip-10-0-130-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-74.ec2.internal uid: a094f0c2-988c-42e1-afbc-41b198c68f77 resourceVersion: "42691" uid: bf7a07bd-41bb-47aa-8601-b1cb2412af89 spec: sourcePod: network-check-source-7f44b6dd87-vr75d targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T20:32:06Z" message: 'network-check-target-ip-10-0-130-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.001087ms message: 'network-check-target-ip-10-0-130-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:53:06Z" - latency: 1.934901ms message: 'network-check-target-ip-10-0-130-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:52:06Z" - latency: 1.941713ms message: 'network-check-target-ip-10-0-130-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:51:06Z" - latency: 1.936415ms message: 'network-check-target-ip-10-0-130-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:50:06Z" - latency: 1.765205ms message: 'network-check-target-ip-10-0-130-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:49:06Z" - latency: 1.816274ms message: 'network-check-target-ip-10-0-130-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:48:06Z" - latency: 1.827518ms message: 'network-check-target-ip-10-0-130-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:47:06Z" - latency: 1.977316ms message: 'network-check-target-ip-10-0-130-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:46:06Z" - latency: 1.845099ms message: 'network-check-target-ip-10-0-130-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:45:06Z" - latency: 1.891408ms message: 'network-check-target-ip-10-0-130-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:44:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T20:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-74-to-network-check-target-ip-10-0-130-74 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-74.ec2.internal uid: a094f0c2-988c-42e1-afbc-41b198c68f77 resourceVersion: "42690" uid: 4400e3a3-ff68-4e42-9a31-9f63f65d6e6b spec: sourcePod: network-check-source-7f44b6dd87-vr75d targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-21T20:32:06Z" message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 810.665µs message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:53:06Z" - latency: 1.173367ms message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:52:06Z" - latency: 804.939µs message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:51:06Z" - latency: 1.146082ms message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:50:06Z" - latency: 776.612µs message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:49:06Z" - latency: 751.44µs message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:48:06Z" - latency: 827.238µs message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:47:06Z" - latency: 774.165µs message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:46:06Z" - latency: 811.867µs message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:45:06Z" - latency: 1.261741ms message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:44:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T20:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-74-to-network-check-target-ip-10-0-134-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-74.ec2.internal uid: a094f0c2-988c-42e1-afbc-41b198c68f77 resourceVersion: "42692" uid: 2d6c7618-b4e3-41a1-8c52-500ce255ab5d spec: sourcePod: network-check-source-7f44b6dd87-vr75d targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T20:32:06Z" message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.287542ms message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:53:06Z" - latency: 1.999236ms message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:52:06Z" - latency: 2.316445ms message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:51:06Z" - latency: 2.337524ms message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:50:06Z" - latency: 2.102914ms message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:49:06Z" - latency: 2.12349ms message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:48:06Z" - latency: 2.205185ms message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:47:06Z" - latency: 2.070093ms message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:46:06Z" - latency: 2.226324ms message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:45:06Z" - latency: 1.855583ms message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:44:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T20:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-74-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-74.ec2.internal uid: a094f0c2-988c-42e1-afbc-41b198c68f77 resourceVersion: "45225" uid: 9ba8f4d6-9ab5-4ae9-bd0d-e854b17d7d04 spec: sourcePod: network-check-source-7f44b6dd87-vr75d targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T20:31:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 824.586µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:55:06Z" - latency: 1.638764ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T20:55:06Z" - latency: 881.491µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:54:06Z" - latency: 1.690641ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T20:54:06Z" - latency: 827.303µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:53:06Z" - latency: 2.046011ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T20:53:06Z" - latency: 927.989µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:52:06Z" - latency: 1.704253ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T20:52:06Z" - latency: 839.951µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T20:51:06Z" - latency: 1.791038ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T20:51:06Z" kind: List metadata: resourceVersion: ""