apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T15:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-101-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-101.ec2.internal uid: 92c2c4af-a313-4cfb-b953-81c5e4fe93b4 resourceVersion: "40508" uid: 6c8ed8f8-37ce-4753-a05a-a97b6ab2525b spec: sourcePod: network-check-source-7b678d77c7-s7ggn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T15:08:34Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 598.002µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:57:34Z" - latency: 781.251µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:56:34Z" - latency: 978.31µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:55:34Z" - latency: 745.118µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:54:34Z" - latency: 1.667298ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:53:34Z" - latency: 802.962µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:52:34Z" - latency: 872.73µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:51:34Z" - latency: 1.283125ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:50:34Z" - latency: 1.116143ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:49:34Z" - latency: 955.539µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:48:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T15:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-101-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-101.ec2.internal uid: 92c2c4af-a313-4cfb-b953-81c5e4fe93b4 resourceVersion: "39481" uid: 09536fe3-56c2-4cdd-a6c5-77f8cb7122df spec: sourcePod: network-check-source-7b678d77c7-s7ggn targetEndpoint: a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T15:07:34Z" message: 'load-balancer-api-external: tcp connection to a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.581854ms message: 'load-balancer-api-external: tcp connection to a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:55:34Z" - latency: 8.533577ms message: 'load-balancer-api-external: resolved host name a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:55:34Z" - latency: 5.429045ms message: 'load-balancer-api-external: tcp connection to a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:54:34Z" - latency: 9.258008ms message: 'load-balancer-api-external: resolved host name a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:54:34Z" - latency: 5.10274ms message: 'load-balancer-api-external: tcp connection to a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:53:34Z" - latency: 10.761382ms message: 'load-balancer-api-external: resolved host name a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:53:34Z" - latency: 4.731925ms message: 'load-balancer-api-external: tcp connection to a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:52:34Z" - latency: 8.246636ms message: 'load-balancer-api-external: resolved host name a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:52:34Z" - latency: 4.379344ms message: 'load-balancer-api-external: tcp connection to a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:51:34Z" - latency: 8.073165ms message: 'load-balancer-api-external: resolved host name a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:51:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T15:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-101-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-101.ec2.internal uid: 92c2c4af-a313-4cfb-b953-81c5e4fe93b4 resourceVersion: "39480" uid: 9d85ca8d-48f7-4b8a-8af4-874d6cbe60a0 spec: sourcePod: network-check-source-7b678d77c7-s7ggn targetEndpoint: a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T15:07:34Z" message: 'load-balancer-api-internal: tcp connection to a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.614467ms message: 'load-balancer-api-internal: tcp connection to a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:55:34Z" - latency: 8.466445ms message: 'load-balancer-api-internal: resolved host name a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:55:34Z" - latency: 5.430114ms message: 'load-balancer-api-internal: tcp connection to a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:54:34Z" - latency: 9.19475ms message: 'load-balancer-api-internal: resolved host name a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:54:34Z" - latency: 5.176505ms message: 'load-balancer-api-internal: tcp connection to a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:53:34Z" - latency: 10.657627ms message: 'load-balancer-api-internal: resolved host name a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:53:34Z" - latency: 3.436317ms message: 'load-balancer-api-internal: tcp connection to a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:52:34Z" - latency: 8.325795ms message: 'load-balancer-api-internal: resolved host name a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:52:34Z" - latency: 5.175538ms message: 'load-balancer-api-internal: tcp connection to a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:51:34Z" - latency: 8.119504ms message: 'load-balancer-api-internal: resolved host name a461a1042b4694e61919c01d77fc1b70-ba42f3684789f220.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:51:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T15:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-101-to-network-check-target-ip-10-0-129-76 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-101.ec2.internal uid: 92c2c4af-a313-4cfb-b953-81c5e4fe93b4 resourceVersion: "40507" uid: 199375f5-5ec3-46ad-b6f0-311316a5771a spec: sourcePod: network-check-source-7b678d77c7-s7ggn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T15:08:34Z" message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.274597ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:57:34Z" - latency: 1.767058ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:56:34Z" - latency: 2.228602ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:55:34Z" - latency: 2.151201ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:54:34Z" - latency: 2.996185ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:53:34Z" - latency: 2.129849ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:52:34Z" - latency: 2.355308ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:51:34Z" - latency: 2.436849ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:50:34Z" - latency: 1.817233ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:49:34Z" - latency: 2.530761ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:48:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T15:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-101-to-network-check-target-ip-10-0-139-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-101.ec2.internal uid: 92c2c4af-a313-4cfb-b953-81c5e4fe93b4 resourceVersion: "40505" uid: 260deee8-3be8-4c3f-b750-c71841276788 spec: sourcePod: network-check-source-7b678d77c7-s7ggn targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T15:08:34Z" message: 'network-check-target-ip-10-0-139-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.05679ms message: 'network-check-target-ip-10-0-139-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:57:34Z" - latency: 789.175µs message: 'network-check-target-ip-10-0-139-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:56:34Z" - latency: 735.119µs message: 'network-check-target-ip-10-0-139-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:55:34Z" - latency: 858.42µs message: 'network-check-target-ip-10-0-139-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:54:34Z" - latency: 1.206473ms message: 'network-check-target-ip-10-0-139-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:53:34Z" - latency: 797.532µs message: 'network-check-target-ip-10-0-139-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:52:34Z" - latency: 827.356µs message: 'network-check-target-ip-10-0-139-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:51:34Z" - latency: 955.546µs message: 'network-check-target-ip-10-0-139-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:50:34Z" - latency: 723.126µs message: 'network-check-target-ip-10-0-139-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:49:34Z" - latency: 804.447µs message: 'network-check-target-ip-10-0-139-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:48:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T15:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-101-to-network-check-target-ip-10-0-139-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-101.ec2.internal uid: 92c2c4af-a313-4cfb-b953-81c5e4fe93b4 resourceVersion: "40506" uid: 99e34812-96fd-441f-84a1-6159fc29d670 spec: sourcePod: network-check-source-7b678d77c7-s7ggn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T15:08:34Z" message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.132537ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:57:34Z" - latency: 2.068835ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:56:34Z" - latency: 2.143482ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:55:34Z" - latency: 2.215356ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:54:34Z" - latency: 2.146993ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:53:34Z" - latency: 1.98316ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:52:34Z" - latency: 2.381247ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:51:34Z" - latency: 2.146475ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:50:34Z" - latency: 1.849574ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:49:34Z" - latency: 2.352578ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:48:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T15:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-101-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-101.ec2.internal uid: 92c2c4af-a313-4cfb-b953-81c5e4fe93b4 resourceVersion: "39479" uid: abb74b4d-0df6-40cd-b26b-1a5e0f2c1b55 spec: sourcePod: network-check-source-7b678d77c7-s7ggn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T15:07:34Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 814.073µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:55:34Z" - latency: 2.211357ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T15:55:34Z" - latency: 794.2µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:54:34Z" - latency: 1.600831ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T15:54:34Z" - latency: 1.205278ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:53:34Z" - latency: 2.668542ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T15:53:34Z" - latency: 922.63µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:52:34Z" - latency: 1.710317ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T15:52:34Z" - latency: 1.267336ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:51:34Z" - latency: 1.607561ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T15:51:34Z" kind: List metadata: resourceVersion: ""