apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:14:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-113-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-113.ec2.internal uid: c9a44315-c28e-4413-964b-71d6105eb5d8 resourceVersion: "56943" uid: 6ccbf5a3-ca11-4dfd-9ccf-4bd5d3bc8ffe spec: sourcePod: network-check-source-869dcfcdcd-chhhx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T21:21:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.606626ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:49:04Z" - latency: 1.010884ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:04Z" - latency: 984.135µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:04Z" - latency: 982.321µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:04Z" - latency: 908.02µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:04Z" - latency: 887.486µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:04Z" - latency: 940.002µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:04Z" - latency: 804.677µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:04Z" - latency: 906.054µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:04Z" - latency: 1.140567ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:14:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-113-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-113.ec2.internal uid: c9a44315-c28e-4413-964b-71d6105eb5d8 resourceVersion: "51884" uid: 583d7e6a-31ad-4df5-a58a-c9f220b5700e spec: sourcePod: network-check-source-869dcfcdcd-chhhx targetEndpoint: a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T21:20:04Z" message: 'load-balancer-api-external: tcp connection to a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.407346ms message: 'load-balancer-api-external: tcp connection to a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:04Z" - latency: 6.801618ms message: 'load-balancer-api-external: resolved host name a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:44:04Z" - latency: 5.836689ms message: 'load-balancer-api-external: tcp connection to a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:04Z" - latency: 7.115865ms message: 'load-balancer-api-external: resolved host name a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:43:04Z" - latency: 3.571639ms message: 'load-balancer-api-external: tcp connection to a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:04Z" - latency: 7.721947ms message: 'load-balancer-api-external: resolved host name a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:42:04Z" - latency: 6.328588ms message: 'load-balancer-api-external: tcp connection to a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:04Z" - latency: 7.668053ms message: 'load-balancer-api-external: resolved host name a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:41:04Z" - latency: 4.993669ms message: 'load-balancer-api-external: tcp connection to a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:04Z" - latency: 10.899621ms message: 'load-balancer-api-external: resolved host name a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:40:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:14:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-113-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-113.ec2.internal uid: c9a44315-c28e-4413-964b-71d6105eb5d8 resourceVersion: "51885" uid: accdd104-923e-4581-b153-10f5e1a44da1 spec: sourcePod: network-check-source-869dcfcdcd-chhhx targetEndpoint: a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T21:20:04Z" message: 'load-balancer-api-internal: tcp connection to a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.021891ms message: 'load-balancer-api-internal: tcp connection to a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:04Z" - latency: 6.83391ms message: 'load-balancer-api-internal: resolved host name a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:44:04Z" - latency: 5.927852ms message: 'load-balancer-api-internal: tcp connection to a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:04Z" - latency: 7.055008ms message: 'load-balancer-api-internal: resolved host name a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:43:04Z" - latency: 5.511889ms message: 'load-balancer-api-internal: tcp connection to a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:04Z" - latency: 7.79882ms message: 'load-balancer-api-internal: resolved host name a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:42:04Z" - latency: 5.733238ms message: 'load-balancer-api-internal: tcp connection to a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:04Z" - latency: 7.711483ms message: 'load-balancer-api-internal: resolved host name a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:41:04Z" - latency: 5.783336ms message: 'load-balancer-api-internal: tcp connection to a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:04Z" - latency: 10.874797ms message: 'load-balancer-api-internal: resolved host name a1d87dc9d67704d52a2077ed9e14b9be-e0a1f30c8186735e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:40:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:14:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-113-to-network-check-target-ip-10-0-131-113 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-113.ec2.internal uid: c9a44315-c28e-4413-964b-71d6105eb5d8 resourceVersion: "56941" uid: d207fe7a-afbb-4417-ab3c-d93dd05486ea spec: sourcePod: network-check-source-869dcfcdcd-chhhx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:21:04Z" message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.074824ms message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:49:04Z" - latency: 1.055066ms message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:04Z" - latency: 895.721µs message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:04Z" - latency: 1.037806ms message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:04Z" - latency: 818.093µs message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:04Z" - latency: 946.022µs message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:04Z" - latency: 887.682µs message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:04Z" - latency: 1.130075ms message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:04Z" - latency: 969.245µs message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:04Z" - latency: 924.5µs message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:14:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-113-to-network-check-target-ip-10-0-136-220 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-113.ec2.internal uid: c9a44315-c28e-4413-964b-71d6105eb5d8 resourceVersion: "56940" uid: 10240687-8868-4753-9d41-9b83de887083 spec: sourcePod: network-check-source-869dcfcdcd-chhhx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:21:04Z" message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.913024ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:49:04Z" - latency: 2.250368ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:04Z" - latency: 1.909458ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:04Z" - latency: 2.232989ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:04Z" - latency: 1.912787ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:04Z" - latency: 1.723265ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:04Z" - latency: 1.923089ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:04Z" - latency: 1.999217ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:04Z" - latency: 1.981818ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:04Z" - latency: 2.438563ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:14:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-113-to-network-check-target-ip-10-0-143-128 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-113.ec2.internal uid: c9a44315-c28e-4413-964b-71d6105eb5d8 resourceVersion: "56942" uid: 43019e0a-8e3d-4d32-91bd-9bebb4124355 spec: sourcePod: network-check-source-869dcfcdcd-chhhx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T21:21:04Z" message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.225304ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:49:04Z" - latency: 2.20727ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:48:04Z" - latency: 1.996ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:47:04Z" - latency: 2.24449ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:46:04Z" - latency: 1.874785ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:45:04Z" - latency: 1.983906ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:04Z" - latency: 2.004851ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:04Z" - latency: 2.070819ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:04Z" - latency: 2.057655ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:04Z" - latency: 2.096895ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T21:14:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-113-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-113.ec2.internal uid: c9a44315-c28e-4413-964b-71d6105eb5d8 resourceVersion: "51883" uid: c18e4364-9851-4689-af7c-5669a4f0ce1b spec: sourcePod: network-check-source-869dcfcdcd-chhhx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T21:20:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.090723ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:44:04Z" - latency: 1.925837ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:44:04Z" - latency: 1.04129ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:43:04Z" - latency: 1.939013ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:43:04Z" - latency: 1.070364ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:42:04Z" - latency: 2.134412ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:42:04Z" - latency: 1.098168ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:41:04Z" - latency: 1.868713ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:41:04Z" - latency: 1.024185ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:40:04Z" - latency: 2.270842ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:40:04Z" kind: List metadata: resourceVersion: ""