apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T16:07:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-158-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-158.ec2.internal uid: 4813f765-6a58-4bf5-bcd3-2d3d003f4649 resourceVersion: "44009" uid: efa7aa2b-6dfa-41b7-a94d-85da91b27b7c spec: sourcePod: network-check-source-8894fc9bd-9hksj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-21T16:14:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.037716ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:35:40Z" - latency: 1.036419ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:34:40Z" - latency: 950.77µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:33:40Z" - latency: 937.851µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:32:40Z" - latency: 1.004444ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:31:40Z" - latency: 1.499976ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:30:40Z" - latency: 804.446µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:29:40Z" - latency: 976.873µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:28:40Z" - latency: 1.046752ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:27:40Z" - latency: 1.069265ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:26:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T16:07:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-158-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-158.ec2.internal uid: 4813f765-6a58-4bf5-bcd3-2d3d003f4649 resourceVersion: "45978" uid: 3f9269db-d903-4e98-829a-156c73f52726 spec: sourcePod: network-check-source-8894fc9bd-9hksj targetEndpoint: a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T16:13:40Z" message: 'load-balancer-api-external: tcp connection to a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.172698ms message: 'load-balancer-api-external: tcp connection to a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:37:40Z" - latency: 6.502485ms message: 'load-balancer-api-external: resolved host name a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:37:40Z" - latency: 6.04989ms message: 'load-balancer-api-external: tcp connection to a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:36:40Z" - latency: 6.502243ms message: 'load-balancer-api-external: resolved host name a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:36:40Z" - latency: 5.167566ms message: 'load-balancer-api-external: tcp connection to a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:35:40Z" - latency: 10.419047ms message: 'load-balancer-api-external: resolved host name a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:35:40Z" - latency: 5.534552ms message: 'load-balancer-api-external: tcp connection to a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:34:40Z" - latency: 9.813815ms message: 'load-balancer-api-external: resolved host name a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:34:40Z" - latency: 5.17307ms message: 'load-balancer-api-external: tcp connection to a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:33:40Z" - latency: 10.905779ms message: 'load-balancer-api-external: resolved host name a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:33:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T16:07:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-158-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-158.ec2.internal uid: 4813f765-6a58-4bf5-bcd3-2d3d003f4649 resourceVersion: "45979" uid: ea726ded-086c-4d5d-97cb-277c54cb9e8a spec: sourcePod: network-check-source-8894fc9bd-9hksj targetEndpoint: a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T16:13:40Z" message: 'load-balancer-api-internal: tcp connection to a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.737515ms message: 'load-balancer-api-internal: tcp connection to a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:37:40Z" - latency: 6.558525ms message: 'load-balancer-api-internal: resolved host name a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:37:40Z" - latency: 6.087465ms message: 'load-balancer-api-internal: tcp connection to a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:36:40Z" - latency: 6.438812ms message: 'load-balancer-api-internal: resolved host name a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:36:40Z" - latency: 5.184656ms message: 'load-balancer-api-internal: tcp connection to a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:35:40Z" - latency: 10.394461ms message: 'load-balancer-api-internal: resolved host name a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:35:40Z" - latency: 5.181497ms message: 'load-balancer-api-internal: tcp connection to a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:34:40Z" - latency: 9.732423ms message: 'load-balancer-api-internal: resolved host name a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:34:40Z" - latency: 4.278302ms message: 'load-balancer-api-internal: tcp connection to a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:33:40Z" - latency: 10.82609ms message: 'load-balancer-api-internal: resolved host name a4cc3d65bc9844f389e68de35ce2ee60-4bdbe0257ec45f2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:33:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T16:07:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-158-to-network-check-target-ip-10-0-129-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-158.ec2.internal uid: 4813f765-6a58-4bf5-bcd3-2d3d003f4649 resourceVersion: "44007" uid: 6d23bfd8-fa90-4c9c-9ec0-6e9bff6067bb spec: sourcePod: network-check-source-8894fc9bd-9hksj targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T16:14:40Z" message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.352906ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:35:40Z" - latency: 2.123427ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:34:40Z" - latency: 2.018567ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:33:40Z" - latency: 2.45308ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:32:40Z" - latency: 1.926233ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:31:40Z" - latency: 2.883424ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:30:40Z" - latency: 2.254391ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:29:40Z" - latency: 2.075469ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:28:40Z" - latency: 2.243718ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:27:40Z" - latency: 2.090085ms message: 'network-check-target-ip-10-0-129-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:26:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T16:07:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-158-to-network-check-target-ip-10-0-138-191 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-158.ec2.internal uid: 4813f765-6a58-4bf5-bcd3-2d3d003f4649 resourceVersion: "44006" uid: e941029d-7f1e-4193-ad21-5e7b450848a8 spec: sourcePod: network-check-source-8894fc9bd-9hksj targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T16:14:40Z" message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.285367ms message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:35:40Z" - latency: 1.93222ms message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:34:40Z" - latency: 2.125585ms message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:33:40Z" - latency: 2.441134ms message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:32:40Z" - latency: 2.466301ms message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:31:40Z" - latency: 2.644622ms message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:30:40Z" - latency: 2.66515ms message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:29:40Z" - latency: 2.03434ms message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:28:40Z" - latency: 2.064712ms message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:27:40Z" - latency: 2.119856ms message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:26:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T16:07:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-158-to-network-check-target-ip-10-0-142-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-158.ec2.internal uid: 4813f765-6a58-4bf5-bcd3-2d3d003f4649 resourceVersion: "44005" uid: bb39e040-7538-45d6-8237-df67019a8b21 spec: sourcePod: network-check-source-8894fc9bd-9hksj targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-21T16:14:40Z" message: 'network-check-target-ip-10-0-142-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.16721ms message: 'network-check-target-ip-10-0-142-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:35:40Z" - latency: 897.071µs message: 'network-check-target-ip-10-0-142-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:34:40Z" - latency: 1.411399ms message: 'network-check-target-ip-10-0-142-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:33:40Z" - latency: 929.855µs message: 'network-check-target-ip-10-0-142-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:32:40Z" - latency: 840.412µs message: 'network-check-target-ip-10-0-142-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:31:40Z" - latency: 1.145467ms message: 'network-check-target-ip-10-0-142-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:30:40Z" - latency: 1.366637ms message: 'network-check-target-ip-10-0-142-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:29:40Z" - latency: 1.020555ms message: 'network-check-target-ip-10-0-142-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:28:40Z" - latency: 840.217µs message: 'network-check-target-ip-10-0-142-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:27:40Z" - latency: 854.304µs message: 'network-check-target-ip-10-0-142-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:26:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T16:07:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-158-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-158.ec2.internal uid: 4813f765-6a58-4bf5-bcd3-2d3d003f4649 resourceVersion: "45976" uid: 926e84b9-8481-4e19-b011-dbd1ceabcbf9 spec: sourcePod: network-check-source-8894fc9bd-9hksj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-21T16:13:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.017272ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:37:40Z" - latency: 1.75011ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T16:37:40Z" - latency: 874.075µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:36:40Z" - latency: 2.126945ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T16:36:40Z" - latency: 772.774µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:35:40Z" - latency: 1.620594ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T16:35:40Z" - latency: 787.931µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:34:40Z" - latency: 1.79471ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T16:34:40Z" - latency: 1.1215ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:33:40Z" - latency: 1.835298ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T16:33:40Z" kind: List metadata: resourceVersion: ""