apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T19:59:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-175-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-175.us-east-2.compute.internal uid: e7f89c7c-8ccd-42f4-8bbf-dd87d9cbdef7 resourceVersion: "160289" uid: 5107fc45-cca4-4acd-915c-3e98b7ddd7d3 spec: sourcePod: network-check-source-6f78d59f99-djwlz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-01T20:06:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.529641ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:55:42Z" - latency: 1.255739ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:54:42Z" - latency: 1.496166ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:53:42Z" - latency: 1.439935ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:52:42Z" - latency: 1.06123ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:51:42Z" - latency: 992.108µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:50:42Z" - latency: 1.460626ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:49:42Z" - latency: 1.157317ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:48:42Z" - latency: 1.318455ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:47:42Z" - latency: 1.932763ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:46:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T19:59:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-175-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-175.us-east-2.compute.internal uid: e7f89c7c-8ccd-42f4-8bbf-dd87d9cbdef7 resourceVersion: "166734" uid: 2987fa24-5aaa-43b5-803d-93ce9b35b650 spec: sourcePod: network-check-source-6f78d59f99-djwlz targetEndpoint: a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T20:05:42Z" message: 'load-balancer-api-external: tcp connection to a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.826032ms message: 'load-balancer-api-external: tcp connection to a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:59:42Z" - latency: 7.824746ms message: 'load-balancer-api-external: resolved host name a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T20:59:42Z" - latency: 6.847526ms message: 'load-balancer-api-external: tcp connection to a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:58:42Z" - latency: 7.326544ms message: 'load-balancer-api-external: resolved host name a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T20:58:42Z" - latency: 5.773628ms message: 'load-balancer-api-external: tcp connection to a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:57:42Z" - latency: 6.890301ms message: 'load-balancer-api-external: resolved host name a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T20:57:42Z" - latency: 6.638938ms message: 'load-balancer-api-external: tcp connection to a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:56:42Z" - latency: 7.168704ms message: 'load-balancer-api-external: resolved host name a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T20:56:42Z" - latency: 5.026457ms message: 'load-balancer-api-external: tcp connection to a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:55:42Z" - latency: 6.960873ms message: 'load-balancer-api-external: resolved host name a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T20:55:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T19:59:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-175-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-175.us-east-2.compute.internal uid: e7f89c7c-8ccd-42f4-8bbf-dd87d9cbdef7 resourceVersion: "166735" uid: 2b2efb59-2b75-4676-8e10-be6b16daafb3 spec: sourcePod: network-check-source-6f78d59f99-djwlz targetEndpoint: a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T20:05:42Z" message: 'load-balancer-api-internal: tcp connection to a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.832576ms message: 'load-balancer-api-internal: tcp connection to a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:59:42Z" - latency: 7.778492ms message: 'load-balancer-api-internal: resolved host name a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T20:59:42Z" - latency: 9.399746ms message: 'load-balancer-api-internal: tcp connection to a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:58:42Z" - latency: 7.12189ms message: 'load-balancer-api-internal: resolved host name a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T20:58:42Z" - latency: 5.827237ms message: 'load-balancer-api-internal: tcp connection to a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:57:42Z" - latency: 6.872748ms message: 'load-balancer-api-internal: resolved host name a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T20:57:42Z" - latency: 6.685019ms message: 'load-balancer-api-internal: tcp connection to a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:56:42Z" - latency: 7.134393ms message: 'load-balancer-api-internal: resolved host name a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T20:56:42Z" - latency: 5.026876ms message: 'load-balancer-api-internal: tcp connection to a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:55:42Z" - latency: 6.910643ms message: 'load-balancer-api-internal: resolved host name a4cb920232ed848f7b7a0c837bccb1a9-33950dcfe04ae3e2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T20:55:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T19:59:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-175-to-network-check-target-ip-10-0-133-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-175.us-east-2.compute.internal uid: e7f89c7c-8ccd-42f4-8bbf-dd87d9cbdef7 resourceVersion: "160344" uid: b325a131-3635-4e3f-b7b6-b3786ea4bde0 spec: sourcePod: network-check-source-6f78d59f99-djwlz targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T20:06:48Z" message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.702346ms message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:55:48Z" - latency: 982.776µs message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:54:48Z" - latency: 1.222571ms message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:53:48Z" - latency: 2.280465ms message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:52:48Z" - latency: 2.68218ms message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:51:48Z" - latency: 2.114964ms message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:50:48Z" - latency: 2.723293ms message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:49:48Z" - latency: 671.21µs message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:48:48Z" - latency: 3.072975ms message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:47:48Z" - latency: 2.173355ms message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:46:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T19:59:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-175-to-network-check-target-ip-10-0-136-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-175.us-east-2.compute.internal uid: e7f89c7c-8ccd-42f4-8bbf-dd87d9cbdef7 resourceVersion: "160306" uid: 30a4118a-58ad-4bb2-9f58-2157d8f32124 spec: sourcePod: network-check-source-6f78d59f99-djwlz targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T20:06:43Z" message: 'network-check-target-ip-10-0-136-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.97687ms message: 'network-check-target-ip-10-0-136-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:55:43Z" - latency: 2.315155ms message: 'network-check-target-ip-10-0-136-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:54:43Z" - latency: 2.295428ms message: 'network-check-target-ip-10-0-136-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:53:43Z" - latency: 924.262µs message: 'network-check-target-ip-10-0-136-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:52:43Z" - latency: 1.531115ms message: 'network-check-target-ip-10-0-136-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:51:43Z" - latency: 1.154397ms message: 'network-check-target-ip-10-0-136-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:50:43Z" - latency: 964.87µs message: 'network-check-target-ip-10-0-136-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:49:43Z" - latency: 2.73592ms message: 'network-check-target-ip-10-0-136-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:48:43Z" - latency: 2.506254ms message: 'network-check-target-ip-10-0-136-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:47:43Z" - latency: 857.574µs message: 'network-check-target-ip-10-0-136-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:46:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T19:59:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-175-to-network-check-target-ip-10-0-137-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-175.us-east-2.compute.internal uid: e7f89c7c-8ccd-42f4-8bbf-dd87d9cbdef7 resourceVersion: "160288" uid: d0e53649-d646-4013-9ce7-323ff6d61590 spec: sourcePod: network-check-source-6f78d59f99-djwlz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T20:06:42Z" message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.482482ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:55:42Z" - latency: 1.079691ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:54:42Z" - latency: 1.445244ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:53:42Z" - latency: 1.635505ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:52:42Z" - latency: 1.532406ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:51:42Z" - latency: 1.387936ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:50:42Z" - latency: 1.593525ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:49:42Z" - latency: 1.489392ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:48:42Z" - latency: 1.298402ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:47:42Z" - latency: 1.909992ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:46:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T19:59:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-175-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-175.us-east-2.compute.internal uid: e7f89c7c-8ccd-42f4-8bbf-dd87d9cbdef7 resourceVersion: "166733" uid: 520deacc-daba-40a5-9b1d-7fb9c92b0526 spec: sourcePod: network-check-source-6f78d59f99-djwlz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-01T20:05:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.105796ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:59:42Z" - latency: 1.898433ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T20:59:42Z" - latency: 969.098µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:58:42Z" - latency: 1.947543ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T20:58:42Z" - latency: 850.136µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:57:42Z" - latency: 1.713953ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T20:57:42Z" - latency: 922.722µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:56:42Z" - latency: 1.992163ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T20:56:42Z" - latency: 900.09µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T20:55:42Z" - latency: 2.024156ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T20:55:42Z" kind: List metadata: resourceVersion: ""