apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:22:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-228-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-228.ec2.internal uid: 73200750-ea35-4768-954d-e8a38da91333 resourceVersion: "77887" uid: 4c9587cd-7724-4f50-8f70-897d7311a2ef spec: sourcePod: network-check-source-65bdbbff45-4xp4z targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-05T17:29:46Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 810.891µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:18:46Z" - latency: 1.28974ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:17:46Z" - latency: 938.075µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:16:46Z" - latency: 976.156µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:15:46Z" - latency: 1.035803ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:14:46Z" - latency: 1.29224ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:13:46Z" - latency: 1.07922ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:12:46Z" - latency: 1.593098ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:11:46Z" - latency: 1.004455ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:10:46Z" - latency: 1.155513ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:09:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:22:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-228-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-228.ec2.internal uid: 73200750-ea35-4768-954d-e8a38da91333 resourceVersion: "75984" uid: ca70e31e-f603-4ae3-9774-550ab4292ee9 spec: sourcePod: network-check-source-65bdbbff45-4xp4z targetEndpoint: a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T17:28:46Z" message: 'load-balancer-api-external: tcp connection to a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.346564ms message: 'load-balancer-api-external: tcp connection to a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:16:46Z" - latency: 6.575682ms message: 'load-balancer-api-external: resolved host name a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:16:46Z" - latency: 3.256327ms message: 'load-balancer-api-external: tcp connection to a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:15:46Z" - latency: 6.62253ms message: 'load-balancer-api-external: resolved host name a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:15:46Z" - latency: 3.728791ms message: 'load-balancer-api-external: tcp connection to a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:14:46Z" - latency: 7.17254ms message: 'load-balancer-api-external: resolved host name a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:14:46Z" - latency: 4.462713ms message: 'load-balancer-api-external: tcp connection to a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:13:46Z" - latency: 6.41652ms message: 'load-balancer-api-external: resolved host name a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:13:46Z" - latency: 5.501261ms message: 'load-balancer-api-external: tcp connection to a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:12:46Z" - latency: 6.945814ms message: 'load-balancer-api-external: resolved host name a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:12:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:22:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-228-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-228.ec2.internal uid: 73200750-ea35-4768-954d-e8a38da91333 resourceVersion: "75983" uid: 747602a1-0b1a-4bf5-a290-89f0faaca295 spec: sourcePod: network-check-source-65bdbbff45-4xp4z targetEndpoint: a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T17:28:46Z" message: 'load-balancer-api-internal: tcp connection to a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.346154ms message: 'load-balancer-api-internal: tcp connection to a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:16:46Z" - latency: 6.52639ms message: 'load-balancer-api-internal: resolved host name a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:16:46Z" - latency: 3.642043ms message: 'load-balancer-api-internal: tcp connection to a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:15:46Z" - latency: 6.643531ms message: 'load-balancer-api-internal: resolved host name a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:15:46Z" - latency: 4.367512ms message: 'load-balancer-api-internal: tcp connection to a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:14:46Z" - latency: 7.028456ms message: 'load-balancer-api-internal: resolved host name a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:14:46Z" - latency: 3.814104ms message: 'load-balancer-api-internal: tcp connection to a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:13:46Z" - latency: 6.177337ms message: 'load-balancer-api-internal: resolved host name a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:13:46Z" - latency: 5.479252ms message: 'load-balancer-api-internal: tcp connection to a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:12:46Z" - latency: 6.922516ms message: 'load-balancer-api-internal: resolved host name a1a1bc52740d741a496bba4585a382bb-c43361ff7cd55904.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:12:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:22:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-228-to-network-check-target-ip-10-0-138-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-228.ec2.internal uid: 73200750-ea35-4768-954d-e8a38da91333 resourceVersion: "77884" uid: 1804cde2-5689-43c0-a4d2-7db86522a7db spec: sourcePod: network-check-source-65bdbbff45-4xp4z targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:29:46Z" message: 'network-check-target-ip-10-0-138-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.003755ms message: 'network-check-target-ip-10-0-138-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:18:46Z" - latency: 975.643µs message: 'network-check-target-ip-10-0-138-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:17:46Z" - latency: 988.864µs message: 'network-check-target-ip-10-0-138-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:16:46Z" - latency: 1.214049ms message: 'network-check-target-ip-10-0-138-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:15:46Z" - latency: 961.146µs message: 'network-check-target-ip-10-0-138-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:14:46Z" - latency: 1.513561ms message: 'network-check-target-ip-10-0-138-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:13:46Z" - latency: 947.213µs message: 'network-check-target-ip-10-0-138-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:12:46Z" - latency: 1.472339ms message: 'network-check-target-ip-10-0-138-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:11:46Z" - latency: 880.444µs message: 'network-check-target-ip-10-0-138-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:10:46Z" - latency: 1.382282ms message: 'network-check-target-ip-10-0-138-228: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:09:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:22:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-228-to-network-check-target-ip-10-0-141-37 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-228.ec2.internal uid: 73200750-ea35-4768-954d-e8a38da91333 resourceVersion: "77885" uid: 24a5fbf0-db7a-459b-a24c-aa912c6854d6 spec: sourcePod: network-check-source-65bdbbff45-4xp4z targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:29:46Z" message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.421084ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:18:46Z" - latency: 2.301905ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:17:46Z" - latency: 1.966061ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:16:46Z" - latency: 2.088401ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:15:46Z" - latency: 2.282442ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:14:46Z" - latency: 2.124808ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:13:46Z" - latency: 2.315097ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:12:46Z" - latency: 2.299282ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:11:46Z" - latency: 2.127849ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:10:46Z" - latency: 2.261332ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:09:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:22:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-228-to-network-check-target-ip-10-0-143-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-228.ec2.internal uid: 73200750-ea35-4768-954d-e8a38da91333 resourceVersion: "77886" uid: 474cba1c-cb65-4ed1-b8f4-7f7883696e5c spec: sourcePod: network-check-source-65bdbbff45-4xp4z targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:29:46Z" message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.518278ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:18:46Z" - latency: 2.53437ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:17:46Z" - latency: 2.470873ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:16:46Z" - latency: 2.570382ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:15:46Z" - latency: 1.914366ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:14:46Z" - latency: 2.502096ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:13:46Z" - latency: 2.591427ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:12:46Z" - latency: 2.17515ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:11:46Z" - latency: 1.999074ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:10:46Z" - latency: 2.086784ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:09:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:22:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-228-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-228.ec2.internal uid: 73200750-ea35-4768-954d-e8a38da91333 resourceVersion: "75981" uid: 497161d9-2635-4f2c-b5e9-b655ecaf46cd spec: sourcePod: network-check-source-65bdbbff45-4xp4z targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-05T17:28:46Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.020611ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:16:46Z" - latency: 1.743689ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:16:46Z" - latency: 772.727µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:15:46Z" - latency: 1.45241ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:15:46Z" - latency: 1.053471ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:14:46Z" - latency: 1.779432ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:14:46Z" - latency: 907.762µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:13:46Z" - latency: 2.090833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:13:46Z" - latency: 897.999µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:12:46Z" - latency: 1.759206ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:12:46Z" kind: List metadata: resourceVersion: ""