apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T21:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-134-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-134.ec2.internal uid: ea4e2b70-fd8d-4e22-8a5e-ec9c7ec979b3 resourceVersion: "22870" uid: a8e9009c-d80a-49e8-8d2c-339d3f83859d spec: sourcePod: network-check-source-989f8b8dc-bvq64 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T21:26:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 957.235µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:40:59Z" - latency: 943.574µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:39:59Z" - latency: 958.574µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:38:59Z" - latency: 1.019898ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:37:59Z" - latency: 959.058µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:36:59Z" - latency: 995.854µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:35:59Z" - latency: 1.045855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:34:59Z" - latency: 1.353972ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:33:59Z" - latency: 1.276626ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:32:59Z" - latency: 875.424µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:31:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T21:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-134-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-134.ec2.internal uid: ea4e2b70-fd8d-4e22-8a5e-ec9c7ec979b3 resourceVersion: "21536" uid: 783be673-1d81-4afc-a9af-d69935532b88 spec: sourcePod: network-check-source-989f8b8dc-bvq64 targetEndpoint: ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T21:25:59Z" message: 'load-balancer-api-external: tcp connection to ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.012641ms message: 'load-balancer-api-external: tcp connection to ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:37:59Z" - latency: 7.121571ms message: 'load-balancer-api-external: resolved host name ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:37:59Z" - latency: 5.898051ms message: 'load-balancer-api-external: tcp connection to ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:36:59Z" - latency: 10.897134ms message: 'load-balancer-api-external: resolved host name ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:36:59Z" - latency: 6.238871ms message: 'load-balancer-api-external: tcp connection to ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:35:59Z" - latency: 8.836571ms message: 'load-balancer-api-external: resolved host name ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:35:59Z" - latency: 5.77877ms message: 'load-balancer-api-external: tcp connection to ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:34:59Z" - latency: 11.062944ms message: 'load-balancer-api-external: resolved host name ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:34:59Z" - latency: 5.489243ms message: 'load-balancer-api-external: tcp connection to ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:33:59Z" - latency: 7.982034ms message: 'load-balancer-api-external: resolved host name ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:33:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T21:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-134-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-134.ec2.internal uid: ea4e2b70-fd8d-4e22-8a5e-ec9c7ec979b3 resourceVersion: "21537" uid: ec3f51ca-0ada-40ff-9f63-7354058744c8 spec: sourcePod: network-check-source-989f8b8dc-bvq64 targetEndpoint: ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T21:25:59Z" message: 'load-balancer-api-internal: tcp connection to ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.528331ms message: 'load-balancer-api-internal: tcp connection to ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:37:59Z" - latency: 7.184334ms message: 'load-balancer-api-internal: resolved host name ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:37:59Z" - latency: 6.664409ms message: 'load-balancer-api-internal: tcp connection to ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:36:59Z" - latency: 11.019847ms message: 'load-balancer-api-internal: resolved host name ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:36:59Z" - latency: 6.250236ms message: 'load-balancer-api-internal: tcp connection to ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:35:59Z" - latency: 8.808939ms message: 'load-balancer-api-internal: resolved host name ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:35:59Z" - latency: 5.761433ms message: 'load-balancer-api-internal: tcp connection to ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:34:59Z" - latency: 11.138632ms message: 'load-balancer-api-internal: resolved host name ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:34:59Z" - latency: 5.528366ms message: 'load-balancer-api-internal: tcp connection to ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:33:59Z" - latency: 8.221224ms message: 'load-balancer-api-internal: resolved host name ae3553bf79be94ec7b5a653ade06a408-b548ed185de8f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:33:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T21:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-134-to-network-check-target-ip-10-0-130-89 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-134.ec2.internal uid: ea4e2b70-fd8d-4e22-8a5e-ec9c7ec979b3 resourceVersion: "22868" uid: 11738734-82e0-4b35-b6d1-f23955f6fc12 spec: sourcePod: network-check-source-989f8b8dc-bvq64 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T21:26:59Z" message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.369423ms message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:40:59Z" - latency: 2.572548ms message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:39:59Z" - latency: 2.352316ms message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:38:59Z" - latency: 2.492989ms message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:37:59Z" - latency: 2.415567ms message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:36:59Z" - latency: 2.337824ms message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:35:59Z" - latency: 2.427807ms message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:34:59Z" - latency: 1.996735ms message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:33:59Z" - latency: 2.311878ms message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:32:59Z" - latency: 2.733362ms message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:31:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T21:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-134-to-network-check-target-ip-10-0-132-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-134.ec2.internal uid: ea4e2b70-fd8d-4e22-8a5e-ec9c7ec979b3 resourceVersion: "22867" uid: cae48029-2b9b-4829-9a2c-d5c1a2e4d1de spec: sourcePod: network-check-source-989f8b8dc-bvq64 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T21:26:59Z" message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 885.404µs message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:40:59Z" - latency: 1.015625ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:39:59Z" - latency: 1.273953ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:38:59Z" - latency: 1.013659ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:37:59Z" - latency: 1.070214ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:36:59Z" - latency: 988.165µs message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:35:59Z" - latency: 823.278µs message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:34:59Z" - latency: 1.14726ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:33:59Z" - latency: 919.574µs message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:32:59Z" - latency: 814.144µs message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:31:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T21:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-134-to-network-check-target-ip-10-0-137-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-134.ec2.internal uid: ea4e2b70-fd8d-4e22-8a5e-ec9c7ec979b3 resourceVersion: "22869" uid: 0e9d17a9-55fd-442b-9aab-29d3288b58a9 spec: sourcePod: network-check-source-989f8b8dc-bvq64 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T21:26:59Z" message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.333052ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:40:59Z" - latency: 2.287579ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:39:59Z" - latency: 2.186772ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:38:59Z" - latency: 2.248013ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:37:59Z" - latency: 2.072239ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:36:59Z" - latency: 2.236442ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:35:59Z" - latency: 2.52201ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:34:59Z" - latency: 2.585569ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:33:59Z" - latency: 2.517764ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:32:59Z" - latency: 2.844618ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:31:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T21:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-134-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-134.ec2.internal uid: ea4e2b70-fd8d-4e22-8a5e-ec9c7ec979b3 resourceVersion: "21535" uid: 45b7fc8f-843d-4d33-9814-8e44ee0eed4a spec: sourcePod: network-check-source-989f8b8dc-bvq64 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T21:25:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 976.157µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:37:59Z" - latency: 1.963058ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:37:59Z" - latency: 825.61µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:36:59Z" - latency: 1.668067ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:36:59Z" - latency: 921.884µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:35:59Z" - latency: 1.711809ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:35:59Z" - latency: 886.678µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:34:59Z" - latency: 1.621775ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:34:59Z" - latency: 1.360776ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:33:59Z" - latency: 1.606561ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:33:59Z" kind: List metadata: resourceVersion: ""