apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T16:03:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-129-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-129.us-east-2.compute.internal uid: 67142690-39bb-4815-a7c5-1cd656d61913 resourceVersion: "66001" uid: aef1af85-4d69-4ae5-93d2-c41c09378b61 spec: sourcePod: network-check-source-6f78d59f99-mhc9q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T16:10:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.152629ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:38:40Z" - latency: 1.551678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:37:40Z" - latency: 1.296777ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:36:40Z" - latency: 1.004455ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:35:40Z" - latency: 1.34724ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:34:40Z" - latency: 1.343848ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:33:40Z" - latency: 1.469502ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:32:40Z" - latency: 1.387141ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:31:40Z" - latency: 1.366848ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:30:40Z" - latency: 1.139628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:29:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T16:03:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-129-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-129.us-east-2.compute.internal uid: 67142690-39bb-4815-a7c5-1cd656d61913 resourceVersion: "66896" uid: 12a54e1c-d342-4e42-be23-76e1ca9e3b73 spec: sourcePod: network-check-source-6f78d59f99-mhc9q targetEndpoint: a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T16:09:40Z" message: 'load-balancer-api-external: tcp connection to a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.126963ms message: 'load-balancer-api-external: tcp connection to a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:39:40Z" - latency: 6.882768ms message: 'load-balancer-api-external: resolved host name a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T16:39:40Z" - latency: 9.059961ms message: 'load-balancer-api-external: tcp connection to a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:38:40Z" - latency: 10.104132ms message: 'load-balancer-api-external: resolved host name a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T16:38:40Z" - latency: 5.535344ms message: 'load-balancer-api-external: tcp connection to a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:37:40Z" - latency: 7.128043ms message: 'load-balancer-api-external: resolved host name a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T16:37:40Z" - latency: 6.601734ms message: 'load-balancer-api-external: tcp connection to a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:36:40Z" - latency: 6.545392ms message: 'load-balancer-api-external: resolved host name a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T16:36:40Z" - latency: 5.58015ms message: 'load-balancer-api-external: tcp connection to a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:35:40Z" - latency: 6.858913ms message: 'load-balancer-api-external: resolved host name a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T16:35:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T16:03:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-129-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-129.us-east-2.compute.internal uid: 67142690-39bb-4815-a7c5-1cd656d61913 resourceVersion: "66897" uid: d3985ffa-9d93-45c2-aefc-882d54228461 spec: sourcePod: network-check-source-6f78d59f99-mhc9q targetEndpoint: a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T16:09:40Z" message: 'load-balancer-api-internal: tcp connection to a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.154377ms message: 'load-balancer-api-internal: tcp connection to a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:39:40Z" - latency: 6.857423ms message: 'load-balancer-api-internal: resolved host name a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T16:39:40Z" - latency: 5.892046ms message: 'load-balancer-api-internal: tcp connection to a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:38:40Z" - latency: 9.848041ms message: 'load-balancer-api-internal: resolved host name a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T16:38:40Z" - latency: 5.60593ms message: 'load-balancer-api-internal: tcp connection to a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:37:40Z" - latency: 7.0793ms message: 'load-balancer-api-internal: resolved host name a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T16:37:40Z" - latency: 6.988988ms message: 'load-balancer-api-internal: tcp connection to a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:36:40Z" - latency: 6.487575ms message: 'load-balancer-api-internal: resolved host name a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T16:36:40Z" - latency: 5.51433ms message: 'load-balancer-api-internal: tcp connection to a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:35:40Z" - latency: 6.805344ms message: 'load-balancer-api-internal: resolved host name a2b47bef83ad349e58d036eef7d06611-d779ba969dfa1f9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T16:35:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T16:03:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-129-to-network-check-target-ip-10-0-129-122 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-129.us-east-2.compute.internal uid: 67142690-39bb-4815-a7c5-1cd656d61913 resourceVersion: "66204" uid: 227f05c9-3ec9-490c-82ad-dd5e30cb798f spec: sourcePod: network-check-source-6f78d59f99-mhc9q targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T16:10:53Z" message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.367693ms message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:38:53Z" - latency: 2.145314ms message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:37:53Z" - latency: 2.008684ms message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:36:53Z" - latency: 2.685801ms message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:35:53Z" - latency: 2.339181ms message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:34:53Z" - latency: 1.992ms message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:33:53Z" - latency: 2.700271ms message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:32:53Z" - latency: 2.578227ms message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:31:53Z" - latency: 2.586292ms message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:30:53Z" - latency: 2.541202ms message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:29:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T16:03:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-129-to-network-check-target-ip-10-0-133-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-129.us-east-2.compute.internal uid: 67142690-39bb-4815-a7c5-1cd656d61913 resourceVersion: "65999" uid: 543c47b2-78c6-4ff2-b562-d20c3a9e3523 spec: sourcePod: network-check-source-6f78d59f99-mhc9q targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T16:10:40Z" message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.561948ms message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:38:40Z" - latency: 976.147µs message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:37:40Z" - latency: 1.369972ms message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:36:40Z" - latency: 1.336791ms message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:35:40Z" - latency: 899.383µs message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:34:40Z" - latency: 1.529841ms message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:33:40Z" - latency: 1.404079ms message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:32:40Z" - latency: 1.254316ms message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:31:40Z" - latency: 1.580098ms message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:30:40Z" - latency: 1.426052ms message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:29:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T16:03:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-129-to-network-check-target-ip-10-0-137-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-129.us-east-2.compute.internal uid: 67142690-39bb-4815-a7c5-1cd656d61913 resourceVersion: "66021" uid: 65360ebf-baf8-468d-a68a-ab1547a16e8a spec: sourcePod: network-check-source-6f78d59f99-mhc9q targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T16:10:41Z" message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.64267ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:38:41Z" - latency: 804.468µs message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:37:41Z" - latency: 1.070726ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:36:41Z" - latency: 2.126824ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:35:41Z" - latency: 1.897717ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:34:41Z" - latency: 1.82861ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:33:41Z" - latency: 2.093513ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:32:41Z" - latency: 2.065246ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:31:41Z" - latency: 2.447423ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:30:41Z" - latency: 2.234998ms message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:29:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T16:03:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-129-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-129.us-east-2.compute.internal uid: 67142690-39bb-4815-a7c5-1cd656d61913 resourceVersion: "66893" uid: 4df570d7-faed-4fff-88d6-4052d806e521 spec: sourcePod: network-check-source-6f78d59f99-mhc9q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T16:09:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 864.421µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:39:40Z" - latency: 1.953341ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T16:39:40Z" - latency: 1.212668ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:38:40Z" - latency: 4.172971ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T16:38:40Z" - latency: 2.053317ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:37:40Z" - latency: 2.263131ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T16:37:40Z" - latency: 1.612978ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:36:40Z" - latency: 1.820791ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T16:36:40Z" - latency: 744.273µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T16:35:40Z" - latency: 1.958942ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T16:35:40Z" kind: List metadata: resourceVersion: ""