apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T15:14:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-79-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-79.ec2.internal uid: 9c36e956-d33d-479d-b4e6-c3749328e93c resourceVersion: "75075" uid: cf8f9e9c-a1a5-46ea-9c10-525e3245d845 spec: sourcePod: network-check-source-7d88cb55d8-mnwh8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-30T15:21:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.452815ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:10:52Z" - latency: 1.816782ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:09:52Z" - latency: 1.064682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:08:52Z" - latency: 947.147µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:07:52Z" - latency: 1.601923ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:06:52Z" - latency: 1.171186ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:05:52Z" - latency: 1.575808ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:04:52Z" - latency: 1.209834ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:03:52Z" - latency: 1.148068ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:02:52Z" - latency: 1.052825ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:01:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T15:14:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-79-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-79.ec2.internal uid: 9c36e956-d33d-479d-b4e6-c3749328e93c resourceVersion: "79327" uid: 6866b41f-cb28-4bfe-81cb-f28825690e6a spec: sourcePod: network-check-source-7d88cb55d8-mnwh8 targetEndpoint: afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T15:20:52Z" message: 'load-balancer-api-external: tcp connection to afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.748219ms message: 'load-balancer-api-external: tcp connection to afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:14:52Z" - latency: 8.363656ms message: 'load-balancer-api-external: resolved host name afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T16:14:52Z" - latency: 4.131126ms message: 'load-balancer-api-external: tcp connection to afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:13:52Z" - latency: 6.743746ms message: 'load-balancer-api-external: resolved host name afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T16:13:52Z" - latency: 4.324219ms message: 'load-balancer-api-external: tcp connection to afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:12:52Z" - latency: 8.951674ms message: 'load-balancer-api-external: resolved host name afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T16:12:52Z" - latency: 5.013513ms message: 'load-balancer-api-external: tcp connection to afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:11:52Z" - latency: 7.687845ms message: 'load-balancer-api-external: resolved host name afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T16:11:52Z" - latency: 5.10847ms message: 'load-balancer-api-external: tcp connection to afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:10:52Z" - latency: 9.376164ms message: 'load-balancer-api-external: resolved host name afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T16:10:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T15:14:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-79-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-79.ec2.internal uid: 9c36e956-d33d-479d-b4e6-c3749328e93c resourceVersion: "79326" uid: 686f014e-885f-4689-b14e-4d465249c95f spec: sourcePod: network-check-source-7d88cb55d8-mnwh8 targetEndpoint: afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T15:20:52Z" message: 'load-balancer-api-internal: tcp connection to afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.68484ms message: 'load-balancer-api-internal: tcp connection to afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:14:52Z" - latency: 8.352406ms message: 'load-balancer-api-internal: resolved host name afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T16:14:52Z" - latency: 4.148364ms message: 'load-balancer-api-internal: tcp connection to afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:13:52Z" - latency: 6.660289ms message: 'load-balancer-api-internal: resolved host name afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T16:13:52Z" - latency: 3.607118ms message: 'load-balancer-api-internal: tcp connection to afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:12:52Z" - latency: 8.863596ms message: 'load-balancer-api-internal: resolved host name afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T16:12:52Z" - latency: 5.057321ms message: 'load-balancer-api-internal: tcp connection to afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:11:52Z" - latency: 7.716304ms message: 'load-balancer-api-internal: resolved host name afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T16:11:52Z" - latency: 4.46493ms message: 'load-balancer-api-internal: tcp connection to afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:10:52Z" - latency: 9.287756ms message: 'load-balancer-api-internal: resolved host name afd101fae1b034d6f8e5f218e6ddd8c6-26bd3e1ec47c2b21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T16:10:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T15:14:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-79-to-network-check-target-ip-10-0-133-210 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-79.ec2.internal uid: 9c36e956-d33d-479d-b4e6-c3749328e93c resourceVersion: "75074" uid: 44662ba3-e7cc-4646-8b66-6a5f1d7b8f2b spec: sourcePod: network-check-source-7d88cb55d8-mnwh8 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T15:21:52Z" message: 'network-check-target-ip-10-0-133-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.241418ms message: 'network-check-target-ip-10-0-133-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:10:52Z" - latency: 2.688247ms message: 'network-check-target-ip-10-0-133-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:09:52Z" - latency: 1.855386ms message: 'network-check-target-ip-10-0-133-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:08:52Z" - latency: 2.261115ms message: 'network-check-target-ip-10-0-133-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:07:52Z" - latency: 2.19805ms message: 'network-check-target-ip-10-0-133-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:06:52Z" - latency: 2.303324ms message: 'network-check-target-ip-10-0-133-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:05:52Z" - latency: 2.576707ms message: 'network-check-target-ip-10-0-133-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:04:52Z" - latency: 2.379935ms message: 'network-check-target-ip-10-0-133-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:03:52Z" - latency: 2.408672ms message: 'network-check-target-ip-10-0-133-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:02:52Z" - latency: 2.298249ms message: 'network-check-target-ip-10-0-133-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:01:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T15:14:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-79-to-network-check-target-ip-10-0-138-79 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-79.ec2.internal uid: 9c36e956-d33d-479d-b4e6-c3749328e93c resourceVersion: "75072" uid: 4f22d31a-7ff7-48d3-a381-c581230dd1b3 spec: sourcePod: network-check-source-7d88cb55d8-mnwh8 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-30T15:21:52Z" message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.090442ms message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:10:52Z" - latency: 918.282µs message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:09:52Z" - latency: 1.021412ms message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:08:52Z" - latency: 1.055532ms message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:07:52Z" - latency: 977.208µs message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:06:52Z" - latency: 1.01577ms message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:05:52Z" - latency: 966.703µs message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:04:52Z" - latency: 917.198µs message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:03:52Z" - latency: 976.597µs message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:02:52Z" - latency: 795.477µs message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:01:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T15:14:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-79-to-network-check-target-ip-10-0-142-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-79.ec2.internal uid: 9c36e956-d33d-479d-b4e6-c3749328e93c resourceVersion: "75073" uid: 7af82881-6e03-402f-be93-e9899def00fa spec: sourcePod: network-check-source-7d88cb55d8-mnwh8 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T15:21:52Z" message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.451377ms message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:10:52Z" - latency: 2.605442ms message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:09:52Z" - latency: 2.016496ms message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:08:52Z" - latency: 2.109349ms message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:07:52Z" - latency: 2.215711ms message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:06:52Z" - latency: 2.338357ms message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:05:52Z" - latency: 2.212019ms message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:04:52Z" - latency: 2.253556ms message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:03:52Z" - latency: 2.197569ms message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:02:52Z" - latency: 1.889038ms message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:01:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T15:14:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-79-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-79.ec2.internal uid: 9c36e956-d33d-479d-b4e6-c3749328e93c resourceVersion: "79325" uid: 8221edf4-a966-430f-a005-b5bab5f87719 spec: sourcePod: network-check-source-7d88cb55d8-mnwh8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-30T15:20:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 987.565µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:14:52Z" - latency: 1.919608ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T16:14:52Z" - latency: 971.194µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:13:52Z" - latency: 2.876754ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T16:13:52Z" - latency: 940.394µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:12:52Z" - latency: 1.912135ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T16:12:52Z" - latency: 1.106322ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:11:52Z" - latency: 1.835438ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T16:11:52Z" - latency: 986.097µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T16:10:52Z" - latency: 1.925915ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T16:10:52Z" kind: List metadata: resourceVersion: ""