apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T17:56:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-156-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-156.ec2.internal uid: 51887886-c4cc-4ada-8a85-7fd6a9511379 resourceVersion: "85013" uid: 73023fbd-aadd-4963-8ba1-5bb04e765b1b spec: sourcePod: network-check-source-7d88cb55d8-4s8jb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T18:03:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.257265ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:59:38Z" - latency: 1.357315ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:58:38Z" - latency: 1.251664ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:57:38Z" - latency: 1.56664ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:56:38Z" - latency: 1.24824ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:55:38Z" - latency: 1.394396ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:54:38Z" - latency: 1.703204ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:53:38Z" - latency: 996.47µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:52:38Z" - latency: 1.391616ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:51:38Z" - latency: 1.070266ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:50:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T17:56:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-156-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-156.ec2.internal uid: 51887886-c4cc-4ada-8a85-7fd6a9511379 resourceVersion: "81631" uid: f104f8da-a0dd-4867-a595-3e4a5020cabe spec: sourcePod: network-check-source-7d88cb55d8-4s8jb targetEndpoint: a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T18:02:38Z" message: 'load-balancer-api-external: tcp connection to a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.963745ms message: 'load-balancer-api-external: tcp connection to a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:56:38Z" - latency: 7.214216ms message: 'load-balancer-api-external: resolved host name a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:56:38Z" - latency: 4.040424ms message: 'load-balancer-api-external: tcp connection to a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:55:38Z" - latency: 9.113191ms message: 'load-balancer-api-external: resolved host name a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:55:38Z" - latency: 5.822064ms message: 'load-balancer-api-external: tcp connection to a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:54:38Z" - latency: 7.38332ms message: 'load-balancer-api-external: resolved host name a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:54:38Z" - latency: 4.776013ms message: 'load-balancer-api-external: tcp connection to a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:53:38Z" - latency: 7.785688ms message: 'load-balancer-api-external: resolved host name a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:53:38Z" - latency: 5.957404ms message: 'load-balancer-api-external: tcp connection to a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:52:38Z" - latency: 7.538941ms message: 'load-balancer-api-external: resolved host name a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:52:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T17:56:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-156-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-156.ec2.internal uid: 51887886-c4cc-4ada-8a85-7fd6a9511379 resourceVersion: "81630" uid: 28a666e5-b5a8-4a3d-8c23-5424ceac53d1 spec: sourcePod: network-check-source-7d88cb55d8-4s8jb targetEndpoint: a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T18:02:38Z" message: 'load-balancer-api-internal: tcp connection to a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.494901ms message: 'load-balancer-api-internal: tcp connection to a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:56:38Z" - latency: 7.284421ms message: 'load-balancer-api-internal: resolved host name a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:56:38Z" - latency: 5.156987ms message: 'load-balancer-api-internal: tcp connection to a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:55:38Z" - latency: 9.0527ms message: 'load-balancer-api-internal: resolved host name a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:55:38Z" - latency: 5.913978ms message: 'load-balancer-api-internal: tcp connection to a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:54:38Z" - latency: 7.294247ms message: 'load-balancer-api-internal: resolved host name a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:54:38Z" - latency: 5.021196ms message: 'load-balancer-api-internal: tcp connection to a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:53:38Z" - latency: 7.829263ms message: 'load-balancer-api-internal: resolved host name a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:53:38Z" - latency: 5.974337ms message: 'load-balancer-api-internal: tcp connection to a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:52:38Z" - latency: 7.463642ms message: 'load-balancer-api-internal: resolved host name a80d6ce4610e84eb2bc106483ed5069b-7bfb7e5c08df3b58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:52:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T17:56:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-156-to-network-check-target-ip-10-0-129-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-156.ec2.internal uid: 51887886-c4cc-4ada-8a85-7fd6a9511379 resourceVersion: "85012" uid: 8fa3b008-8ba4-4b30-9b93-70ecdad965d1 spec: sourcePod: network-check-source-7d88cb55d8-4s8jb targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T18:03:38Z" message: 'network-check-target-ip-10-0-129-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.664462ms message: 'network-check-target-ip-10-0-129-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:59:38Z" - latency: 2.338648ms message: 'network-check-target-ip-10-0-129-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:58:38Z" - latency: 2.557954ms message: 'network-check-target-ip-10-0-129-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:57:38Z" - latency: 2.368535ms message: 'network-check-target-ip-10-0-129-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:56:38Z" - latency: 2.400059ms message: 'network-check-target-ip-10-0-129-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:55:38Z" - latency: 2.359295ms message: 'network-check-target-ip-10-0-129-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:54:38Z" - latency: 2.095014ms message: 'network-check-target-ip-10-0-129-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:53:38Z" - latency: 2.040358ms message: 'network-check-target-ip-10-0-129-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:52:38Z" - latency: 2.236461ms message: 'network-check-target-ip-10-0-129-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:51:38Z" - latency: 2.492018ms message: 'network-check-target-ip-10-0-129-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:50:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T17:56:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-156-to-network-check-target-ip-10-0-135-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-156.ec2.internal uid: 51887886-c4cc-4ada-8a85-7fd6a9511379 resourceVersion: "85011" uid: c9598e30-15cd-4173-b6be-6d0f9e2e8356 spec: sourcePod: network-check-source-7d88cb55d8-4s8jb targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T18:03:38Z" message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.539886ms message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:59:38Z" - latency: 2.511349ms message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:58:38Z" - latency: 2.47389ms message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:57:38Z" - latency: 2.697704ms message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:56:38Z" - latency: 2.255006ms message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:55:38Z" - latency: 2.473641ms message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:54:38Z" - latency: 2.504389ms message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:53:38Z" - latency: 2.034858ms message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:52:38Z" - latency: 2.925077ms message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:51:38Z" - latency: 2.439821ms message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:50:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T17:56:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-156-to-network-check-target-ip-10-0-142-156 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-156.ec2.internal uid: 51887886-c4cc-4ada-8a85-7fd6a9511379 resourceVersion: "85010" uid: 98f76845-1067-45aa-935d-781be7bfa76f spec: sourcePod: network-check-source-7d88cb55d8-4s8jb targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T18:03:38Z" message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.49638ms message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:59:38Z" - latency: 1.072579ms message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:58:38Z" - latency: 1.506ms message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:57:38Z" - latency: 1.619983ms message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:56:38Z" - latency: 1.011306ms message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:55:38Z" - latency: 1.694562ms message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:54:38Z" - latency: 1.798049ms message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:53:38Z" - latency: 1.060195ms message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:52:38Z" - latency: 1.270333ms message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:51:38Z" - latency: 1.250086ms message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:50:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T17:56:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-156-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-156.ec2.internal uid: 51887886-c4cc-4ada-8a85-7fd6a9511379 resourceVersion: "81629" uid: 19c4420b-5953-4493-859e-4c890e1d43b4 spec: sourcePod: network-check-source-7d88cb55d8-4s8jb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T18:02:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.605503ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:56:38Z" - latency: 2.016093ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:56:38Z" - latency: 1.381371ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:55:38Z" - latency: 1.766686ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:55:38Z" - latency: 1.016269ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:54:38Z" - latency: 2.075063ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:54:38Z" - latency: 913.935µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:53:38Z" - latency: 1.815943ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:53:38Z" - latency: 1.152583ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:52:38Z" - latency: 2.092047ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:52:38Z" kind: List metadata: resourceVersion: ""