apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-111-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-111.ec2.internal uid: ad7efbd9-5b2e-4ae2-9f47-e85b7e1f1c61 resourceVersion: "54523" uid: 014e6520-3e24-4b08-859e-cbcb651d945c spec: sourcePod: network-check-source-989f8b8dc-ddbpw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T18:51:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 935.262µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:19:16Z" - latency: 1.180922ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:18:16Z" - latency: 945.982µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:17:16Z" - latency: 1.583868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:16:16Z" - latency: 4.978898ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:15:16Z" - latency: 710.197µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:14:16Z" - latency: 766.396µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:13:16Z" - latency: 966.946µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:12:16Z" - latency: 1.426924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:11:16Z" - latency: 1.233882ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:10:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-111-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-111.ec2.internal uid: ad7efbd9-5b2e-4ae2-9f47-e85b7e1f1c61 resourceVersion: "49629" uid: 02751a67-08a3-4671-bdb9-f16e3c1ec4fe spec: sourcePod: network-check-source-989f8b8dc-ddbpw targetEndpoint: a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T18:50:16Z" message: 'load-balancer-api-external: tcp connection to a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.519987ms message: 'load-balancer-api-external: tcp connection to a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:14:16Z" - latency: 8.87737ms message: 'load-balancer-api-external: resolved host name a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:14:16Z" - latency: 4.343392ms message: 'load-balancer-api-external: tcp connection to a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:13:16Z" - latency: 6.670392ms message: 'load-balancer-api-external: resolved host name a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:13:16Z" - latency: 3.133018ms message: 'load-balancer-api-external: tcp connection to a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:12:16Z" - latency: 8.327599ms message: 'load-balancer-api-external: resolved host name a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:12:16Z" - latency: 5.79032ms message: 'load-balancer-api-external: tcp connection to a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:11:16Z" - latency: 9.523983ms message: 'load-balancer-api-external: resolved host name a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:11:16Z" - latency: 4.229344ms message: 'load-balancer-api-external: tcp connection to a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:10:16Z" - latency: 10.346737ms message: 'load-balancer-api-external: resolved host name a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:10:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-111-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-111.ec2.internal uid: ad7efbd9-5b2e-4ae2-9f47-e85b7e1f1c61 resourceVersion: "49628" uid: b2a754dc-bfb0-4172-a3fa-7d22e1ec699e spec: sourcePod: network-check-source-989f8b8dc-ddbpw targetEndpoint: a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T18:50:16Z" message: 'load-balancer-api-internal: tcp connection to a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.141436ms message: 'load-balancer-api-internal: tcp connection to a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:14:16Z" - latency: 8.900698ms message: 'load-balancer-api-internal: resolved host name a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:14:16Z" - latency: 3.265616ms message: 'load-balancer-api-internal: tcp connection to a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:13:16Z" - latency: 6.607486ms message: 'load-balancer-api-internal: resolved host name a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:13:16Z" - latency: 4.511087ms message: 'load-balancer-api-internal: tcp connection to a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:12:16Z" - latency: 8.258829ms message: 'load-balancer-api-internal: resolved host name a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:12:16Z" - latency: 5.476158ms message: 'load-balancer-api-internal: tcp connection to a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:11:16Z" - latency: 9.574134ms message: 'load-balancer-api-internal: resolved host name a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:11:16Z" - latency: 3.967203ms message: 'load-balancer-api-internal: tcp connection to a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:10:16Z" - latency: 7.360731ms message: 'load-balancer-api-internal: resolved host name a5108e6b59df140258b04e0ab13e17dc-e3c07465437c983a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:10:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-111-to-network-check-target-ip-10-0-129-111 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-111.ec2.internal uid: ad7efbd9-5b2e-4ae2-9f47-e85b7e1f1c61 resourceVersion: "54520" uid: e254eb0f-80f2-42cc-8510-e6876b45cf29 spec: sourcePod: network-check-source-989f8b8dc-ddbpw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:51:16Z" message: 'network-check-target-ip-10-0-129-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 975.123µs message: 'network-check-target-ip-10-0-129-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:19:16Z" - latency: 913.898µs message: 'network-check-target-ip-10-0-129-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:18:16Z" - latency: 874.655µs message: 'network-check-target-ip-10-0-129-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:17:16Z" - latency: 884.088µs message: 'network-check-target-ip-10-0-129-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:16:16Z" - latency: 4.710638ms message: 'network-check-target-ip-10-0-129-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:15:16Z" - latency: 1.252048ms message: 'network-check-target-ip-10-0-129-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:14:16Z" - latency: 994.865µs message: 'network-check-target-ip-10-0-129-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:13:16Z" - latency: 867.677µs message: 'network-check-target-ip-10-0-129-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:12:16Z" - latency: 864.838µs message: 'network-check-target-ip-10-0-129-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:11:16Z" - latency: 2.31097ms message: 'network-check-target-ip-10-0-129-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:10:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-111-to-network-check-target-ip-10-0-131-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-111.ec2.internal uid: ad7efbd9-5b2e-4ae2-9f47-e85b7e1f1c61 resourceVersion: "54522" uid: 545f1bc0-12c0-4723-8606-f4d4fc722f3e spec: sourcePod: network-check-source-989f8b8dc-ddbpw targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:51:16Z" message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.39125ms message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:19:16Z" - latency: 2.429796ms message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:18:16Z" - latency: 2.568065ms message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:17:16Z" - latency: 2.384043ms message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:16:16Z" - latency: 4.306029ms message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:15:16Z" - latency: 2.349824ms message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:14:16Z" - latency: 2.340118ms message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:13:16Z" - latency: 3.029013ms message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:12:16Z" - latency: 2.451551ms message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:11:16Z" - latency: 2.457549ms message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:10:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-111-to-network-check-target-ip-10-0-143-154 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-111.ec2.internal uid: ad7efbd9-5b2e-4ae2-9f47-e85b7e1f1c61 resourceVersion: "54521" uid: eb77bac0-df0e-46e6-865e-5780ca0c4f67 spec: sourcePod: network-check-source-989f8b8dc-ddbpw targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:51:16Z" message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.479854ms message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:19:16Z" - latency: 2.793419ms message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:18:16Z" - latency: 2.489567ms message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:17:16Z" - latency: 2.826974ms message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:16:16Z" - latency: 2.711395ms message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:15:16Z" - latency: 2.275487ms message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:14:16Z" - latency: 2.070351ms message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:13:16Z" - latency: 2.414974ms message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:12:16Z" - latency: 2.62381ms message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:11:16Z" - latency: 4.034403ms message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:10:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-111-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-111.ec2.internal uid: ad7efbd9-5b2e-4ae2-9f47-e85b7e1f1c61 resourceVersion: "49627" uid: 16e77212-186d-4ec2-8e1c-b631cdc0e34f spec: sourcePod: network-check-source-989f8b8dc-ddbpw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T18:50:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.056368ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:14:16Z" - latency: 1.901511ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:14:16Z" - latency: 1.054117ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:13:16Z" - latency: 1.674715ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:13:16Z" - latency: 1.357846ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:12:16Z" - latency: 1.834775ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:12:16Z" - latency: 946.073µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:11:16Z" - latency: 1.843458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:11:16Z" - latency: 999.25µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:10:16Z" - latency: 4.501218ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:10:16Z" kind: List metadata: resourceVersion: ""