apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T23:49:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-199-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-199.ec2.internal uid: 783d70e4-4dfb-43d8-a630-7c5e1f82a397 resourceVersion: "32211" uid: a14e30f7-7d77-4c10-bcf1-7fd37203175d spec: sourcePod: network-check-source-65bdbbff45-5lq9k targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-31T23:56:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.02311ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:31:15Z" - latency: 1.058342ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:30:15Z" - latency: 851.362µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:29:15Z" - latency: 963.606µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:28:15Z" - latency: 877.957µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:27:15Z" - latency: 1.024976ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:26:15Z" - latency: 968.916µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:25:15Z" - latency: 937.056µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:24:15Z" - latency: 945.899µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:23:15Z" - latency: 1.140036ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:22:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T23:49:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-199-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-199.ec2.internal uid: 783d70e4-4dfb-43d8-a630-7c5e1f82a397 resourceVersion: "32212" uid: 6fa72351-0d0d-4ac2-a2f9-a149e35ed303 spec: sourcePod: network-check-source-65bdbbff45-5lq9k targetEndpoint: a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-31T23:55:15Z" message: 'load-balancer-api-external: tcp connection to a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.344191ms message: 'load-balancer-api-external: tcp connection to a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:31:15Z" - latency: 7.120682ms message: 'load-balancer-api-external: resolved host name a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T00:31:15Z" - latency: 5.232396ms message: 'load-balancer-api-external: tcp connection to a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:30:15Z" - latency: 9.620489ms message: 'load-balancer-api-external: resolved host name a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T00:30:15Z" - latency: 4.625259ms message: 'load-balancer-api-external: tcp connection to a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:29:15Z" - latency: 8.655966ms message: 'load-balancer-api-external: resolved host name a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T00:29:15Z" - latency: 4.999779ms message: 'load-balancer-api-external: tcp connection to a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:28:15Z" - latency: 7.658865ms message: 'load-balancer-api-external: resolved host name a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T00:28:15Z" - latency: 4.148493ms message: 'load-balancer-api-external: tcp connection to a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:27:15Z" - latency: 7.90432ms message: 'load-balancer-api-external: resolved host name a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T00:27:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T23:49:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-199-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-199.ec2.internal uid: 783d70e4-4dfb-43d8-a630-7c5e1f82a397 resourceVersion: "32213" uid: f18dd523-d123-49f2-ad4f-b99214889859 spec: sourcePod: network-check-source-65bdbbff45-5lq9k targetEndpoint: a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-31T23:55:15Z" message: 'load-balancer-api-internal: tcp connection to a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.31544ms message: 'load-balancer-api-internal: tcp connection to a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:31:15Z" - latency: 7.213187ms message: 'load-balancer-api-internal: resolved host name a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T00:31:15Z" - latency: 5.197464ms message: 'load-balancer-api-internal: tcp connection to a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:30:15Z" - latency: 9.665984ms message: 'load-balancer-api-internal: resolved host name a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T00:30:15Z" - latency: 4.701979ms message: 'load-balancer-api-internal: tcp connection to a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:29:15Z" - latency: 8.712522ms message: 'load-balancer-api-internal: resolved host name a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T00:29:15Z" - latency: 5.006929ms message: 'load-balancer-api-internal: tcp connection to a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:28:15Z" - latency: 7.707119ms message: 'load-balancer-api-internal: resolved host name a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T00:28:15Z" - latency: 4.188673ms message: 'load-balancer-api-internal: tcp connection to a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:27:15Z" - latency: 7.999992ms message: 'load-balancer-api-internal: resolved host name a27e737580ae24d07a03e8120bafa6a7-b9b7abd286d9a8c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T00:27:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T23:49:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-199-to-network-check-target-ip-10-0-128-75 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-199.ec2.internal uid: 783d70e4-4dfb-43d8-a630-7c5e1f82a397 resourceVersion: "32207" uid: 5eafe7cf-7902-46a8-ba2f-86000a5179be spec: sourcePod: network-check-source-65bdbbff45-5lq9k targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-31T23:56:15Z" message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.225273ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:31:15Z" - latency: 1.829572ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:30:15Z" - latency: 1.897466ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:29:15Z" - latency: 1.897175ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:28:15Z" - latency: 1.965123ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:27:15Z" - latency: 1.836219ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:26:15Z" - latency: 1.848604ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:25:15Z" - latency: 1.907754ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:24:15Z" - latency: 1.925382ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:23:15Z" - latency: 2.042102ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:22:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T23:49:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-199-to-network-check-target-ip-10-0-136-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-199.ec2.internal uid: 783d70e4-4dfb-43d8-a630-7c5e1f82a397 resourceVersion: "32210" uid: 3d51e933-d041-4132-8966-ce57ff4a06ad spec: sourcePod: network-check-source-65bdbbff45-5lq9k targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-31T23:56:15Z" message: 'network-check-target-ip-10-0-136-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.197921ms message: 'network-check-target-ip-10-0-136-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:31:15Z" - latency: 2.269149ms message: 'network-check-target-ip-10-0-136-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:30:15Z" - latency: 2.170114ms message: 'network-check-target-ip-10-0-136-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:29:15Z" - latency: 2.56238ms message: 'network-check-target-ip-10-0-136-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:28:15Z" - latency: 2.333189ms message: 'network-check-target-ip-10-0-136-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:27:15Z" - latency: 2.340191ms message: 'network-check-target-ip-10-0-136-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:26:15Z" - latency: 2.297266ms message: 'network-check-target-ip-10-0-136-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:25:15Z" - latency: 2.302779ms message: 'network-check-target-ip-10-0-136-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:24:15Z" - latency: 2.316509ms message: 'network-check-target-ip-10-0-136-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:23:15Z" - latency: 2.131326ms message: 'network-check-target-ip-10-0-136-108: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:22:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T23:49:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-199-to-network-check-target-ip-10-0-142-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-199.ec2.internal uid: 783d70e4-4dfb-43d8-a630-7c5e1f82a397 resourceVersion: "32208" uid: e4968486-91b1-4c70-a953-4cdde6569b04 spec: sourcePod: network-check-source-65bdbbff45-5lq9k targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-31T23:56:15Z" message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.174661ms message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:31:15Z" - latency: 814.834µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:30:15Z" - latency: 836.299µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:29:15Z" - latency: 1.265774ms message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:28:15Z" - latency: 743.071µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:27:15Z" - latency: 781.505µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:26:15Z" - latency: 783.541µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:25:15Z" - latency: 826.882µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:24:15Z" - latency: 971.112µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:23:15Z" - latency: 952.753µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:22:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T23:49:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-199-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-199.ec2.internal uid: 783d70e4-4dfb-43d8-a630-7c5e1f82a397 resourceVersion: "32209" uid: f052e64e-af26-49c0-b17d-a249da3a9f5f spec: sourcePod: network-check-source-65bdbbff45-5lq9k targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-31T23:55:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 975.368µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:31:15Z" - latency: 2.007564ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T00:31:15Z" - latency: 1.115088ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:30:15Z" - latency: 1.772904ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T00:30:15Z" - latency: 900.119µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:29:15Z" - latency: 1.820539ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T00:29:15Z" - latency: 1.118696ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:28:15Z" - latency: 1.618893ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T00:28:15Z" - latency: 1.074715ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T00:27:15Z" - latency: 2.391356ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T00:27:15Z" kind: List metadata: resourceVersion: ""