apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T13:04:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-198-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-198.ec2.internal uid: 81b60d50-8871-4c08-8613-6293918b93ed resourceVersion: "61593" uid: 76ba4a5e-b7c9-40a3-a665-623f6ef34fce spec: sourcePod: network-check-source-7bc5b6bf85-bfhzl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T13:11:50Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.892921ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:46:50Z" - latency: 1.129152ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:45:50Z" - latency: 1.018184ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:44:50Z" - latency: 1.011836ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:43:50Z" - latency: 895.201µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:42:50Z" - latency: 1.120861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:41:50Z" - latency: 1.458625ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:40:50Z" - latency: 1.082818ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:39:50Z" - latency: 928.77µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:38:50Z" - latency: 851.154µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:37:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T13:04:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-198-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-198.ec2.internal uid: 81b60d50-8871-4c08-8613-6293918b93ed resourceVersion: "61595" uid: fdc0f420-6470-4694-9ca7-216eded155e3 spec: sourcePod: network-check-source-7bc5b6bf85-bfhzl targetEndpoint: a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T13:10:50Z" message: 'load-balancer-api-external: tcp connection to a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.356309ms message: 'load-balancer-api-external: tcp connection to a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:46:50Z" - latency: 9.459358ms message: 'load-balancer-api-external: resolved host name a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:46:50Z" - latency: 5.36584ms message: 'load-balancer-api-external: tcp connection to a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:45:50Z" - latency: 9.264121ms message: 'load-balancer-api-external: resolved host name a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:45:50Z" - latency: 3.916379ms message: 'load-balancer-api-external: tcp connection to a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:44:50Z" - latency: 10.103991ms message: 'load-balancer-api-external: resolved host name a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:44:50Z" - latency: 4.010929ms message: 'load-balancer-api-external: tcp connection to a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:43:50Z" - latency: 9.290568ms message: 'load-balancer-api-external: resolved host name a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:43:50Z" - latency: 6.841494ms message: 'load-balancer-api-external: tcp connection to a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:42:50Z" - latency: 10.827555ms message: 'load-balancer-api-external: resolved host name a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:42:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T13:04:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-198-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-198.ec2.internal uid: 81b60d50-8871-4c08-8613-6293918b93ed resourceVersion: "61594" uid: da3930cf-56a2-4f39-8e76-35bc320a1e01 spec: sourcePod: network-check-source-7bc5b6bf85-bfhzl targetEndpoint: a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T13:10:50Z" message: 'load-balancer-api-internal: tcp connection to a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.420662ms message: 'load-balancer-api-internal: tcp connection to a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:46:50Z" - latency: 9.424916ms message: 'load-balancer-api-internal: resolved host name a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:46:50Z" - latency: 4.605666ms message: 'load-balancer-api-internal: tcp connection to a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:45:50Z" - latency: 9.179955ms message: 'load-balancer-api-internal: resolved host name a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:45:50Z" - latency: 4.634011ms message: 'load-balancer-api-internal: tcp connection to a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:44:50Z" - latency: 10.05617ms message: 'load-balancer-api-internal: resolved host name a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:44:50Z" - latency: 4.016673ms message: 'load-balancer-api-internal: tcp connection to a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:43:50Z" - latency: 9.245012ms message: 'load-balancer-api-internal: resolved host name a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:43:50Z" - latency: 6.916922ms message: 'load-balancer-api-internal: tcp connection to a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:42:50Z" - latency: 10.69923ms message: 'load-balancer-api-internal: resolved host name a53d07f54f6bf4054b58988aef99d3ce-b5057a553a335b4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:42:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T13:04:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-198-to-network-check-target-ip-10-0-131-198 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-198.ec2.internal uid: 81b60d50-8871-4c08-8613-6293918b93ed resourceVersion: "61589" uid: ee15afb3-57c9-42c0-a384-8f1a2329a85e spec: sourcePod: network-check-source-7bc5b6bf85-bfhzl targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T13:11:50Z" message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.403901ms message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:46:50Z" - latency: 898.853µs message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:45:50Z" - latency: 899.175µs message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:44:50Z" - latency: 877.858µs message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:43:50Z" - latency: 1.25023ms message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:42:50Z" - latency: 884.622µs message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:41:50Z" - latency: 769.271µs message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:40:50Z" - latency: 842.178µs message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:39:50Z" - latency: 940.524µs message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:38:50Z" - latency: 891.155µs message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:37:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T13:04:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-198-to-network-check-target-ip-10-0-134-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-198.ec2.internal uid: 81b60d50-8871-4c08-8613-6293918b93ed resourceVersion: "61592" uid: 566fc7c7-5c01-4678-90ce-93316c3ba7ea spec: sourcePod: network-check-source-7bc5b6bf85-bfhzl targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-20T13:11:50Z" message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.381909ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:46:50Z" - latency: 2.239262ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:45:50Z" - latency: 3.031566ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:44:50Z" - latency: 2.808783ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:43:50Z" - latency: 2.61363ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:42:50Z" - latency: 2.83243ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:41:50Z" - latency: 2.416183ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:40:50Z" - latency: 2.505666ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:39:50Z" - latency: 2.462377ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:38:50Z" - latency: 2.346223ms message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:37:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T13:04:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-198-to-network-check-target-ip-10-0-141-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-198.ec2.internal uid: 81b60d50-8871-4c08-8613-6293918b93ed resourceVersion: "61590" uid: 6b4037b2-a7ed-4d1b-a57b-147306f38817 spec: sourcePod: network-check-source-7bc5b6bf85-bfhzl targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T13:11:50Z" message: 'network-check-target-ip-10-0-141-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.994758ms message: 'network-check-target-ip-10-0-141-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:46:50Z" - latency: 2.090115ms message: 'network-check-target-ip-10-0-141-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:45:50Z" - latency: 2.304242ms message: 'network-check-target-ip-10-0-141-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:44:50Z" - latency: 2.209809ms message: 'network-check-target-ip-10-0-141-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:43:50Z" - latency: 2.335666ms message: 'network-check-target-ip-10-0-141-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:42:50Z" - latency: 2.197262ms message: 'network-check-target-ip-10-0-141-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:41:50Z" - latency: 2.146476ms message: 'network-check-target-ip-10-0-141-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:40:50Z" - latency: 2.192753ms message: 'network-check-target-ip-10-0-141-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:39:50Z" - latency: 2.14126ms message: 'network-check-target-ip-10-0-141-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:38:50Z" - latency: 2.069168ms message: 'network-check-target-ip-10-0-141-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:37:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T13:04:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-198-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-198.ec2.internal uid: 81b60d50-8871-4c08-8613-6293918b93ed resourceVersion: "61591" uid: 11eb7163-3bba-4e82-953f-50424c5990f0 spec: sourcePod: network-check-source-7bc5b6bf85-bfhzl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T13:10:50Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 868.907µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:46:50Z" - latency: 1.820172ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T13:46:50Z" - latency: 819.067µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:45:50Z" - latency: 1.783228ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T13:45:50Z" - latency: 1.050914ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:44:50Z" - latency: 1.804555ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T13:44:50Z" - latency: 1.126675ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:43:50Z" - latency: 1.977583ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T13:43:50Z" - latency: 1.487043ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:42:50Z" - latency: 2.340448ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T13:42:50Z" kind: List metadata: resourceVersion: ""