apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:57:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-48-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-48.ec2.internal uid: 824b76ac-41ac-44ca-8771-9b70f481f4b8 resourceVersion: "38216" uid: 585ac3d3-4049-4137-be14-a7ab2f91f279 spec: sourcePod: network-check-source-8894fc9bd-c8jsl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T20:04:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.139024ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:25:30Z" - latency: 765.369µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:24:30Z" - latency: 1.09954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:23:30Z" - latency: 1.390907ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:22:30Z" - latency: 1.183704ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:21:30Z" - latency: 1.108246ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:20:30Z" - latency: 1.032461ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:19:30Z" - latency: 1.715073ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:18:30Z" - latency: 1.31232ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:17:30Z" - latency: 853.513µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:16:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:57:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-48-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-48.ec2.internal uid: 824b76ac-41ac-44ca-8771-9b70f481f4b8 resourceVersion: "35077" uid: fe79e717-2677-4bf4-9e40-829d2f722405 spec: sourcePod: network-check-source-8894fc9bd-c8jsl targetEndpoint: abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T20:03:30Z" message: 'load-balancer-api-external: tcp connection to abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.220575ms message: 'load-balancer-api-external: tcp connection to abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:21:30Z" - latency: 7.794869ms message: 'load-balancer-api-external: resolved host name abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:21:30Z" - latency: 5.00685ms message: 'load-balancer-api-external: tcp connection to abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:20:30Z" - latency: 8.369838ms message: 'load-balancer-api-external: resolved host name abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:20:30Z" - latency: 4.488367ms message: 'load-balancer-api-external: tcp connection to abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:19:30Z" - latency: 6.927699ms message: 'load-balancer-api-external: resolved host name abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:19:30Z" - latency: 5.250263ms message: 'load-balancer-api-external: tcp connection to abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:18:30Z" - latency: 8.009574ms message: 'load-balancer-api-external: resolved host name abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:18:30Z" - latency: 4.560703ms message: 'load-balancer-api-external: tcp connection to abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:17:30Z" - latency: 7.375183ms message: 'load-balancer-api-external: resolved host name abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:17:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:57:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-48-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-48.ec2.internal uid: 824b76ac-41ac-44ca-8771-9b70f481f4b8 resourceVersion: "35078" uid: 959b109e-db5d-42ee-a7e9-fb69bf26e7e1 spec: sourcePod: network-check-source-8894fc9bd-c8jsl targetEndpoint: abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T20:03:30Z" message: 'load-balancer-api-internal: tcp connection to abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.189348ms message: 'load-balancer-api-internal: tcp connection to abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:21:30Z" - latency: 7.750524ms message: 'load-balancer-api-internal: resolved host name abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:21:30Z" - latency: 5.649537ms message: 'load-balancer-api-internal: tcp connection to abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:20:30Z" - latency: 8.534908ms message: 'load-balancer-api-internal: resolved host name abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:20:30Z" - latency: 4.294318ms message: 'load-balancer-api-internal: tcp connection to abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:19:30Z" - latency: 6.837601ms message: 'load-balancer-api-internal: resolved host name abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:19:30Z" - latency: 4.73351ms message: 'load-balancer-api-internal: tcp connection to abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:18:30Z" - latency: 8.093042ms message: 'load-balancer-api-internal: resolved host name abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:18:30Z" - latency: 4.557141ms message: 'load-balancer-api-internal: tcp connection to abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:17:30Z" - latency: 7.316899ms message: 'load-balancer-api-internal: resolved host name abb9c8bb95cf54d749dff3ad7b93926c-55fde18ec7c9d109.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:17:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:57:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-48-to-network-check-target-ip-10-0-128-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-48.ec2.internal uid: 824b76ac-41ac-44ca-8771-9b70f481f4b8 resourceVersion: "38213" uid: a115060e-3c78-4284-9ac4-087311b8ba21 spec: sourcePod: network-check-source-8894fc9bd-c8jsl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:04:30Z" message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 951.887µs message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:25:30Z" - latency: 1.123397ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:24:30Z" - latency: 964.715µs message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:23:30Z" - latency: 989.203µs message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:22:30Z" - latency: 1.1781ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:21:30Z" - latency: 1.298336ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:20:30Z" - latency: 1.149202ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:19:30Z" - latency: 1.235522ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:18:30Z" - latency: 962.061µs message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:17:30Z" - latency: 739.782µs message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:16:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:57:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-48-to-network-check-target-ip-10-0-131-77 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-48.ec2.internal uid: 824b76ac-41ac-44ca-8771-9b70f481f4b8 resourceVersion: "38215" uid: b60b9fb8-a10f-4e0b-9eff-5e58e39160d1 spec: sourcePod: network-check-source-8894fc9bd-c8jsl targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:04:30Z" message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.983939ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:25:30Z" - latency: 1.747907ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:24:30Z" - latency: 2.137308ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:23:30Z" - latency: 1.71436ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:22:30Z" - latency: 1.899779ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:21:30Z" - latency: 1.869339ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:20:30Z" - latency: 1.703104ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:19:30Z" - latency: 2.079921ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:18:30Z" - latency: 1.806705ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:17:30Z" - latency: 1.955921ms message: 'network-check-target-ip-10-0-131-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:16:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:57:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-48-to-network-check-target-ip-10-0-138-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-48.ec2.internal uid: 824b76ac-41ac-44ca-8771-9b70f481f4b8 resourceVersion: "38214" uid: bec54664-8416-4317-99f9-6f705ef28a84 spec: sourcePod: network-check-source-8894fc9bd-c8jsl targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:04:30Z" message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.857621ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:25:30Z" - latency: 1.971566ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:24:30Z" - latency: 1.764726ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:23:30Z" - latency: 2.004613ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:22:30Z" - latency: 2.446413ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:21:30Z" - latency: 2.136279ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:20:30Z" - latency: 2.123011ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:19:30Z" - latency: 2.694324ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:18:30Z" - latency: 2.210253ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:17:30Z" - latency: 1.951947ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:16:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:57:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-48-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-48.ec2.internal uid: 824b76ac-41ac-44ca-8771-9b70f481f4b8 resourceVersion: "35075" uid: 3a1e5e32-e759-4403-a6ce-9d97189bb998 spec: sourcePod: network-check-source-8894fc9bd-c8jsl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T20:03:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 896.802µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:21:30Z" - latency: 1.769062ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:21:30Z" - latency: 781.147µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:20:30Z" - latency: 1.815685ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:20:30Z" - latency: 850.316µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:19:30Z" - latency: 1.59717ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:19:30Z" - latency: 1.514013ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:18:30Z" - latency: 1.821055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:18:30Z" - latency: 725.893µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:17:30Z" - latency: 1.880269ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:17:30Z" kind: List metadata: resourceVersion: ""