apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T07:44:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-10-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-10.ec2.internal uid: 41cb13d3-bc68-425e-b717-6d8408cd61b1 resourceVersion: "62477" uid: 360d3d94-bfc2-4316-8ce5-eef53f5130d3 spec: sourcePod: network-check-source-869dcfcdcd-r7f5m targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-11T07:51:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 801.591µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:26:24Z" - latency: 1.156429ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:25:24Z" - latency: 870.462µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:24:24Z" - latency: 835.513µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:23:24Z" - latency: 834.865µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:22:24Z" - latency: 794.711µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:21:24Z" - latency: 728.832µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:20:24Z" - latency: 1.250352ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:19:24Z" - latency: 836.337µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:18:24Z" - latency: 895.075µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:17:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T07:44:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-10-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-10.ec2.internal uid: 41cb13d3-bc68-425e-b717-6d8408cd61b1 resourceVersion: "62480" uid: e92122b2-92c1-4b80-aae2-ccef71488abe spec: sourcePod: network-check-source-869dcfcdcd-r7f5m targetEndpoint: a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-11T07:50:24Z" message: 'load-balancer-api-external: tcp connection to a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.324868ms message: 'load-balancer-api-external: tcp connection to a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:26:24Z" - latency: 7.202372ms message: 'load-balancer-api-external: resolved host name a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T08:26:24Z" - latency: 3.814878ms message: 'load-balancer-api-external: tcp connection to a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:25:24Z" - latency: 7.273855ms message: 'load-balancer-api-external: resolved host name a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T08:25:24Z" - latency: 3.240302ms message: 'load-balancer-api-external: tcp connection to a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:24:24Z" - latency: 6.807612ms message: 'load-balancer-api-external: resolved host name a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T08:24:24Z" - latency: 4.566628ms message: 'load-balancer-api-external: tcp connection to a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:23:24Z" - latency: 6.875518ms message: 'load-balancer-api-external: resolved host name a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T08:23:24Z" - latency: 4.894843ms message: 'load-balancer-api-external: tcp connection to a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:22:24Z" - latency: 7.035292ms message: 'load-balancer-api-external: resolved host name a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T08:22:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T07:44:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-10-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-10.ec2.internal uid: 41cb13d3-bc68-425e-b717-6d8408cd61b1 resourceVersion: "62481" uid: c09afe3b-0177-432a-bbe3-cabc5c00e9a1 spec: sourcePod: network-check-source-869dcfcdcd-r7f5m targetEndpoint: a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-11T07:50:24Z" message: 'load-balancer-api-internal: tcp connection to a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.317938ms message: 'load-balancer-api-internal: tcp connection to a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:26:24Z" - latency: 7.267608ms message: 'load-balancer-api-internal: resolved host name a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T08:26:24Z" - latency: 3.722042ms message: 'load-balancer-api-internal: tcp connection to a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:25:24Z" - latency: 7.427893ms message: 'load-balancer-api-internal: resolved host name a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T08:25:24Z" - latency: 3.195352ms message: 'load-balancer-api-internal: tcp connection to a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:24:24Z" - latency: 6.864436ms message: 'load-balancer-api-internal: resolved host name a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T08:24:24Z" - latency: 4.325055ms message: 'load-balancer-api-internal: tcp connection to a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:23:24Z" - latency: 6.966985ms message: 'load-balancer-api-internal: resolved host name a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T08:23:24Z" - latency: 3.94637ms message: 'load-balancer-api-internal: tcp connection to a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:22:24Z" - latency: 6.993785ms message: 'load-balancer-api-internal: resolved host name a6048030159874df8bfe39bca8c64f89-fbaee16ea3b0a0f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T08:22:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T07:44:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-10-to-network-check-target-ip-10-0-132-10 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-10.ec2.internal uid: 41cb13d3-bc68-425e-b717-6d8408cd61b1 resourceVersion: "62474" uid: 3e890936-3801-404b-a073-2a043d6eb44d spec: sourcePod: network-check-source-869dcfcdcd-r7f5m targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-11T07:51:24Z" message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.12623ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:26:24Z" - latency: 1.282363ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:25:24Z" - latency: 925.957µs message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:24:24Z" - latency: 825.626µs message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:23:24Z" - latency: 968.223µs message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:22:24Z" - latency: 985.416µs message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:21:24Z" - latency: 1.086172ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:20:24Z" - latency: 803.973µs message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:19:24Z" - latency: 1.184155ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:18:24Z" - latency: 1.635015ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:17:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T07:44:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-10-to-network-check-target-ip-10-0-141-181 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-10.ec2.internal uid: 41cb13d3-bc68-425e-b717-6d8408cd61b1 resourceVersion: "62473" uid: 93cacc7a-1367-4618-bbc3-dd9ffc2d999b spec: sourcePod: network-check-source-869dcfcdcd-r7f5m targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-11T07:51:24Z" message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.071007ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:26:24Z" - latency: 1.673389ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:25:24Z" - latency: 2.157976ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:24:24Z" - latency: 1.800989ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:23:24Z" - latency: 1.814994ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:22:24Z" - latency: 1.806401ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:21:24Z" - latency: 1.724367ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:20:24Z" - latency: 1.860034ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:19:24Z" - latency: 1.913255ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:18:24Z" - latency: 2.158319ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:17:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T07:44:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-10-to-network-check-target-ip-10-0-142-153 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-10.ec2.internal uid: 41cb13d3-bc68-425e-b717-6d8408cd61b1 resourceVersion: "62475" uid: 4a1921e1-3d34-4a08-a235-4befb4dca2ea spec: sourcePod: network-check-source-869dcfcdcd-r7f5m targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-11T07:51:24Z" message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.029509ms message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:26:24Z" - latency: 1.658303ms message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:25:24Z" - latency: 1.987098ms message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:24:24Z" - latency: 2.05681ms message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:23:24Z" - latency: 2.075017ms message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:22:24Z" - latency: 2.24006ms message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:21:24Z" - latency: 2.132429ms message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:20:24Z" - latency: 1.964942ms message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:19:24Z" - latency: 1.971769ms message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:18:24Z" - latency: 2.251552ms message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:17:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T07:44:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-10-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-10.ec2.internal uid: 41cb13d3-bc68-425e-b717-6d8408cd61b1 resourceVersion: "62476" uid: 56048fbd-697d-457f-b2a0-d96649aa730e spec: sourcePod: network-check-source-869dcfcdcd-r7f5m targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-11T07:50:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 902.518µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:26:24Z" - latency: 1.974811ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T08:26:24Z" - latency: 912.898µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:25:24Z" - latency: 1.61601ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T08:25:24Z" - latency: 784.778µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:24:24Z" - latency: 1.771519ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T08:24:24Z" - latency: 995.451µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:23:24Z" - latency: 1.965262ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T08:23:24Z" - latency: 838.282µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T08:22:24Z" - latency: 1.758107ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T08:22:24Z" kind: List metadata: resourceVersion: ""