apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T15:28:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-61-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-61.ec2.internal uid: 7be4532a-0b14-4c9b-8ff6-e260422aad74 resourceVersion: "60760" uid: 47ccdf11-49be-4477-b16c-2ec8fea6793b spec: sourcePod: network-check-source-869dcfcdcd-l64mk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T15:35:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.309006ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:10:43Z" - latency: 877.476µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:09:43Z" - latency: 1.323203ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:08:43Z" - latency: 966.106µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:07:43Z" - latency: 958.888µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:06:43Z" - latency: 874.441µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:05:43Z" - latency: 1.446311ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:04:43Z" - latency: 824.293µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:03:43Z" - latency: 859.39µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:02:43Z" - latency: 855.805µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:01:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T15:28:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-61-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-61.ec2.internal uid: 7be4532a-0b14-4c9b-8ff6-e260422aad74 resourceVersion: "60762" uid: d984bb76-1db0-4a90-b098-2b0fbe79debd spec: sourcePod: network-check-source-869dcfcdcd-l64mk targetEndpoint: a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T15:34:43Z" message: 'load-balancer-api-external: tcp connection to a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.424748ms message: 'load-balancer-api-external: tcp connection to a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:10:43Z" - latency: 6.847831ms message: 'load-balancer-api-external: resolved host name a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:10:43Z" - latency: 4.249338ms message: 'load-balancer-api-external: tcp connection to a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:09:43Z" - latency: 7.646151ms message: 'load-balancer-api-external: resolved host name a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:09:43Z" - latency: 5.245521ms message: 'load-balancer-api-external: tcp connection to a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:08:43Z" - latency: 6.468797ms message: 'load-balancer-api-external: resolved host name a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:08:43Z" - latency: 3.63552ms message: 'load-balancer-api-external: tcp connection to a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:07:43Z" - latency: 6.941954ms message: 'load-balancer-api-external: resolved host name a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:07:43Z" - latency: 3.415548ms message: 'load-balancer-api-external: tcp connection to a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:06:43Z" - latency: 6.952445ms message: 'load-balancer-api-external: resolved host name a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:06:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T15:28:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-61-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-61.ec2.internal uid: 7be4532a-0b14-4c9b-8ff6-e260422aad74 resourceVersion: "60761" uid: 381a2de7-04e1-49ce-ab9a-9092a9acb57c spec: sourcePod: network-check-source-869dcfcdcd-l64mk targetEndpoint: a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T15:34:43Z" message: 'load-balancer-api-internal: tcp connection to a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.389074ms message: 'load-balancer-api-internal: tcp connection to a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:10:43Z" - latency: 6.897096ms message: 'load-balancer-api-internal: resolved host name a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:10:43Z" - latency: 4.23819ms message: 'load-balancer-api-internal: tcp connection to a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:09:43Z" - latency: 7.698036ms message: 'load-balancer-api-internal: resolved host name a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:09:43Z" - latency: 5.220092ms message: 'load-balancer-api-internal: tcp connection to a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:08:43Z" - latency: 6.529605ms message: 'load-balancer-api-internal: resolved host name a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:08:43Z" - latency: 4.730875ms message: 'load-balancer-api-internal: tcp connection to a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:07:43Z" - latency: 6.996639ms message: 'load-balancer-api-internal: resolved host name a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:07:43Z" - latency: 3.533714ms message: 'load-balancer-api-internal: tcp connection to a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:06:43Z" - latency: 6.933212ms message: 'load-balancer-api-internal: resolved host name a2681e6f0cbaf4f8194427698225ca07-d90f17071759289a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:06:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T15:28:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-135-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-61.ec2.internal uid: 7be4532a-0b14-4c9b-8ff6-e260422aad74 resourceVersion: "60758" uid: dd33b704-41dc-4dfa-9a0e-679541411110 spec: sourcePod: network-check-source-869dcfcdcd-l64mk targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T15:35:43Z" message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.929772ms message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:10:43Z" - latency: 2.755058ms message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:09:43Z" - latency: 2.435735ms message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:08:43Z" - latency: 2.422885ms message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:07:43Z" - latency: 2.151144ms message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:06:43Z" - latency: 1.900405ms message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:05:43Z" - latency: 2.347791ms message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:04:43Z" - latency: 2.275382ms message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:03:43Z" - latency: 2.097582ms message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:02:43Z" - latency: 2.48519ms message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:01:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T15:28:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-138-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-61.ec2.internal uid: 7be4532a-0b14-4c9b-8ff6-e260422aad74 resourceVersion: "60757" uid: e5806796-91a4-4444-9e44-65941827d1ca spec: sourcePod: network-check-source-869dcfcdcd-l64mk targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T15:35:43Z" message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.999695ms message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:10:43Z" - latency: 2.392118ms message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:09:43Z" - latency: 2.441029ms message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:08:43Z" - latency: 2.327017ms message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:07:43Z" - latency: 2.322484ms message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:06:43Z" - latency: 2.121736ms message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:05:43Z" - latency: 2.245219ms message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:04:43Z" - latency: 2.262385ms message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:03:43Z" - latency: 2.045324ms message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:02:43Z" - latency: 2.12097ms message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:01:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T15:28:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-140-61 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-61.ec2.internal uid: 7be4532a-0b14-4c9b-8ff6-e260422aad74 resourceVersion: "60756" uid: 12b87beb-dbd2-4a5f-b8bc-3d5d06b67047 spec: sourcePod: network-check-source-869dcfcdcd-l64mk targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T15:35:43Z" message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 903.123µs message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:10:43Z" - latency: 750.628µs message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:09:43Z" - latency: 707.498µs message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:08:43Z" - latency: 899.091µs message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:07:43Z" - latency: 917.267µs message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:06:43Z" - latency: 841.312µs message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:05:43Z" - latency: 1.240232ms message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:04:43Z" - latency: 849.04µs message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:03:43Z" - latency: 818.449µs message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:02:43Z" - latency: 945.639µs message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:01:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T15:28:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-61-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-61.ec2.internal uid: 7be4532a-0b14-4c9b-8ff6-e260422aad74 resourceVersion: "60759" uid: b08e3eec-73ca-44c3-9c51-29011f895c33 spec: sourcePod: network-check-source-869dcfcdcd-l64mk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T15:34:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.065179ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:10:43Z" - latency: 1.881181ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:10:43Z" - latency: 967.604µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:09:43Z" - latency: 1.891381ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:09:43Z" - latency: 996.751µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:08:43Z" - latency: 1.730147ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:08:43Z" - latency: 746.419µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:07:43Z" - latency: 1.69636ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:07:43Z" - latency: 792.194µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:06:43Z" - latency: 1.612899ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:06:43Z" kind: List metadata: resourceVersion: ""