apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T02:06:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-25-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-25.ec2.internal uid: b9cee60a-6d3e-46bc-928d-d0957b5e7510 resourceVersion: "61565" uid: 919d6b1c-88c8-42be-b1c5-d4199899b09e spec: sourcePod: network-check-source-869dcfcdcd-pb8mx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T02:13:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 908.084µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:48:02Z" - latency: 1.024373ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:47:02Z" - latency: 1.050124ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:46:02Z" - latency: 1.099449ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:45:02Z" - latency: 1.144163ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:44:02Z" - latency: 987.425µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:43:02Z" - latency: 1.785528ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:42:02Z" - latency: 1.029699ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:41:02Z" - latency: 984.762µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:40:02Z" - latency: 1.489852ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:39:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T02:06:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-25-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-25.ec2.internal uid: b9cee60a-6d3e-46bc-928d-d0957b5e7510 resourceVersion: "61566" uid: 026bb13f-d8ad-4756-a688-3632cdfbe419 spec: sourcePod: network-check-source-869dcfcdcd-pb8mx targetEndpoint: a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T02:12:02Z" message: 'load-balancer-api-external: tcp connection to a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.932881ms message: 'load-balancer-api-external: tcp connection to a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:48:02Z" - latency: 6.650282ms message: 'load-balancer-api-external: resolved host name a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T02:48:02Z" - latency: 5.143247ms message: 'load-balancer-api-external: tcp connection to a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:47:02Z" - latency: 6.561713ms message: 'load-balancer-api-external: resolved host name a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T02:47:02Z" - latency: 4.598986ms message: 'load-balancer-api-external: tcp connection to a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:46:02Z" - latency: 6.698141ms message: 'load-balancer-api-external: resolved host name a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T02:46:02Z" - latency: 5.071669ms message: 'load-balancer-api-external: tcp connection to a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:45:02Z" - latency: 6.62588ms message: 'load-balancer-api-external: resolved host name a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T02:45:02Z" - latency: 6.18656ms message: 'load-balancer-api-external: tcp connection to a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:44:02Z" - latency: 5.97773ms message: 'load-balancer-api-external: resolved host name a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T02:44:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T02:06:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-25-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-25.ec2.internal uid: b9cee60a-6d3e-46bc-928d-d0957b5e7510 resourceVersion: "61567" uid: 0fa533e9-b1f5-4c1b-98e9-e803d06b3a59 spec: sourcePod: network-check-source-869dcfcdcd-pb8mx targetEndpoint: a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T02:12:02Z" message: 'load-balancer-api-internal: tcp connection to a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.41814ms message: 'load-balancer-api-internal: tcp connection to a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:48:02Z" - latency: 6.618722ms message: 'load-balancer-api-internal: resolved host name a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T02:48:02Z" - latency: 5.120916ms message: 'load-balancer-api-internal: tcp connection to a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:47:02Z" - latency: 6.642456ms message: 'load-balancer-api-internal: resolved host name a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T02:47:02Z" - latency: 6.316881ms message: 'load-balancer-api-internal: tcp connection to a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:46:02Z" - latency: 6.626727ms message: 'load-balancer-api-internal: resolved host name a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T02:46:02Z" - latency: 5.026915ms message: 'load-balancer-api-internal: tcp connection to a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:45:02Z" - latency: 6.692558ms message: 'load-balancer-api-internal: resolved host name a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T02:45:02Z" - latency: 5.363328ms message: 'load-balancer-api-internal: tcp connection to a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:44:02Z" - latency: 6.016354ms message: 'load-balancer-api-internal: resolved host name a62703364e0b9498f9a2a650a7f06b87-806c38dad9ad1f63.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T02:44:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T02:06:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-25-to-network-check-target-ip-10-0-128-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-25.ec2.internal uid: b9cee60a-6d3e-46bc-928d-d0957b5e7510 resourceVersion: "61562" uid: 2f6bdabb-5008-44aa-8a68-0b878fec1d98 spec: sourcePod: network-check-source-869dcfcdcd-pb8mx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T02:13:02Z" message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.059887ms message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:48:02Z" - latency: 2.336796ms message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:47:02Z" - latency: 2.023372ms message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:46:02Z" - latency: 2.49869ms message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:45:02Z" - latency: 2.300786ms message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:44:02Z" - latency: 2.265887ms message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:43:02Z" - latency: 2.715316ms message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:42:02Z" - latency: 2.204961ms message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:41:02Z" - latency: 2.646196ms message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:40:02Z" - latency: 2.159925ms message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:39:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T02:06:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-25-to-network-check-target-ip-10-0-129-135 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-25.ec2.internal uid: b9cee60a-6d3e-46bc-928d-d0957b5e7510 resourceVersion: "61563" uid: 91fa8dc6-83c0-4461-8d46-b7460d65a60b spec: sourcePod: network-check-source-869dcfcdcd-pb8mx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T02:13:02Z" message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.488938ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:48:02Z" - latency: 2.395778ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:47:02Z" - latency: 2.777967ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:46:02Z" - latency: 2.550273ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:45:02Z" - latency: 2.640955ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:44:02Z" - latency: 2.194589ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:43:02Z" - latency: 2.283334ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:42:02Z" - latency: 2.231482ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:41:02Z" - latency: 2.137816ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:40:02Z" - latency: 2.30902ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:39:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T02:06:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-25-to-network-check-target-ip-10-0-131-25 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-25.ec2.internal uid: b9cee60a-6d3e-46bc-928d-d0957b5e7510 resourceVersion: "61561" uid: b5220b50-5c86-43e0-aad8-aca41da21b7d spec: sourcePod: network-check-source-869dcfcdcd-pb8mx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T02:13:02Z" message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.032754ms message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:48:02Z" - latency: 935.488µs message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:47:02Z" - latency: 1.013591ms message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:46:02Z" - latency: 890.079µs message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:45:02Z" - latency: 987.033µs message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:44:02Z" - latency: 1.324999ms message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:43:02Z" - latency: 2.145414ms message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:42:02Z" - latency: 1.238876ms message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:41:02Z" - latency: 1.394183ms message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:40:02Z" - latency: 812.562µs message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:39:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T02:06:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-25-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-25.ec2.internal uid: b9cee60a-6d3e-46bc-928d-d0957b5e7510 resourceVersion: "61564" uid: 4d421465-f011-4477-8886-e5317da776b6 spec: sourcePod: network-check-source-869dcfcdcd-pb8mx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T02:12:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.164049ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:48:02Z" - latency: 1.733032ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T02:48:02Z" - latency: 892.53µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:47:02Z" - latency: 1.780676ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T02:47:02Z" - latency: 868.406µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:46:02Z" - latency: 1.784434ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T02:46:02Z" - latency: 917.111µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:45:02Z" - latency: 1.602197ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T02:45:02Z" - latency: 774.287µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T02:44:02Z" - latency: 1.65713ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T02:44:02Z" kind: List metadata: resourceVersion: ""