apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T17:56:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-108-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-108.ec2.internal uid: 0d7afa4b-220c-45f7-ab01-e0080e96e0ec resourceVersion: "57334" uid: 2f94615b-18b8-4d67-8e02-25b4b4638dc6 spec: sourcePod: network-check-source-7bc5b6bf85-ndbkz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T18:03:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.205119ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:38:58Z" - latency: 1.136918ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:37:58Z" - latency: 1.211791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:36:58Z" - latency: 1.262946ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:35:58Z" - latency: 1.12664ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:34:58Z" - latency: 1.107507ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:33:58Z" - latency: 1.058754ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:32:58Z" - latency: 1.039197ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:31:58Z" - latency: 970.02µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:30:58Z" - latency: 1.210666ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:29:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T17:56:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-108-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-108.ec2.internal uid: 0d7afa4b-220c-45f7-ab01-e0080e96e0ec resourceVersion: "57335" uid: 1cfd3472-7750-4a86-8a0a-0660d5049c78 spec: sourcePod: network-check-source-7bc5b6bf85-ndbkz targetEndpoint: ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T18:02:58Z" message: 'load-balancer-api-external: tcp connection to ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.943187ms message: 'load-balancer-api-external: tcp connection to ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:38:58Z" - latency: 6.410408ms message: 'load-balancer-api-external: resolved host name ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:38:58Z" - latency: 6.666005ms message: 'load-balancer-api-external: tcp connection to ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:37:58Z" - latency: 10.422144ms message: 'load-balancer-api-external: resolved host name ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:37:58Z" - latency: 26.19172ms message: 'load-balancer-api-external: tcp connection to ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:36:58Z" - latency: 6.84761ms message: 'load-balancer-api-external: resolved host name ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:36:58Z" - latency: 3.849929ms message: 'load-balancer-api-external: tcp connection to ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:35:58Z" - latency: 7.279753ms message: 'load-balancer-api-external: resolved host name ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:35:58Z" - latency: 4.818198ms message: 'load-balancer-api-external: tcp connection to ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:34:58Z" - latency: 6.728922ms message: 'load-balancer-api-external: resolved host name ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:34:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T17:56:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-108-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-108.ec2.internal uid: 0d7afa4b-220c-45f7-ab01-e0080e96e0ec resourceVersion: "57336" uid: 81b20ec7-98b8-47ed-99b3-60aefa846fbb spec: sourcePod: network-check-source-7bc5b6bf85-ndbkz targetEndpoint: ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T18:02:58Z" message: 'load-balancer-api-internal: tcp connection to ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.924278ms message: 'load-balancer-api-internal: tcp connection to ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:38:58Z" - latency: 6.474366ms message: 'load-balancer-api-internal: resolved host name ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:38:58Z" - latency: 6.303493ms message: 'load-balancer-api-internal: tcp connection to ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:37:58Z" - latency: 10.496901ms message: 'load-balancer-api-internal: resolved host name ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:37:58Z" - latency: 8.904463ms message: 'load-balancer-api-internal: tcp connection to ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:36:58Z" - latency: 6.898286ms message: 'load-balancer-api-internal: resolved host name ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:36:58Z" - latency: 3.548778ms message: 'load-balancer-api-internal: tcp connection to ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:35:58Z" - latency: 7.337828ms message: 'load-balancer-api-internal: resolved host name ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:35:58Z" - latency: 4.890421ms message: 'load-balancer-api-internal: tcp connection to ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:34:58Z" - latency: 6.749775ms message: 'load-balancer-api-internal: resolved host name ade0d5179790e46f791c61b589a33d84-3862e67a95eca7be.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:34:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T17:56:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-108-to-network-check-target-ip-10-0-135-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-108.ec2.internal uid: 0d7afa4b-220c-45f7-ab01-e0080e96e0ec resourceVersion: "57330" uid: 2f104ab9-d977-4548-a6dc-cdb578451256 spec: sourcePod: network-check-source-7bc5b6bf85-ndbkz targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-20T18:03:58Z" message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.038525ms message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:38:58Z" - latency: 1.512382ms message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:37:58Z" - latency: 1.092294ms message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:36:58Z" - latency: 1.010608ms message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:35:58Z" - latency: 914.403µs message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:34:58Z" - latency: 1.006459ms message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:33:58Z" - latency: 889.398µs message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:32:58Z" - latency: 991.753µs message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:31:58Z" - latency: 846.752µs message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:30:58Z" - latency: 887.52µs message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:29:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T17:56:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-108-to-network-check-target-ip-10-0-141-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-108.ec2.internal uid: 0d7afa4b-220c-45f7-ab01-e0080e96e0ec resourceVersion: "57331" uid: b7dc9cae-b0ec-4cbc-bc31-2e746d2097f8 spec: sourcePod: network-check-source-7bc5b6bf85-ndbkz targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T18:03:58Z" message: 'network-check-target-ip-10-0-141-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.411065ms message: 'network-check-target-ip-10-0-141-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:38:58Z" - latency: 2.385053ms message: 'network-check-target-ip-10-0-141-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:37:58Z" - latency: 2.190293ms message: 'network-check-target-ip-10-0-141-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:36:58Z" - latency: 2.356076ms message: 'network-check-target-ip-10-0-141-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:35:58Z" - latency: 2.389737ms message: 'network-check-target-ip-10-0-141-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:34:58Z" - latency: 2.920732ms message: 'network-check-target-ip-10-0-141-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:33:58Z" - latency: 2.008146ms message: 'network-check-target-ip-10-0-141-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:32:58Z" - latency: 2.857505ms message: 'network-check-target-ip-10-0-141-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:31:58Z" - latency: 2.48515ms message: 'network-check-target-ip-10-0-141-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:30:58Z" - latency: 2.488062ms message: 'network-check-target-ip-10-0-141-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:29:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T17:56:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-108-to-network-check-target-ip-10-0-141-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-108.ec2.internal uid: 0d7afa4b-220c-45f7-ab01-e0080e96e0ec resourceVersion: "57332" uid: 9f78bef5-8708-4904-aa26-55da0914b349 spec: sourcePod: network-check-source-7bc5b6bf85-ndbkz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T18:03:58Z" message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.466708ms message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:38:58Z" - latency: 3.322571ms message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:37:58Z" - latency: 2.461879ms message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:36:58Z" - latency: 2.399722ms message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:35:58Z" - latency: 2.735296ms message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:34:58Z" - latency: 2.30097ms message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:33:58Z" - latency: 2.172936ms message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:32:58Z" - latency: 2.397684ms message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:31:58Z" - latency: 2.024741ms message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:30:58Z" - latency: 2.093029ms message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:29:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T17:56:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-108-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-108.ec2.internal uid: 0d7afa4b-220c-45f7-ab01-e0080e96e0ec resourceVersion: "57333" uid: 03868fb3-a9f8-4e72-98b7-2e3999163c67 spec: sourcePod: network-check-source-7bc5b6bf85-ndbkz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T18:02:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 861.943µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:38:58Z" - latency: 1.801896ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T18:38:58Z" - latency: 1.447961ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:37:58Z" - latency: 2.45631ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T18:37:58Z" - latency: 1.173594ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:36:58Z" - latency: 1.888696ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T18:36:58Z" - latency: 1.014016ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:35:58Z" - latency: 1.928879ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T18:35:58Z" - latency: 1.138845ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:34:58Z" - latency: 1.777579ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T18:34:58Z" kind: List metadata: resourceVersion: ""